Execute PLAN.md tasks with fresh subagents and atomic commits.
npx skills add https://github.com/yulonghe97/ystack --skill go-yulonghe97
Please help me install this Agent Skill. Skill: go Source: https://github.com/yulonghe97/ystack/tree/main/skills/go Command: npx skills add https://github.com/yulonghe97/ystack --skill go-yulonghe97
Execute a plan created by /build. Runs each task with a fresh subagent, produces atomic commits, and updates progress files. Use this skill when the user says 'go', '/go', 'execute', 'run the plan', 'execute the plan', 'start building', 'let's do it', or confirms a plan and wants to proceed with implementation. Requires a PLAN.md from a prior /build run.
Place a PLAN.md produced by a prior /build run and execute it with /go to start implementing the plan.
High-intent search queries and answers about installing and using this skill.
To execute a PLAN.md with per-task isolation, you can use the /go command to run each task with a fresh subagent. This produces atomic commits and updates progress files while adhering to locked decisions from DECISIONS.md.
The best way to ensure atomic commits when running a prebuilt plan is to delegate each task to a fresh subagent. This approach guarantees deterministic execution and creates an atomic commit for every individual task completed.
Yes, you need a PLAN.md generated from a prior /build run to start deterministic task execution. The execution process reads this plan and locks decisions from DECISIONS.md to maintain plan fidelity during implementation.
Spawning a fresh subagent for each task maintains plan fidelity by isolating task execution and preventing context bleed. It follows the prebuilt PLAN.md and locked decisions from DECISIONS.md to ensure deterministic implementation and automatic progress-tracking updates.
Yes, you can execute a plan and update progress files automatically by running the /go command. It delegates work to subagents per task, creates atomic commits, and updates progress tracking files throughout the implementation process.
During execution, the system adheres to locked decisions from DECISIONS.md to maintain plan fidelity over the PLAN.md. If conflicts arise, the locked decisions take precedence to ensure deterministic task execution and consistent atomic commits.
TaylorHustonGenerate structured phase-based plans from project issues into PLAN.md.
getdatasurgeExecute PLAN.md files atomically with per-task commits and deviation handling.
apsulliExecute GSD plans with atomic commits and checkpoint-driven progression.
earchibaldDispatch fresh subagents per task with two-stage spec and code quality reviews.
