Execute a 3-doc implementation plan with wave-based parallel subagents and verification gates.
npx skills add https://github.com/baek-labs/hames --skill go-baek-labs
Please help me install this Agent Skill. Skill: go Source: https://github.com/baek-labs/hames/tree/main/packages/claude/integrations/dryforge/upstream/go Command: npx skills add https://github.com/baek-labs/hames --skill go-baek-labs
ready skill and executes it end-to-end with structured orchestration instead of ad-hoc coding. ## Core Features & Use Cases - Wave-based parallel execution: Parses the plan's Execution Graph, topologically sorts tasks into waves of up to 8 concurrent subagents, and isolates parallel work in git worktrees. - Evidence-based verification gates: Runs merge gates, integration gates, and a completion gate using captured command exit codes, plus a runtime smoke test for services. - Spec-first review and escalation: Applies conditional spec reviews for risky tasks, a final full-diff review, and a bounded escalation ladder that pauses for the user instead of guessing. - Harness lifecycle management: Creates or updates project documentation (CLAUDE.md/AGENTS.md, docs/) after the first cycle and archives the 3-doc on approval. - Use Case: After ready writes a handoff, spec, and plan for a new feature, invoke go to implement all tasks across isolated worktrees, verify the integrated result, and present it for approval before merging to main. ## Quick Start Invoke the go skill after ready has written the 3-doc to execute the plan and implement the spec.High-intent search queries and answers about installing and using this skill.
Invoke the go skill after the ready skill writes the 3-doc (handoff, spec, plan) into .dryforge/. It parses the plan's Execution Graph, sorts tasks into waves of up to 8 concurrent subagents, and merges verified results into the base branch.
Wave-based execution groups independent tasks from a dependency graph into batches that run in parallel, while dependent tasks wait for earlier waves. Each wave ends with an integration gate running the project's verify commands on the merged result.
Yes, git is required because worktree isolation depends on it. If the folder is not a repository, the skill offers to run git init with an initial commit; if git is not installed, it stops and reports.
For existing projects, all work happens on a feature branch created from main, and main is only modified through a final user-approved merge. For greenfield projects with no application code, main serves as the working base directly.
The skill runs a bounded escalation ladder: re-dispatch with missing context, then an upgraded model, then the user. Any escalation reaching the user is synchronous, pausing the run until the user responds, and blocked worktrees are preserved for diagnosis.
Do not use it without a valid 3-doc from the ready skill, since the plan's Execution Graph is the authority it executes against. It also stops if the graph has cycles, dangling dependencies, or a first-cycle handoff missing the Project Foundation section.
kimprobablyConvert ambiguous product intent into an approved design specification.
AlmogMaayanCommits, pushes, merges, and deploys a feature branch through a gated GitHub pipeline.
selfagencyRender local markdown files in a cmux viewer panel with live reload.
Veloxia-agencyCoordinate parallel subagents in isolated git worktrees for shared tasks.