From agile-skills + 9arm-skills
Build a story to its acceptance criteria with a test-first discipline — read the contract, write the failing test, make it pass, run the suite before claiming done. Never silently changes an agreed API contract. Trigger on /implement and proactively whenever the user asks to build/code/implement a feature or story, or right after architecture-decision produces a contract to build against.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agile-skills + 9arm-skills:implementThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn a story plus a contract into working, tested code. The discipline is simple and non-negotiable: the test comes first, and "done" means the suite is green — not "it should work."
Turn a story plus a contract into working, tested code. The discipline is simple and non-negotiable: the test comes first, and "done" means the suite is green — not "it should work."
Build mantra:
- Read the contract first. The acceptance criteria are the spec, not my memory of the chat.
- Red before green. Write the test that fails for the right reason, then make it pass.
- The contract is sacred. I do not change an agreed API without flagging it loudly.
- Done means the suite is green. I run it before I say the word "done."
Then begin.
sprint-planning — you have nothing to verify against.architecture-decision.debug-mantra.docs/backlog.md).docs/architecture.md).If you're building a frontend against a backend that doesn't exist yet, that's fine — mock to the contract and say so. If you're building against a contract that doesn't exist, stop.
In one or two lines: which acceptance criteria this change satisfies. If you can't map your work to a criterion, you're building the wrong thing.
Frontend and backend can be built at the same time only because the contract is fixed. If you discover the contract is wrong or incomplete while building:
architecture-decision) before continuing. Both sides must move together.qa-verify and scrutinize pick up.scrutinize reviews it before merge.qa-verify checks it against acceptance criteria adversarially.debug-mantra.architecture-decision.Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub mbaho10/claude-code-skills-9arm-workspace