IAP Catalog Specification

Required product iap_catalog_spec

Agent Prompt Snippet

Ensure the project has an IAP catalog specification covering purchasable items, currency bundles, pricing tiers, and store integration.

Purpose

An IAP catalog specification lists purchasable items, virtual currency bundles, pricing tiers, and platform store integration details needed to operate an in-game storefront.

This is a Required document — every project of this type should have one. Without it, the team risks misalignment, rework, or undetected issues that compound over time.

Key Sections to Include

Purchasable items
Currency bundles
Pricing tiers
Store integration

Agent hint: Ensure the project has an IAP catalog specification covering purchasable items, currency bundles, pricing tiers, and store integration.

What Makes It Good vs Bad

A strong version of this document:

Clearly articulates the problem being solved and for whom
Includes measurable success criteria and acceptance tests
Prioritizes features with clear rationale for ordering
Connects user needs to technical requirements traceably
Reviewed by both product and engineering stakeholders

Warning signs of a weak version:

Feature list without context on user problems or goals
No success metrics — impossible to know if the feature worked
Requirements so vague that multiple interpretations are valid
Missing edge cases or error scenarios
Written in isolation without cross-functional input

Common Mistakes

Conflating features (solutions) with user problems (needs)
Defining success metrics after launch rather than before
Not involving engineering early enough to assess feasibility
Scope creep — adding requirements without re-evaluating priority and timeline

How to Use This Document

Start with the user problem, not the solution. Define who experiences the problem, how painful it is, and how you’ll know when it’s solved. Use acceptance criteria that are testable — ’the user can do X’ rather than ’the system supports X’. Prioritize ruthlessly: every feature has an opportunity cost.

For AI agents: Use product documents to understand the intent behind features. When implementing, ensure acceptance criteria are met and edge cases from the spec are handled. Flag any requirements that seem ambiguous or contradictory.

Starter Template

SpecBase includes a ready-to-use template for this document: kb/templates/product/iap_catalog_spec.md.tmpl. Use the SpecBase CLI or MCP integration to generate it pre-filled for your project.

# Generate stubs via CLI
specbase init <archetype> --features <features> --dir ./docs