← ClaudeAtlas

agentic-sdd-routerlisted

Route spec-driven development work to the correct phase skill. Use when the user asks for SDD, spec-driven development, Spec Kit style workflow, feature planning, implementation from specs, verification, or spec drift review.
nawodyaishan/universal-mcp-sync · ★ 5 · AI & Automation · score 76
Install: claude install-skill nawodyaishan/universal-mcp-sync
# Agentic SDD Router Use this skill first for spec-driven development work. It chooses the current phase, loads only the needed phase skill, and prevents accidental jumps from vague intent to code. ## Source Backing This workflow is based on: - Local guide: `/Users/nawodyaishan/Downloads/production-spec-driven-agentic-coding-guide.md` - GitHub Spec Kit workflow: constitution, specify, clarify, plan, tasks, analyze/checklist, implement - OpenAI Codex safety guidance: bounded sandboxing, explicit approvals for high-risk actions, and auditable tool activity ## Phase Map | User intent | Use skill | |---|---| | Set up SDD in a repo | `agentic-sdd-bootstrap` | | Write or improve product intent | `agentic-sdd-spec` | | Resolve unclear requirements | `agentic-sdd-spec` | | Create a technical plan | `agentic-sdd-plan` | | Review plan before coding | `agentic-sdd-architecture-review` | | Break plan into agent tasks | `agentic-sdd-tasks` | | Implement an approved task | `agentic-sdd-implement` | | Verify implementation or review diff | `agentic-sdd-verification-review` | | Detect drift, release notes, retrospective | `agentic-sdd-drift-retro` | ## Required Order For non-trivial production work, enforce this order: ```text bootstrap, if needed -> spec -> clarify, if needed -> plan -> architecture review and approval -> tasks -> implementation -> verification and code review -> drift check, release notes, retrospective ``` ## Routing Rules - If there is no `spec.md` for the req