onur-aslan/sdd
Spec-Driven Development (SDD) core workflow from planning to implementation, including project feature discovery, the one-shot sdd-developer pipeline, domain-agnostic bug-fix and enhancement loops, and E2E verification. Companion plugin: vibecoding.
Autonomously reproduce, diagnose, and fix bugs with a bounded fix-and-verify loop.
Conducts an interview-driven design session using a multi-level zoom approach (L5:Domain to L1:Line), producing a structured spec.md under docs/sdd/features/. Use when user mentions "deep-spec", "spec-designer", or wants to design a new feature through guided questioning.
Plan, implement, and verify enhancements through an approved plan and a bounded execution loop.
Verify every User Story and all its Acceptance Criteria sequentially using a separate subagent per story. Fix discovered issues and re-verify. Invoke only when explicitly named by the user or another skill/prompt.
Implement feature.md tasks one at a time with Chicago TDD, then review and fix, then per-story E2E verification. Invoke ONLY when the feature-tdd skill is explicitly named — by the user (e.g. /feature-tdd) or by another skill/prompt instructing to invoke feature-tdd by name. Never select this skill by matching a task description to it.
Discover existing project features by scanning the codebase and generate a spec for each.
Implement spec.md through baseline checks, sequential subagents, review and fix, and per-story E2E verification.
Convert a spec into an ordered task list with explicit implementation steps.