automate-dev

Orchestrates autonomous build-review-test-fix loops with subagents and parallel agent teams for development tasks.

Updated May 20, 2026
One-click install
npx skills add https://github.com/TechCorp25/kingdom --skill automate-dev-techcorp25
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: automate-dev
Source: https://github.com/TechCorp25/kingdom/tree/main/.claude/skills/automate-dev
Command: npx skills add https://github.com/TechCorp25/kingdom --skill automate-dev-techcorp25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Multi-step development work—building features, fixing bugs, refactoring—often ships with regressions, band-aid fixes, and inconsistent quality because review, testing, and validation happen ad hoc. This Skill enforces a disciplined, iterative workflow that loops through analysis, building, review, testing, fixing, and simplification until every quality gate passes. ## Core Features & Use Cases - Iterative Quality Loop: Runs an 8-phase cycle (Analyse, Build, Review, Test, Fix, Simplify, Validate, Ship) that rejects band-aid fixes, breaking changes, and workarounds, iterating until all gates pass. - Multi-Agent Coordination: Delegates work to specialised solo subagents (code-explorer, code-architect, code-reviewer) and escalates to parallel agent teams (team-lead, team-implementer, team-reviewer, team-debugger) via /team-* slash commands for multi-stream or multi-dimensional work. - Automated Quality Scripts: Ships scripts for code review with band-aid detection, fix validation, code simplification, deployment readiness, and token budget monitoring. - Use Case: When asked to implement a new API endpoint, the Skill explores the codebase, designs the architecture, implements the change, runs parallel reviews across security/performance/correctness dimensions, executes tests, fixes root causes of any failures, and only ships once compatibility and quality thresholds are met. ## Quick Start Ask the AI to build, fix, or refactor a feature using the automate-dev workflow and let it iterate until all quality gates pass.

Frequently Asked Questions about automate-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run an autonomous build-test-fix loop for a coding task?▼

Invoke the workflow with a build, fix, or refactor request and it enters an 8-phase loop: analyse, build, review, test, fix, simplify, validate, ship. It iterates up to 10 times until all quality gates pass, rejecting band-aid fixes and breaking changes.

When should I use agent teams instead of solo subagents?▼

Escalate to teams when work splits into 3 or more independent file-ownership streams, needs 4+ review dimensions, or a bug has multiple plausible root causes. Single-file changes and standard 3-dimension reviews are faster with solo subagents.

Does the team coordination mode require special setup?▼

Yes, team mode requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in the environment and a teammateMode setting in ~/.claude/settings.json. Solo subagent modes work without any special configuration.

What counts as a band-aid fix that gets rejected?▼

Rejected patterns include swallowed exceptions, try/except pass blocks, commented-out failing code, hardcoded workarounds, conditional branches skipping broken paths, and noqa or type-ignore suppressions used as the fix itself.

How are token costs controlled during long workflows?▼

The token_budget_monitor.py script enforces per-phase, per-agent, and total task budgets with alerts at 50%, 75%, and 90% thresholds. Team mode multiplies phase budgets by team size, and the 90% threshold halts new parallel launches.