By nesquikm
Portable skills, agents, and templates that add Spec-Driven Development and TDD workflows to any Claude Code project.
Socratic design session for greenfield features with open solution spaces. Clarifies goals one question at a time, proposes 2-3 approaches with tradeoffs, gets design approval, then feeds into /spec-write.
Structured debugging protocol for failed gate checks, failing tests, or unexpected behavior. Use when /gate-check or /tdd fails and the cause is unclear. Phases: Root Cause → Pattern Analysis → Hypothesis Testing → Implementation.
Run the project gate checks and report results. Use after completing any feature, before creating a PR, or to verify project health.
Implement a feature or fix end-to-end. Analyzes the request, builds in TDD order, runs gate checks, self-reviews with bounded loops, and reports for human approval before committing.
Create a pull request with conventional format. Use when asked to create a PR, open a pull request, or push changes for review.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin that adds Spec-Driven Development (SDD) and TDD workflows to any project. Includes 12 commands, 2 agents, spec templates, and documentation.
/plugin marketplace add nesquikm/dev-process-toolkit
/plugin install dev-process-toolkit@nesquikm-dev-process-toolkit
Then run the setup command in your project:
/dev-process-toolkit:setup
This detects your stack, generates a CLAUDE.md, configures settings, and optionally creates spec files — all adapted to your project.
| Command | Purpose |
|---|---|
/dev-process-toolkit:setup | Set up SDD/TDD process for your project |
/dev-process-toolkit:brainstorm | Socratic design session before writing specs (for open-ended features) |
/dev-process-toolkit:spec-write | Guide through writing spec files (requirements, technical, testing, plan) |
/dev-process-toolkit:implement | End-to-end feature implementation with TDD and two-stage self-review |
/dev-process-toolkit:tdd | RED → GREEN → VERIFY cycle |
/dev-process-toolkit:gate-check | Deterministic quality gates (typecheck + lint + test) |
/dev-process-toolkit:debug | Structured debugging protocol for failing tests or unclear gate failures |
/dev-process-toolkit:spec-review | Audit code against spec requirements |
/dev-process-toolkit:spec-archive | Manually archive a milestone, FR, or AC block into specs/archive/ with diff approval (FR-17) |
/dev-process-toolkit:visual-check | Browser-based UI verification via MCP |
/dev-process-toolkit:pr | Pull request creation |
/dev-process-toolkit:simplify | Code quality review and cleanup |
dev-process-toolkit/
├── .claude-plugin/
│ └── marketplace.json # Marketplace catalog
├── plugins/
│ └── dev-process-toolkit/ # The plugin
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── skills/ # 12 skills (slash commands)
│ ├── agents/ # 2 specialist agents
│ ├── templates/ # CLAUDE.md and spec templates
│ ├── docs/ # Methodology and guides
│ └── examples/ # Stack-specific configs
├── CLAUDE.md
├── README.md
└── LICENSE
See CHANGELOG.md for the full release history. Latest: v1.10.0 — "Bounded Context" (spec archival, /spec-archive skill, stable anchor IDs, specs/archive/ convention).
Three layers prevent AI agents from going off the rails:
The key insight: deterministic checks always override LLM judgment. A failing test means "fix it," not "maybe it's fine."
plugins/dev-process-toolkit/docs/sdd-methodology.md — What SDD is and how it worksplugins/dev-process-toolkit/docs/skill-anatomy.md — How Claude Code skills workplugins/dev-process-toolkit/docs/adaptation-guide.md — Reference for customizing skills and configuration after /setupplugins/dev-process-toolkit/docs/patterns.md — 14 proven patterns + anti-patternsClaude Code official docs: https://code.claude.com/docs/en
npx claudepluginhub nesquikm/dev-process-toolkit --plugin dev-process-toolkitComprehensive AI-assisted development workflow system with specialized agents, orchestrated commands, and file-based state management
SPEC-First development workflow with TDD, Ralph Loop, and autonomous agent coordination for Claude Code
Spec-Driven Development for Claude Code: 17 atomic, stack-agnostic skills + 9 subagents that carry a feature from idea → spec → design → data-model → API → tasks → tests → implement → review → ship, plus a TDD implementation engine and a living roadmap above the per-feature flow. Start with `survey` (maps an existing codebase or bootstraps an empty one), walk the gated backbone — each stage reads the previous artifact and hard-refuses if missing — and keep `docs/roadmap.md` (Now/Next/Later, outcome-altitude, never dates) in sync as `specify` promotes a feature to Now and `ship` moves it to Shipped. The Q&A skills are depth-tunable (easy/medium/hard — decide-for-me vs. interrogate-me-with-trade-offs); the ideation analyses run as named subagents (researcher/strategist/analyst/devil's-advocate) gated by that dial; diagrams are presented in prose and written to file (never raw Mermaid dumped to the terminal); and every acceptance criterion is covered end-to-end. design is surface-aware: it declares the feature's target surfaces at the architecture stage (backend-service / web-frontend / mobile-app / desktop-app / cli / worker / library-sdk, each a C4 container) and downstream stages gate their output by that choice — the `ui` task layer, UI-driven sequence flows, and the component / visual-regression / e2e-through-UI frontend test tiers; `ui` work reuses the repo's existing design system (components / tokens / styling) from the architecture map, never reinvents. Every stage ends with a copy-ready handoff block — what changed, the files to review, then `/clear` + the next `/sdd:…` command.
Persona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
Test-driven development workflow for writing tests before implementation - red-green-refactor cycle with deterministic unit tests