Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From Agentic SDD (Spec-Driven + TDD)
Use when starting any non-trivial feature or change, to run the Spec-Driven Development loop — write a testable spec, derive tests, implement, and verify against the spec. Trigger on "spec", "SDD", "new feature", "requirements", or when work should start from a written contract rather than ad-hoc coding.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-sdd:spec-driven-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The spec is the source of truth. Tests encode the spec; code satisfies the tests. Work flows in one direction and every step traces back to a numbered acceptance criterion.
The spec is the source of truth. Tests encode the spec; code satisfies the tests. Work flows in one direction and every step traces back to a numbered acceptance criterion.
architect agent first to produce docs/design/<feature>.md and ADRs.spec-writer produces specs/<feature>.spec.md: summary, user stories, functional + non-functional requirements, numbered Given/When/Then acceptance criteria (AC-n), edge cases, out-of-scope, and a Definition of Done.tdd-test-writer turns each AC-n into failing tests that reference the AC id. Confirm they fail for the right reason.implementer writes the minimum clean code to pass.e2e-tester covers the criteria marked "needs E2E" through real interfaces.code-reviewer checks AC coverage, clean code, security, performance.AC-n maps to a passing test; the Definition of Done is met.See references/spec-template.md for the canonical structure. Place specs in specs/, designs in docs/design/, decisions in docs/adr/.
npx claudepluginhub walmanarias/agentic-workflow --plugin agentic-sddProvides behavioral guidelines to reduce common LLM coding mistakes, focusing on simplicity, surgical changes, assumption surfacing, and verifiable success criteria.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.