Execute the plan in parallel waves. Independent tasks run as concurrent agents, dependent tasks wait.
From snonpx claudepluginhub guygrigsby/claude-plugins --plugin sno/buildImplements next planned task incrementally via TDD: write failing test, minimal implementation, full tests/build verification, commit changes.
/buildBuilds, compiles, and packages projects with error handling, optimization for dev/prod/test, and detailed reporting. Supports optional target and flags like --type, --clean, --optimize.
/buildScaffolds a VitePress site from existing wiki markdown files, adding dark theme, dark-mode Mermaid diagrams, and click-to-zoom for images and diagrams.
/buildBuilds a task from a Notion page URL: fetches details and properties, implements per spec with progress updates in Notion, communicates via comments if needed, then marks complete with optional diff explanation.
/buildImplements approved plan using TDD (RED-GREEN-REFACTOR per step), runs inline reviews, and produces test verification evidence.
/buildExecutes build, development, or implementation tasks by dynamically loading required expertise, agents, skills, and patterns just-in-time via resource registry.
You are in the build phase of sno. Your goal is to execute the plan as fast as possible by parallelizing independent tasks.
Read .sno/plan.md. If it doesn't exist, tell the user to run /sno:plan first.
Parse the dependency graph. Tasks use the structured format — each task is a ### N. Title (depends: ...) heading with status, files, verify, and done fields. Group remaining unchecked tasks (status [ ]) into waves:
(depends: none) or whose dependencies are already complete [x]Execute one wave at a time. For each wave:
.sno/spec.md)[x] in .sno/plan.md.sno: wave N [tasks 1,2,3] — <brief summary of what the wave did>. Include the task numbers from the plan so git history links back to plan tasks. Do NOT include .sno/ files.Move to next wave. Repeat until all tasks are complete.
When all tasks are done, update .sno/state.json phase to check. Then tell the user: "Run /sno:check to verify the work."
STOP. Do not proceed to the check phase. Do not start verifying anything. Your job ends here — return control to the user. The next phase starts only when the user explicitly runs /sno:check.
When spawning a parallel build agent, give it this context:
done criterionfiles field)verify field)Tell each agent:
verify field — run the specified check before reporting success. Ensure all tests (both existing and new) pass.If the plan identifies bottleneck tasks (tasks with the most downstream dependents), verify those first after a wave completes. If a bottleneck task failed, fix it before spawning the next wave — its failure cascades to everything downstream.
/sno:todo).The STOP gate above does NOT apply when --auto is set. With --auto:
.sno/todos.md and continue with remaining tasks.