tdd-design

To document a TDD design, this Skill guides stakeholders through structured context gathering and vision alignment, automatically generating a concrete design.md artifact for your project.

Start a collaborative TDD design session by naming your design, such as "new-auth-workflow"; the Skill enforces a structured workflow with preflight checks and collaboration locks to manage stakeholder input.

The TDD design pipeline handles revisions by revising existing design.md artifacts, guiding stakeholders through updated context gathering, vision alignment, and logging changes in the design inventory.

Yes, the TDD workflow enforces a specific file structure, automatically creating and maintaining your design documentation within the docs/tdd-designs/<design-name>/design.md directory path.

Yes, you can use this for aligning team vision before writing tests; it orchestrates high-level design conversations to surface problem statements, scope, dependencies, and constraints prior to implementation.

A key limitation is that collaboration locks are managed strictly via preflight checks within the design workflow, meaning concurrent stakeholder edits outside this structured session are not natively synchronized.