spec-driven-build

Coordinate multi-phase feature development across isolated git worktrees with subagents and build checks.

2|Updated Aug 1, 2024
One-click install
npx skills add https://github.com/Kabilan108/dotfiles --skill spec-driven-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-driven-build
Source: https://github.com/Kabilan108/dotfiles/tree/main/agents/skills/spec-driven-build
Command: npx skills add https://github.com/Kabilan108/dotfiles --skill spec-driven-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The spec-driven build orchestrator coordinates multi-phase feature development by managing isolated git worktrees and coordinating subagents.

Core Features & Use Cases

  • Orchestrates phase-based work across isolated worktrees to ensure clean merges and reproducible results.
  • Launches and monitors subagents via tmux panes, enabling parallel phase execution and centralized task tracking.
  • Supports end-to-end verification including merges, lint/build checks, and visual QA against the spec.

Quick Start

  1. Initialize a base environment from the repository and create isolated worktrees for each phase.
  2. Launch subagents in tmux panes and supply Phase tasks via the orchestrator prompts.
  3. Monitor TaskUpdate results and perform merges once phases complete; verify with the visual test plan.

Frequently Asked Questions about spec-driven-build

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

FAQPage Schema
How do I orchestrate multi-phase feature development using isolated git worktrees?

Multi-phase feature development is orchestrated by creating isolated git worktrees for each phase, launching subagents in tmux panes for parallel execution, and performing controlled merges upon task completion.

How does subagent orchestration work with tmux for parallel builds?

Subagent orchestration with tmux launches phase-specific subagents into separate tmux panes, enabling parallel execution and centralized task tracking while enforcing file boundaries and monitoring task status updates.

Do I need a detailed spec to start a multi-phase build with subagents?

A detailed spec is required to start a multi-phase build, as it provides the phase tasks supplied to subagents and defines the visual verification and lint checks needed for controlled merges.

What is the best way to manage controlled merges and visual verification across build phases?

Controlled merges and visual verification are managed by monitoring TaskUpdate results from subagents, performing lint and build checks, and validating outputs against the spec's visual test plan before finalizing merges.

Can I enforce file boundaries when running parallel subagents in different worktrees?

File boundaries are enforced during parallel subagent execution by the orchestrator, ensuring each phase operates within its isolated git worktree to prevent conflicts and maintain reproducible results.

Why use git worktrees for multi-phase builds instead of a single working branch?

Git worktrees are used for multi-phase builds to isolate phase execution, ensuring clean merges and reproducible results without branch contention, while subagents operate independently within their designated worktree.