Structured agent workflow harness — investigate, plan, review, implement, learn. Convention-driven, with dynamic reviewer discovery and standard project conventions.
Stateless executor for a single plan step. Writes tests and code, runs tests, returns a structured report. Workers do not loop, commit, or spawn other agents.
Reads the issues journal, triages each issue, and applies documentation improvements — updates existing docs, fixes discoverability, routes tangential ideas to the project backlog, or creates rare standalone learnings
Explores the current codebase to understand project state, find relevant files, and identify patterns
Reads project documentation and learnings to find guidance relevant to the current task
Fetches current documentation for frameworks and libraries used in the project
Check an existing project for harness readiness — find missing convention files, CLAUDE.md sections, build recipes, and reviewer agents. Interactively scaffold the gaps. Use when the user wants to check project setup, onboard a project into the harness, verify readiness, or asks "is the project set up correctly".
Guide a user through setting up a new project from scratch — discover intent, identify needed documents, create them collaboratively, then scaffold the repo and agent harness. Use when starting from scratch, creating a new repo, bootstrapping a project, or the user says "new project" or "set up a project".
Help the user move from a vague problem, observation, or half-formed solution to a concrete next step. Use when the user wants to explore what to build, sanity-check an idea, dig into the problem behind a proposed solution, or work through phrasings like "I'm thinking about...", "we should consider...", "would it be a good idea to...", "what if we...", "I have an idea for...". Output is 1-3 concrete options or a clear "drop this" recommendation, not a PRD or implementation.
Execute an approved implementation plan — dispatch per-step work to stateless implement-worker subagents, manage commits, run review checkpoints. Adapts to the workflow mode (minimal, light, full).
Gather context for a task and propose what to work on. Either picks the next item from the project plan, or scopes a user-provided task. Use when the user asks what to work on next, wants to pick a task, or hands you a specific task description.
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 structured agent workflow harness for Claude Code. Provides skills and agents for investigating tasks, planning, reviewing, implementing, and learning from completed work.
The plugin provides a full development workflow:
Plus supporting skills:
| Skill | Purpose |
|---|---|
/dev:next [task] | Run the workflow for the next plan item, or for a task description given as argument |
/dev:ideate | Turn a vague problem or half-formed idea into a concrete next step |
/dev:investigate | Propose the next task to work on (from plan or from argument) |
/dev:plan | Create planning documents (light: plan only; full: PRD + plan) |
/dev:review-plan | Review a plan with all discovered reviewers (full mode by default; opt-in from light mode) |
/dev:implement | Execute an approved plan with mode-appropriate review checkpoints |
/dev:review-impl | Review implementation code with all discovered reviewers |
/dev:learn | Process the issues journal into doc improvements |
/dev:prepare-pr | Clean up history, push, and create a PR |
/dev:greenfield | Bootstrap a new project with standard conventions |
/dev:audit | Check harness readiness and scaffold missing pieces |
Always applicable:
Stack-specific:
The plugin's reviewers run by default in any consuming project (no copy needed). A
project can add its own reviewers under .claude/agents/review/ — same-name files
override the plugin reviewer; differently-named files are additive. To drop a plugin
reviewer entirely without replacing it, list its name under a ## Disabled reviewers
section in the project's CLAUDE.md. Each reviewer reads project-specific criteria
from .claude/conventions/ files.
/dev:next invokes downstream skills (/dev:plan, /dev:review-plan,
/dev:implement, /dev:review-impl) via the Skill tool. Skill runs the
called skill body in the caller's context (no subagent boundary), so the
chain stays in the orchestrator's window. Each skill body then Agent-spawns
its workers and reviewers — a single depth-1 spawn from the orchestrator,
which is the depth Claude Code currently supports reliably.
# Add the marketplace
claude plugin marketplace add BalduinLandolt/dev-claude-plugin
# Install the plugin
claude plugin install dev@dev-claude-plugins
Or add to your project's .claude/settings.json:
{
"enabledPlugins": {
"dev@dev-claude-plugins": true
},
"extraKnownMarketplaces": {
"dev-claude-plugins": {
"source": {
"source": "github",
"repo": "BalduinLandolt/dev-claude-plugin"
}
}
}
}
The plugin expects consuming projects to provide:
npx claudepluginhub balduinlandolt/dev-claude-plugin --plugin devHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
AI-powered development tools for code review, research, design, and workflow automation.
Superpowers Plus core skills library for Claude Code: planning, execution routing, TDD, debugging, and collaboration workflows
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Claude harness - A harness for solo developers (Vibecoders) to handle full-cycle contract development.