Menu
Detect spec drift, prepare release notes, and write retrospectives after SDD implementation or review.
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.
Implement one approved SDD task inside strict file, safety, and verification boundaries.
Produce a technical implementation plan from an approved SDD spec without editing product code.
| name | agentic-sdd-drift-retro |
| description | Detect spec drift, prepare release notes, and write retrospectives after SDD implementation or review. |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
| risk | safe |
| source | local |
Use this skill after implementation, before release, or when a diff may have changed behavior without matching artifacts.
Keep code, specs, plans, contracts, ADRs, tests, and release notes aligned.
specs/<feature>/spec.mdspecs/<feature>/plan.mdspecs/<feature>/tasks.mdspecs/<feature>/test-plan.md, if presentspecs/<feature>/contracts/, if presentdocs/release-notes/.specify/memory/constitution.mdFlag drift when:
Create or update specs/<feature>/drift-report.md with:
Create or update docs/retrospectives/<date>-<feature>.md with:
For user-facing changes, create or update docs/release-notes/<release-or-date>.md with:
Return drift status, files updated, release-note status, retrospective path, and recommended process improvements.