Sdd workflow

Skill theinterneti/TTA.dev/.github/skills/sdd-workflow

Use this skill when the user asks to build a new feature, implement code, or start development work. Enforces the Spec-Driven Development (SDD) 4-phase workflow before any code is written. Invoke when the user says "build", "implement", "create a feature", "write code for", or "add support for".From its SKILL.md

Install

npx -y skills add theinterneti/TTA.dev --skill sdd-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 418 tokens by cl100k_base, as published. Nobody here has run it

Spec-Driven Development Workflow (TTA.dev)

No implementation code may be written before completing the SDD phases.

The 4 Phases

Execute these phases sequentially. No phase may be skipped.

/specify — Functional Specification (The "What")
- User journeys, edge cases, success criteria, out-of-scope
- Output: Markdown document for user review and approval
/plan — Technical Plan (The "How")
- Which packages are affected (tta-dev-primitives, tta-observability-integration, etc.)
- New modules, classes, functions to create
- How the feature composes with existing primitives (>>, |)
- External dependencies with justification
- Observability strategy (traces, metrics, logs)
/tasks — Task Breakdown
- Isolated, testable work units
- Each task includes acceptance test description
- Numbered by dependency (topological sort)
- Format: Markdown checklist
/implement — Test-Driven Implementation
- Red: Write failing test encoding acceptance criteria
- Green: Minimal implementation to pass the test
- Refactor: Clean up while tests stay green
- Run quality gate before marking task complete

Exceptions

/spike: User explicitly requests prototype code. Spike code must never be merged without going through the full SDD workflow afterward.

Enforcement

If the user asks for code without a spec, initiate /specify first and explain the SDD process.
Reference this process by phase (e.g., "Per Phase 1, I need to generate a spec first.").

Deep Reference

For the complete SDD Constitution with all tables and detailed guidance, see docs/agent-guides/sdd-constitution.md.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.