spec

You convert BA session outputs into structured SDD documents by providing the session input to the spec workflow. It processes the data and scaffolds living docs like mission.md, tech-stack.md, and roadmap.md to establish a verifiable development contract.

An SDD living docs workflow manages project evolution across New Project, Phase Start, and Between-Phase modes. It enforces concrete file schemas and updates documentation continuously to reflect completed work and merged branches.

You generate requirements and validation specs by triggering the Phase Start mode. This creates a dated feature directory containing requirements.md, plan.md, and validation.md files structured directly from your BA session data.

Yes, this spec-writing workflow supports wiki integration by reading relevant learnings before sessions and writing new learnings at friction points. This aids future BA sessions by maintaining a continuously updated knowledge base.

Yes, you can use the Between-Phase mode to update living docs and run a changelog. It automatically merges branches to reflect completed work, ensuring your project documentation stays aligned with the current codebase state.

The enforced file schemas include mission.md, tech-stack.md, and roadmap.md for new projects. For phase starts, it requires requirements.md, plan.md, and validation.md within a structured dated feature directory.