plan

Plan

Create a complete, actionable plan for implementing a single module.

Process

1. Read module definition: artifacts/03-modules/{module}/module.md
2. Read module spec (BA-owned): artifacts/03-modules/{module}/spec.md — this has requirements, user stories (STORY-IDs), and acceptance criteria. Check the Changelog table for recent changes.
3. Read architecture overview: artifacts/03-modules/architecture.md — this has system-level decisions (deployment, DB, comms patterns) that constrain your design
4. Read context brief: artifacts/02-discovery/context-brief.md
5. Read any relevant research: artifacts/01-research/
6. Check dependencies: are dependent modules' interfaces defined?

Step 5: Gather decisions BEFORE writing artifacts

Decision gathering process:

1. List all technical decisions this module requires (database, framework, auth, APIs, etc.)
2. For each decision, check if it's already resolved:
   • Specified in context-brief.md → use it, no need to ask
   • Specified in module definition → use it, no need to ask
   • Decided in a research artifact → use it, no need to ask
   • Not specified anywhere → must ask the user
3. For each unresolved decision, present 2-3 options:
   • Option name
   • One-line trade-off
   • Your recommendation and why
4. One question at a time — don't dump all decisions in one message
5. Document each decision in the design artifact with rationale

Example flow:

You: "For the auth module, I need to decide on a few things.
     First: what database should we use?
     A) PostgreSQL — battle-tested, great for relational data
     B) SQLite — simple, no server needed, good for small-medium scale
     C) MongoDB — flexible schema, good for rapid iteration
     I'd recommend A for this use case because [reason]. What do you think?"

User: "go with A"

You: "Got it, PostgreSQL. Next: for authentication strategy..."