sdlc-plan

Write intent/<slug>/intent.md from the user's idea, in their words. One page. It is both the agreement and the checklist you will be held to.

Triage

• A feasibility question is a spike: answer it, no intent.
• A bug, tweak, or small behavior change in an existing flow is sdlc-fix, no intent.
• Anything that changes what the product does is an intent. Pick the tier and write it in the frontmatter:
  • change: ordinary feature. One intent file, then build.
  • critical: consequential (migration on populated tables, auth, secrets, privacy or PII, destructive or irreversible operations, LLM prompts or gates that change generated content or approval, external sends, scraping policy). Adds a ## Spec section to the same file and a stricter review (a missing independent reviewer blocks).
  • Both tiers get a fresh-context sdlc-verify after apply.
  • When unsure, take critical.

Rules that matter