Execute the next unfinished row in a CLAUDE Stage 4 phase loop.
npx skills add https://github.com/bonjohen/claude-local --skill phase-bonjohen
Please help me install this Agent Skill. Skill: phase Source: https://github.com/bonjohen/claude-local/tree/main/bundle/skills/phase Command: npx skills add https://github.com/bonjohen/claude-local --skill phase-bonjohen
This Skill executes the next unfinished item in a CLAUDE “Stage 4” phase loop, updating the authoritative plan file as it starts and completes each row.
Started or taking the topmost Open row), while skipping Blocked rows and reporting blockers.Started with a PST timestamp, then verifies the changes, and finally marks it Completed with a fresh PST timestamp.Ask the phase skill to execute the next available row in the most recently modified docs/*_plan.md.
High-intent search queries and answers about installing and using this skill.
Plan execution automation reads a markdown plan file, selects the next unfinished row, updates its status with PST timestamps, performs the scoped work, and verifies results before marking it complete. It resumes started rows or takes the topmost open row while skipping blocked items.
Resumable phase loops persist state by writing Started and Completed transitions with timestamps directly to the plan file immediately after each change. This allows workflows to resume the first incomplete phase seamlessly across different sessions without losing progress.
Yes, workflow automation optionally targets a specified plan file for execution. By default it targets the most recently modified docs/*_plan.md file, but you can direct it to execute the next available row in any explicitly provided plan file path.
When all rows in a phase are completed, the workflow writes a Phase Summary block to the plan file and stages exactly one git commit without pushing. This ensures incremental file edits are captured safely in version control for each finished phase.
Iterative development workflows automatically skip rows marked as Blocked during plan execution and report the blockers to the user. The system selects the next available Open or Started row, ensuring blocked items do not halt the overall phase loop progress.
No, manual git commit staging is unnecessary during phase loop execution. The workflow automatically stages exactly one commit per fully completed phase without pushing, capturing the incremental file edits and phase summary safely in local version control.
boomNDSConvert feature specifications into executable implementation plans with tasks and acceptance criteria.
vineet-codes256Organize staged and unstaged changes into atomic git commits and push them.
zb-ssStandardize workflow phase agent file operations and state tracking.
skaisserExecute reviewed plans by delegating work to subagents and tracking task completion.