By A7um
Coordinate agent teams through structured auto-dev workflows: define requirements, configure environments, generate code, triage issues, and simulate user testing via composable skills and contracts.
Configure a runnable development environment for the current repo or a specified repo using the bundled Auto-env skill
Add a single component — lightweight workflow for well-scoped additions
Enhance existing code — impact-analysis-driven workflow
Fix a bug — hypothesis-driven diagnosis and minimal surgical fix
Greenfield development — full architecture design before implementation
Composable development workflow system. Phases define reusable steps; paradigms compose them into ordered sequences. Four paradigms cover greenfield, enhancement, bugfix, and addition task types.
Configure runnable development environments for repositories using repo inspection, targeted environment-variable discovery, Docker or local setup, and smoke-test evidence. Use this skill whenever the user asks to set up a repo, make a project runnable, configure environment variables, prepare a Docker/dev environment, create a shell/run contract for another agent, or unblock downstream E2E verification.
Requirements elicitation skill. Turns vague human intent into structured, actionable specifications that downstream skills can consume.
Simulated user testing skill. Provisions environments, exercises software through persona-driven interaction, and produces structured feedback.
Issue intake and prioritization skill. Classifies, deduplicates, and dispatches work items from raw issues.
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.
An agent-majority software organization in a plugin. Humans supply requirements and intervene at key decision points. Agents handle everything else — building, testing, triaging — through structured skills that make each role produce high-quality output in one go, without standing human review.
Human Sponsor
│ requirements
▼
┌─────────┐ structured spec ┌──────────┐
│ auto-req │ ──────────────────► │ auto-dev │
└─────────┘ └────┬─────┘
│ artifact
▼
┌──────────┐
│ auto-test│
└────┬─────┘
│ issues
▼
┌───────────┐ work items ┌──────────┐
│auto-triage│ ────────────────►│ auto-dev │
└───────────┘ └──────────┘
│
▼
(loop)
The human re-enters at escalation points: ambiguous requirements, conflicting priorities, policy decisions, or repeated quality gate failures.
This plugin defines the skills and contracts for that loop. It does not orchestrate it — an external system (or a coordinator agent in a separate repo) handles spawning, polling, and state management.
Each role is a directory with SOUL.md (identity and behavioral posture) and AGENTS.md (operational protocol and interfaces), following the Hermes/OpenClaw convention. USER.md at the repo root describes the human sponsor.
| Role | Skill | What they do | Defined in |
|---|---|---|---|
| Human sponsor | — | States requirements, answers escalations, sets priority | USER.md |
| Req agent | auto-req | Elicits, structures, and validates requirements from vague input | roles/req-agent/ |
| Dev agent | auto-dev | Classifies tasks, follows paradigms, ships verified code | roles/dev-agent/ |
| User agent | auto-test | Exercises software as a simulated end user, files feedback | roles/user-agent/ |
| Triage agent | auto-triage | Deduplicates, classifies, prioritizes, dispatches work items | roles/triage-agent/ |
auto-dev uses software engineering discipline and test-driven verification to make coding agents produce high-quality code in one go, without human review or intervention. Every task goes through a mandatory design-thinking phase (architecture for greenfield, impact analysis for enhancements, hypothesis-driven diagnosis for bugs) before any code is written. This forces the agent to understand the problem deeply enough to get it right the first time. Test-plan-driven development (TPDD) defines what "correct" means before implementation — Must Have checkpoints, integration boundaries, and Forbidden Zone redlines give the agent concrete, verifiable success criteria it can check autonomously. Quality gates at every phase boundary replace the human reviewer: the agent self-assesses against objective criteria and escalates only when something doesn't fit. The result is code that passes its own review — designed, implemented, reviewed, and verified — delivered without the human ever needing to read a line.
auto-test makes user agents exercise software the way real people do, not the way engineers verify it. It provisions a Docker environment with the right interaction toolkit (Playwright for web, shell for CLI, HTTP client for APIs), assigns the agent a persona with specific goals and patience limits, and runs a perception-action loop — observe the screen, decide what to do, act, record what happened. Friction is signal: confusion, slowness, missing affordances, and broken flows all become structured bug reports and feature requests that a dev agent can act on without asking for clarification. The persona system prevents the agent from over-testing: a novice gives up when confused, a power user pushes through, an adversarial tester probes boundaries.
npx claudepluginhub a7um/zero-review --plugin zero-reviewPersona-driven AI development team: orchestrator, team agents, review agents, skills, slash commands, and advisory hooks for Claude Code
Production-grade engineering skills for AI coding agents — covering the full software development lifecycle from spec to ship.
Self-orchestrating multi-agent development system powered by Claude Fable 5 — 15 agents (8 core + 1 security gate + 6 department), Smart Routing default, token-efficient subagents, risk-based quality gates. You say WHAT, the AI decides HOW.
An agent-routed harness for end-to-end software product development
127-agent automated development system with Agent Teams, quality gates, Bug Council diagnostics, and autonomous execution
Multi-agent orchestration framework for Claude Code, Gemini CLI, and Codex CLI — 19 agents, 14 skills, 16 commands, quality gates, TDD enforcement