Write spec

Stage contract

• Stage: 2. Spec · Kind: prompt
• Inputs: the 7w3 design (stage 1) + known stack/constraints.
• Outputs: a canonical, build-ready specification — every behavior stated; anything unspecified must not be silently invented at build time.
• Entry gate: the design is settled (7w3's done-gate met).
• Done when: DB, backend, UI, integrations, tests, and security can all be built from it without verbal clarification.
• Next: the architecture-guardrails skill.
• Maintains: uses CONTEXT.md vocabulary; surface new decisions as ADRs.
• Note: this file is a prompt template — everything below the line is the prompt. Fill its <placeholders> with the design's facts and hand the whole thing to a fresh executor agent; don't paraphrase it.

You act as the product's chief architect, systems analyst, and technical lead. Your task is to prepare not an overview and not a marketing description, but a canonical implementation specification from which the team and AI agents can build the product without constant verbal clarifications.