skills.rest
Claudfather
ClaudfatherOFFICIAL
Explore all skills by this author →
WebsiteGitHub

build-all

Executes ordered multi-phase plan docs as one governed sprint with cross-phase state tracking.

Updated May 3, 2026
Search Tags:#git workflow#ci cd#epic execution#multi-phase build#sprint ledger#merge topology#review convergence
One-click install
npx skills add https://github.com/Claudfather/clauDNA --skill build-all-claudfather
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: build-all
Source: https://github.com/Claudfather/clauDNA/tree/main/skills/build-all
Command: npx skills add https://github.com/Claudfather/clauDNA --skill build-all-claudfather

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing an epic that spans multiple phase docs, PRs, and repos often fails in predictable ways: invariants drift between repos, stacked branches conflict after squash merges, review findings get fixed instance-by-instance instead of by class, and merged code is reported as live when deploys are manual. This Skill owns the cross-phase state that no single-phase build process can see. ## Core Features & Use Cases - Sprint Ledger: Maintains a run log with kickoff gates, an invariant registry re-checked after every phase, a merge topology plan, phase results, and an owner-decision queue. - Per-Phase Protocol: Composes worktree isolation, single-phase build, simplify, verification, scope checks, deploy-reachability checks, and shipping into one ordered pipeline per phase. - Review Convergence Loop: Governs review rounds with a class-sweep rule (fix the pattern across all repos and branches, not the cited instance) and a stopping rule that escalates non-converging rounds. - Use Case: You have a nine-doc epic spanning two repos and eight PRs that must land in a declared order. Run this Skill to drive each phase in sequence while tracking invariants, merge topology, and deploy status in a single auditable ledger. ## Quick Start Ask the AI to execute all phase docs in your epic's planning directory as one ordered sprint using the build-all workflow.

Frequently Asked Questions about build-all

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

FAQPage Schema
How do I execute multiple plan docs in order as one epic?▼

Provide the phase docs directory, a declared execution order with rationale, and a goal condition. The Skill creates a sprint ledger, then runs each phase through isolation, build, verification, and shipping while re-checking cross-phase invariants after every merge.

When should I use build-all instead of a single build command?▼

Use build-all when several phase docs must land in a declared order across one or more repos. A single plan doc belongs in the single-phase build skill, and independent parallelizable tasks belong in parallel worktree execution.

How do I avoid conflicts with stacked branches and squash merges?▼

Squash-merging a parent PR rewrites its commits, so a stacked child branch conflicts structurally. Either wait for the parent to merge before branching, or plan a rebase onto main the moment the parent squash-merges and verify the diff scope before pushing.

How should I handle repeated code review findings across rounds?▼

Fix the class, not the cited instance: name the grep-able pattern, sweep every repo and branch the sprint touches, paste the sweep output into the ledger, and fix all in-scope siblings. If a round closes nothing, escalate to the owner instead of looping.

Why is merged code sometimes not actually live?▼

Merged is not live when deployment is manual, such as an operator command or an uninstalled CI workflow. The Skill records such phases as merged-but-not-live with the exact deploy command in the owner-decision queue until the deploy is confirmed.

Related Skills

Explore More Software Engineering Skills→
maorfsdevmaorfsdev
23

phase-kickoff

Convert docs/phases/CURRENT.md into an ordered execution plan with tiered work packages.

Community
Advanced
SethGammonSethGammon
916

deploy-steward

Serializes merging and deploying ready GitHub pull requests into mainline one at a time.

Community
Advanced
zhiyuan-zhang0206zhiyuan-zhang0206
1

adversarial-review

Hunts correctness, security, contract, and fake-green defects in pull requests before merge.

Community
Advanced
NEXUZ-SYSNEXUZ-SYS
1

parallel-dispatch

Coordinate parallel task execution across multiple agents with isolated worktrees.

Official
Advanced