dev-builder

Implements DEV-PLAN phases one at a time with TDD, sub-agent isolation, and four-step verification.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill dev-builder-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-builder
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/dev-builder
Command: npx skills add https://github.com/iJosueeh/amauta --skill dev-builder-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a development plan into working code often drifts: phases balloon in scope, tests get skipped, and verification is claimed without evidence. This Skill enforces a disciplined, phase-by-phase implementation workflow so each DEV-PLAN phase ships verified, committed code. ## Core Features & Use Cases - Three execution modes: Initialization Mode scaffolds greenfield projects from a tech stack table, Continuous Development Mode implements one phase per invocation, and Change-Scoped Mode executes only unchecked tasks from a change directory. - Enforced engineering discipline: TDD red-green-refactor per task, mandatory implementer sub-agent isolation with git worktrees, two-tier code review, and a four-step phase verification (review, completeness, compilation, functional testing) with retry limits and escalation. - Quality gates and memory: A 20-point quality rubric, anti-rationalization and anti-AI-slop checklists, atomic git commits, and persistent memory files (task history, decision logs, project memory) updated after every task. - Use Case: A team has a Product-Spec.md and DEV-PLAN.md for a web app. Invoking the skill scaffolds the project skeleton in Phase 1, then each subsequent invocation implements exactly one phase with tests, review, and evidence-backed verification before stopping. ## Quick Start Ask the AI to run /dev-builder to start coding the next phase defined in your DEV-PLAN.md.

Frequently Asked Questions about dev-builder

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

FAQPage Schema
How do I implement a development plan phase by phase with an AI coding agent?▼

Create a DEV-PLAN.md with phased delivery checklists, then invoke the dev-builder skill once per phase. Each invocation plans tasks, implements them with TDD, runs code review, and verifies with a four-step process before stopping.

What files are required before starting phase-based development?▼

You need Product-Spec.md and DEV-PLAN.md at the project root. If either is missing, the skill prompts you to run the product-spec-builder or dev-planner skills first. Design-Brief.md and design tool integrations are optional.

Can dev-builder implement multiple phases in one invocation?▼

No. The skill enforces a strict one-phase-per-invocation rule with a force stop after verification. Even if asked to continue, it requires a new invocation for the next phase to keep scope controlled and context clean.

How does the skill handle verification failures during a phase?▼

Failed verification restarts the full four-step check from step one, tracked by a retry counter. After three failed cycles it escalates to the user with options to fix manually, skip the task, or adjust the approach.

Does dev-builder support test-driven development workflows?▼

Yes. TDD is mandatory: every task follows red-green-refactor, executed by an isolated implementer sub-agent inside a git worktree. The main session never writes business code directly and only commits after review passes.

When should I use bug-fixer instead of dev-builder?▼

Use bug-fixer for fixing defects in existing code and code-review for quality audits. Dev-builder is only for implementing planned phases or change-scoped tasks from a DEV-PLAN, not for unplanned fixes or reviews.