Agent skills for a gated development cycle on top of dev.mcp. The server exposes Figma, Jira, Confluence, and GitLab tools; this repo is the workflow — gates, evidence, and steps. Without a ready dev.mcp server, skills stop at Step 0. The server alone does not enforce that workflow.
dev-cycle only routes to the manual cycles. Invoke dev-feature-cycle or dev-bug-cycle directly when the type is already clear. Invoke dev-feature-agent or dev-bug-agent when the cycle should decide on its own and stop before ship.
Feature (spec-driven) — what new behavior must exist, why, and how to prove it was delivered:
dev-feature-intake (one gap round) → dev-specify → (dev-design / dev-tasks when large, high-risk, or UI) → dev-execute → dev-verify-feature → dual review → dev-ship
Bug (root-cause-first) — why observed diverges from expected, and the smallest proven fix of the cause:
dev-bug-intake (one gap round) → dev-reproduce-bug → dev-debug → dev-fix-bug → dev-verify-bug → dual review → dev-ship
Agentic — the same sequences. The intake gap round is the only question. Later gates are decisions from ## Decisions and the surrounding evidence. The run stops with a ship briefing; it does not call dev-ship.
Bugs do not go through spec/design/tasks. Features do not treat dev-debug as a default step (only if a task fails). Independent verification (author ≠ verifier) and evidence-or-zero apply to both. UI fidelity uses the Figma screen visual contract (fixed size, absolute position, complex styles), not a spec-sheet and not a generic component.
A finished manual step ends with Next skill: \dev-...``. The question prompt stays a one-line placeholder; the Gate briefing (artifact path and summary) is in the chat message before it.
- Clone next to dev.mcp.
- Configure the server in your MCP host (
envholds tokens — never this repo). See the server README for client configs. - Follow INSTALL.md to link
dev-*skills into the host skill path. - Confirm a ready MCP server named
dev.mcp(hosts may prefix the name). - For shared use, pin a SemVer tag;
mainmay change gates and artifacts.
Python 3 is the only skill runtime. No installer daemon.
| Skill | Role |
|---|---|
dev-shared |
MCP bind, gates, allowlists, parser, state |
dev-cycle |
Feature × Bug router (manual cycles only) |
dev-feature-cycle |
Feature orchestrator |
dev-feature-agent |
Feature orchestrator that decides and stops before ship |
dev-bug-cycle |
Bug orchestrator |
dev-bug-agent |
Bug orchestrator that decides and stops before ship |
dev-feature-intake |
Target, Jira/Figma/GitLab, risk |
dev-specify |
Traceable requirements |
dev-design |
Technical surface + spec vs screen inventory |
dev-tasks |
Atomic tasks |
dev-execute |
Local implementation against spec/screen |
dev-verify-feature |
Fresh feature verifier |
dev-bug-intake |
Symptom, severity, target |
dev-reproduce-bug |
Required reproduction |
dev-debug |
Root cause (read-only) |
dev-fix-bug |
RED test + minimal patch |
dev-verify-bug |
Fresh bug verifier |
dev-mr-guided-review |
Code review (read-only) |
dev-qa-guided-review |
QA AC × Figma × integration (read-only) |
dev-fix-reviews |
Closes confirmed gaps |
dev-ship |
MR / Jira after Gate S |
Git-native memory under .dev/features/<slug>/ (feature) and .dev/bugs/<slug>/ (bug). Dual-review reports stay in chat and include a Completeness profile; reviews/round-NNN.md stores only confirmed findings, and reviews/readiness.md stores each review’s verdict, open-row count, and reviewed commit for dev-ship.
- Intakes, planning, reproduce, debug, verify, reviews, and both agent orchestrators: absolute MCP write denylist.
dev-execute/dev-fix-bug/dev-fix-reviews: working tree + local commits.dev-ship:gitlab_save_merge_requestand, if Gate S authorizes, Jira comment/transition/link. Never accept an MR or force-push.