nawodyaishan

agentic-sdd-architecture-review

Review an SDD implementation plan before code generation and decide whether it is approved, needs changes, or is rejected.

agentic-sdd-bootstrap

Initialize or upgrade a repository for production spec-driven development with constitution, templates, review checklists, and tool memory pointers.

agentic-sdd-implement

Implement one approved SDD task inside strict file, safety, and verification boundaries.

agentic-sdd-plan

Produce a technical implementation plan from an approved SDD spec without editing product code.

Create or improve spec-driven development artifacts using local source docs plus current Exa research. Use for SDD planning, gap analysis, documentation upgrades, architecture specs, task breakdowns, and docs-only preparation before implementation.

agentic-sdd-router

Route spec-driven development work to the correct phase skill. Use when the user asks for SDD, spec-driven development, Spec Kit style workflow, feature planning, implementation from specs, verification, or spec drift review.

agentic-sdd-spec

Create or refine SDD feature, bug-fix, refactor, or migration specifications with clarification handling before technical planning.

agentic-sdd-verification-review

Verify implementation and review code against the approved SDD spec, plan, tasks, contracts, and constitution.

agentic-sdd-drift-retro

Detect spec drift, prepare release notes, and write retrospectives after SDD implementation or review.

agentic-sdd-tasks

Break an approved SDD plan into small, bounded, independently verifiable implementation tasks.

Code & Development Listed

add-provider

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.

Web & Frontend Listed

ux-bug-hunt

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.