dev-builder

Implements project phases from DEV-PLAN.md with per-task review cycles and four-step verification.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill dev-builder-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-builder
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/.agents/skills/dev-builder
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill dev-builder-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a development plan into working code often drifts: tasks get skipped, reviews are skipped, tests pass on paper while features break, and code diverges from the spec. This Skill enforces a disciplined, phase-by-phase implementation workflow driven by DEV-PLAN.md and Product-Spec.md. ## Core Features & Use Cases - Dual-mode execution: Bootstraps a new project skeleton (dependencies, TypeScript strict, git init) when no code exists, or continues phase-by-phase development on an existing codebase. - Per-task review loop: Every task goes through a two-stage code-reviewer cycle with fix iterations, followed by atomic commits with conventional prefixes. - Four-step phase verification: Code review against the delivery checklist, test completeness checks, tsc --noEmit compilation, and live functional testing with evidence attached to every claim. - Use Case: You have a Product-Spec.md and DEV-PLAN.md for a Tauri desktop app. Invoke this Skill to scaffold the project, then implement Phase 1 task by task with automated review and verified completion evidence. ## Quick Start Start building the next phase of my project according to DEV-PLAN.md, running the review and verification steps for each task.

Frequently Asked Questions about dev-builder

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

FAQPage Schema
How do I start coding from a development plan with an AI agent?▼

Provide a DEV-PLAN.md and Product-Spec.md, then invoke the dev-builder skill. It detects project state, scaffolds the skeleton if no code exists, and implements each phase task by task with review and verification loops.

How does the per-task review and fix cycle work?▼

Each task is coded, self-checked against the spec and design values, then sent to a two-stage code-reviewer. Stage failures trigger fixes and re-review; only after both stages pass does the skill commit and move to the next task.

What documents are required before using this development workflow?▼

Product-Spec.md and DEV-PLAN.md are mandatory, along with the toolchain listed in the plan's tech stack table. Design-Brief.md, design tool MCP, gh CLI, and Playwright are optional and trigger degraded modes when missing.

How is a development phase verified as complete?▼

Completion requires a four-step gate: code review against the delivery checklist, test completeness covering interaction and failure paths, tsc --noEmit with zero errors, and live functional testing. Each step must include freshly run evidence.

Can it handle changes to requirements during development?▼

Yes. When the user changes requirements or design mid-development, the skill routes back to the spec or design documentation first, then continues coding so code and documents never diverge.