sdd-skill

Collect user's implicit knowledge (business context, technical constraints, past failures, hidden assumptions) through interactive dialogue and save as _interview-notes.yaml before executing feature documentation skills. Use when running /interview command or automatically before any start-teams-doc phase. Generic design allows use with skills beyond teams-docs.

Unified entry point for generating feature documentation in the teams/ directory. Automatically detects the current phase (Discovery, Design, QA, Operations) and delegates to the appropriate skill. Use when creating new feature docs, continuing existing feature docs, or when user says /start-teams-doc.

Generate Design phase documents (non-functional requirements, domain modeling, ADR, specifications) in the teams/ directory. Phase 2 of the /start-teams-doc workflow. Requires Discovery phase approval. Use when creating design documents, ADRs, ER diagrams, or non-functional requirements.

Generate Discovery phase documents (PRD and user stories) in the teams/ directory. Phase 1 of the /start-teams-doc workflow. Use when creating PRDs, user stories, or requirements definitions under teams/.

Generate Operations phase documents (SLO/SLA definitions, performance test records, operational runbooks) in the teams/ directory. Phase 4 of the /start-teams-doc workflow. Requires QA phase approval. Use when defining SLO/SLA, creating runbooks, or documenting operational procedures.

Generate QA phase documents (test plan, non-functional requirement tests, Gherkin scenarios) in the teams/ directory. Phase 3 of the /start-teams-doc workflow. Requires Design phase approval. Use when creating test plans, test scenarios, Gherkin .feature files.