Spec-Anchored Agentic Development — methodology + ready-to-install Claude Code bundle: one permanent spec per capability, machine gates before human review, autonomy as an evidence-gated gradient
Use when the reviewer subagent is reviewing a diff that implements work defined by a capability spec or an approved plan (protocol Phase 3). Checks two things: does the diff do what the spec requires, and does the diff do what the approved plan said it would. Catches silent drift between intent and implementation.…
Use when the reviewer subagent is reviewing a diff that touches a domain rule, a calculation, a sensitive numeric value, the audit trail, source-of-rule attribution, stage/responsibility boundaries, or past-period rules. Checks the diff against the system constitution (architecture/constitution.md). This is the…
Use when the reviewer subagent is reviewing a diff for correctness/logic, simplicity/reuse, test quality, or type design — the default reviewer dimension for the implement-feature and implement-backlog loops. Domain-rule, audit-trail, and spec-conformance concerns are NOT here — route those to…
EXPLICIT INVOCATION ONLY — run via /implement-backlog or when the user names this skill. Unattended adapter of the shared implementation protocol: autonomous loop over increment issues (bugfix, tech-debt, rule adjustment, reference-data update proposals, feature-within-scope). New capabilities and large features are…
EXPLICIT INVOCATION ONLY — run via /implement-feature or when the user names this skill. Never auto-trigger on general coding requests. Supervised-local adapter of the shared implementation protocol: code work from existing ratified specs, issues, or backlog items, with the human in the session satisfying every gate.
EXPLICIT INVOCATION ONLY — the orchestrated-worker adapter of the shared implementation protocol. Invoked as the FIRST MESSAGE of an Orca child worker: /implement-orchestrated issue # --mode assisted|autonomous. One ticket, one worktree, one PR. Never auto-trigger; never use for local supervised work.
Reviews implementation plans before any code is written. Use when the reviewer subagent is judging whether a plan's approach/architecture is sound — approving it or sending it back with approach-level concerns. Used by implement-backlog (Phase 2, as the gate that replaces the human) and available to implement-feature…
Review tickets (GitHub issues) as executable contracts before dispatch — self-containedness, criteria pointed at the spec, explicit scope and dependencies, size, test scenarios, risk notes. Report-only, [BLOCKER]/[SHOULD]/[NIT]. Use on a generated batch before the quiz (/spec-to-tickets) and before scheduling waves…
★not rated 5 9d agoA80 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: