theinterneti/TTA.dev / .claude/skills/sdd-workflow
sdd-workflow
UnverifiedUse this skill when the user asks to build a new feature or write implementation code. Enforces the Spec-Driven Development (SDD) 4-phase workflow before any code is written.
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)
- Which packages are affected (
-
/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
/specifyfirst and explain the SDD process. - Reference this constitution by section (e.g., "Per §2 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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |