final-review
01Skill Claude CodeCodex
Use before handing off an implementation to compare the diff against the spec, tests, docs, contracts, and safety rules.
Skill Claude CodeCodex
Use before handing off an implementation to compare the diff against the spec, tests, docs, contracts, and safety rules.
Skill Claude CodeCodex
Use when a stakeholder request is rough, ambiguous, or underspecified and needs clarification before planning, writing a spec, or creating issues.
Skill Claude CodeCodex
Use after synthesis to dispatch the next ready task from the TASKS.md ledger through one subagent-driven implementation cycle, one task per invocation.
Skill Claude CodeCodex
Use after a grill-change session is complete to turn the agreement record into an intent-first spec candidate and vertical TDD-ready issue briefs.
Skill Claude CodeCodex
Use when implementing a meaningful repository change that requires an approved spec before code edits.
Skill Claude CodeCodex
Use when a scoped implementation can be delegated to an implementation subagent and then independently reviewed for spec compliance before code quality.
Skill Claude CodeCodex
Use when changing behavior where a focused failing test or golden fixture must prove RED before implementation and GREEN after the minimal fix.
Agent Claude Code
Independently review the complete accumulated change and reachable consumers for product-risk gaps.
Agent Claude Code
Use only after spec review passes to assess maintainability, decomposition, tests, naming, risky mocks, and local code quality in the changed files. Reads code and docs only; does not edit.
Agent Claude Code
Use for a bounded implementation task after the parent agent has provided the full task text, relevant spec excerpts, file ownership, constraints, and expected tests. Returns an explicit status and does not commit or push unless the parent request includes that requirement.
Agent Claude Code
Use after an implementation worker reports DONE or DONEWITHCONCERNS to verify the actual changed files against the task text, approved spec, acceptance criteria, and claimed result. Reads code and docs only; does not edit.
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: