csp-spec-driven-developmentlisted

| Phase | Command | Artifact | |-------|---------|----------| | Clarify what to build | `/csp-spec-phase` | `{phase}-CSPEC.md` | | Discuss how to build | `/csp-discuss-phase` | Discussion notes → PLAN inputs | | Plan implementation | `/csp-plan-phase` | `{phase}-PLAN.md` + tasks | | Execute tasks | `/csp-execute-phase` | Code + `{plan}-SUMMARY.md` | | Verify alignment | `/csp-verify-phase` | `VERIFICATION.md` | | Ship / archive | `/csp-ship` | PR + milestone archive | **Quick change path** (single feature, no full milestone): ``` /csp-planning-phase → proposal + requirements in .planning/ /csp-solutioning-phase → design + task breakdown /csp-implementation-phase → implement with checkbox tracking /csp-verify-phase → three-dimension check /csp-ship ``` Templates: `csp-workflow/templates/change-artifacts/` ## Artifact Dependency Graph Create artifacts in dependency order: ``` Proposal (why + scope) ↓ Requirements / CSPEC (what — falsifiable) ↓ Design (how — decisions + trade-offs) ↓ Tasks (ordered checkboxes) ↓ Implementation ↓ Verification (evidence-backed) ``` **Rule:** Never skip a layer for non-trivial work. If design is trivial, write a one-paragraph design stub — don't omit the file. ## Delta Requirements (Brownfield) When modifying existing behavior, use **delta sections** in spec files: ```markdown ## ADDED Requirements ### Requirement: User can export data ... ## MODIFIED Requirements ### Requirement: Login session timeout (full u