Menu
Verify implementation and review code against the approved SDD spec, plan, tasks, contracts, and constitution.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when adding a new MCP server provider to usync. Triggers: "add a new provider", "add provider X", "scaffold provider", "support <NAME> MCP", "register an MCP server". Walks through official doc lookup, scaffolding, registration, header dispatch, QA scenarios, and documentation updates.
PROJECT-SPECIFIC to usync (mcp-config-tui). Use when iterating on TUI UI/UX bugs via the Docker-first bug-hunt harness. Triggers: "UX bug hunt", "iterate on UI bugs", "fix UX issues", "expand the matrix", "ux-fake-prod", "matrix scenario", "TUI regression", "DM-P<n>". Drives the 4-stage loop (expand → run → triage → fix+lock) and the lens framework for catching UX defect classes beyond functional bugs.
Review an SDD implementation plan before code generation and decide whether it is approved, needs changes, or is rejected.
Initialize or upgrade a repository for production spec-driven development with constitution, templates, review checklists, and tool memory pointers.
Detect spec drift, prepare release notes, and write retrospectives after SDD implementation or review.
Implement one approved SDD task inside strict file, safety, and verification boundaries.
| name | agentic-sdd-verification-review |
| description | Verify implementation and review code against the approved SDD spec, plan, tasks, contracts, and constitution. |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash, web_search_advanced_exa, web_fetch_exa |
| risk | safe |
| source | local |
Use this skill after implementation and before merge or release.
Prove the implementation matches the approved artifacts and is safe to review or merge.
.specify/memory/constitution.mdspecs/<feature>/spec.mdspecs/<feature>/plan.mdspecs/<feature>/tasks.mdspecs/<feature>/test-plan.md, if presentspecs/<feature>/contracts/, if presentRun applicable checks when available:
Do not claim success for checks that were not run.
Assess:
Use this structure:
Status: Approved | Needs changes | Blocked
Blocking findings:
- file:line - issue
Non-blocking suggestions:
- file:line - suggestion
Verification:
- command - passed/failed/not run, reason
Spec drift:
- none found
- or required artifact updates
Do not approve when:
If requested, update:
specs/<feature>/review.mdspecs/<feature>/test-plan.mdspecs/<feature>/drift-report.md