PDD version 0.34.1

pdd-ideate

Ideate decides what the product should do and writes that decision into the Product Model.

Use it for a new product or for any change in behavior, before you implement. You don't have to name it: asking your agent to add or change something in the product, or to make a PDD change, starts it. If the repository already has code but no model, it stops and asks you to run pdd-map first: it won't plan against behavior nobody has described.

/pdd-ideate guest checkout

What you get

  1. Questions, each with a recommendation. A small, specific change gets at most three, asked together. A new product or a broad change is worked in rounds, waiting after each: boundary first (what the product is, who it is for, which surfaces are supported Interfaces), then granularity, such as whether a family of things is one Entity or several, quoted with both counts; then acceptance, which cases each Capability needs; then naming, the product's own word for each thing.
  2. The proposed change. Every resource added, changed or removed, each Capability's Scenarios, the implementation work it implies, and any open questions.
  3. Files written after you approve, only inside product-model/.
  4. Lint, fixed until clean.
  5. An offer to implement: the approved change and its Scenarios are what the code must satisfy. Say implement it, and pdd-verify has your agent implement it in phases and checks each part.

Ideate never writes code. Implementation happens through your own agent, your usual way.

Modes

  • Explore: no specific change yet. It proposes three to five genuinely different directions and writes nothing.
  • Converge: a named outcome or behavior. It works the questions above, then writes the approved change.
  • Resolve: verify has already found a gap and you decided the model should change. It skips brainstorming and drafts the smallest exact change.

What it decides

Beyond what the product does and where, ideate settles:

  • Who may do each thing, always as a grant on a Business Rule, never a sentence in a Scenario.
  • Flags, plans and A/B tests: whether each makes a Variation, by What selects.
  • Granularity: Scenarios are cases of one behavior. Something meaningful on its own becomes its own Capability, grouped by a Domain when that helps.

It attaches the PRD, spec or design the decision came from as a Reference with role: intent, so the source stays linked without being copied. See Is this replacing my PRD?

Related

map

Create or expand a Product Model from the code you already have, without running it.

verify

Implement the Product Model in code, in phases, or check that the model and the code agree, and resolve every gap you approve until they do or something blocks.