Dev Workflows
Stack-agnostic, intent-based spec-driven-development workflows for Claude Code. The same
skills work on any stack (Next.js + Supabase, React + Vite, Rails, …) because everything
stack-specific lives in a per-project stack profile (docs/stack.md) that the skills read
at runtime instead of hardcoding a framework or build command.
Skills
| Skill | Use when… |
|---|
/feature | Build a new feature end-to-end (brainstorm → grill → spec → clarify → plan → tasks → analyze gate → worktree → TDD build with per-task review → /code-review gate → e2e smoke → PR). |
/improve | Change/extend an existing feature that works as specified. Amends the spec first, then a scope-matched build with the /code-review gate (T2/T3) before PR. |
/troubleshoot | Fix a bug you hit while manually testing. Root-cause gate (no fix before root cause) → test-first fix → /code-review gate → PR. |
/grill-me | Stress-test a plan/design — relentless one-decision-at-a-time interview via AskUserQuestion. Used as a gate by /feature and /improve. |
e2e-smoke | (internal) Real-browser smoke gate invoked by the three workflows. Returns PASS/FAIL/BLOCKED. |
/spec /plan /tasks /implement | Thin entry points that defer to your spec layer (GitHub Spec-Kit if installed, plain markdown, or none). |
/analyze /checklist /tasks-to-issues | More spec-layer entry points. /analyze = read-only cross-artifact consistency check (spec vs plan vs tasks) before coding — built into /feature (§4b) and /improve (§3b). /checklist = requirements-quality checklist ("unit tests for the English") for a risk dimension. /tasks-to-issues = export tasks.md to GitHub issues for human/distributed tracking (an alternative to the in-session build loop, not a step in it). |
/pr | Get the current branch's work onto the right PR: checks the live PR status, rebases onto base, resolves conflicts, verifies, and pushes (--force-with-lease). Updates the open PR, or opens a new one if the branch's PR was already merged. |
/projectstatus | Where are we / what's next? Spec-progress snapshot — reads the spec layer from the stack profile, reports per-milestone progress, flags blockers, and recommends the single next action. Read-only. |
/projecthealth | Is it green & deployable? Operational snapshot — git working tree, open PRs + CI, and [VERIFY] quality gates always; plus DB migrations/advisors, deploys, and prod drift when the stack profile declares them. Read-only, red-first verdict. |
/writing-skills | Author or update the skills in this repo using TDD-for-skills (RED baseline → GREEN minimal skill → REFACTOR to close loopholes). Vendored from Superpowers — see skills/writing-skills/ATTRIBUTION.md. |
Routing in one line: new feature → /feature · change a working feature → /improve · wrong/broken behavior → /troubleshoot · where are we / what's next → /projectstatus · is it green/deployable → /projecthealth.
/projectstatus and /projecthealth are the two status lenses — progress vs.
operational health. Both are read-only and both read the stack profile (the spec layer
and the optional Health / operations section, respectively), so the same skills work
on any stack: a project with no DB/deploy/specs simply gets the always-on signals and
n/a for the rest.
The line between /improve and /troubleshoot
/improve = change correct behavior (add/extend/modify a feature that works as specified)./troubleshoot = fix incorrect behavior (wrong value, broken interaction, error — or known-bad-by-design code like a hardcoded auth bypass).
Install (from GitHub)
This repo is a Claude Code plugin marketplace. Add it once, then install the plugin:
# 1. Register this repo as a marketplace (use your repo's URL)
claude plugin marketplace add miroo93/dev-workflows
# …or the full URL:
# claude plugin marketplace add https://github.com/<you>/dev-workflows
# 2. Install the plugin from it
claude plugin install dev-workflows@dev-workflows
The two dev-workflows are <plugin-name>@<marketplace-name> — both happen to be named
the same here. Run these from inside the project where you want the skills (installs to
the project), or with --scope user to make them available everywhere.
Install the prerequisites too (see below) — at minimum superpowers.
Keeping projects up to date
Push updates to this repo, then in each consuming project:
claude plugin marketplace update dev-workflows # pull the latest marketplace + plugin
claude plugin update dev-workflows # apply the new version
