Implement plan

Skill corticalstack/flow/.claude/skills/implement-plan

Flow: a cross-tool agentic-coding workflow plugin (research, plan, implement, validate) with a tracker abstraction

Install

npx -y skills add corticalstack/flow --skill implement-plan

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Execute an implementation plan from flow/plans/ phase by phase, pausing for verification between phases. Explicit workflow command; run only when invoked via /implement-plan or explicitly asked, never autonomously.

SKILL.md

3.5 KB, as published. Nobody here has run it

Implement Plan

You are tasked with implementing an approved technical plan from flow/plans/. These plans contain phases with specific changes and success criteria.

Getting Started

When given a plan path:

Read the plan completely and check for any existing checkmarks (- [x])
Read the original ticket and all files mentioned in the plan
Read files fully - never use limit/offset parameters, you need complete context
Transition the work-item state (if an issue / work item is referenced in the plan): tracker set-state <id> in-progress ready-for-dev
Think deeply about how the pieces fit together
Create a todo list to track your progress
Start implementing if you understand what needs to be done

If no plan path provided, ask for one.

Implementation Philosophy

Plans are carefully designed, but reality can be messy. Your job is to:

Follow the plan's intent while adapting to what you find
Implement each phase fully before moving to the next
Verify your work makes sense in the broader codebase context
Update checkboxes in the plan as you complete sections

When things don't match the plan exactly, think about why and communicate clearly. The plan is your guide, but your judgment matters too.

If you encounter a mismatch:

STOP and think deeply about why the plan can't be followed

Present the issue clearly:

Issue in Phase [N]:
Expected: [what the plan says]
Found: [actual situation]
Why this matters: [explanation]

How should I proceed?

Verification Approach

After implementing a phase:

Run the success criteria checks listed in the plan (e.g., uv run pytest, make test, npm test)
Fix any issues before proceeding
Update your progress in both the plan and your todos
Check off completed items in the plan file itself using Edit

Pause for human verification: After completing all automated verification for a phase, pause and inform the human that the phase is ready for manual testing. Use this format:

Phase [N] Complete - Ready for Manual Verification

Automated verification passed:
- [List automated checks that passed]

Please perform the manual verification steps listed in the plan:
- [List manual verification items from the plan]

Let me know when manual testing is complete so I can proceed to Phase [N+1].

If instructed to execute multiple phases consecutively, skip the pause until the last phase. Otherwise, assume you are just doing one phase.

do not check off items in the manual testing steps until confirmed by the user.

If You Get Stuck

When something isn't working as expected:

First, make sure you've read and understood all the relevant code
Consider if the codebase has evolved since the plan was written
Present the mismatch clearly and ask for guidance

Use sub-tasks sparingly - mainly for targeted debugging or exploring unfamiliar territory.

Resuming Work

If the plan has existing checkmarks:

Trust that completed work is done
Pick up from the first unchecked item
Verify previous work only if something seems off

Remember: You're implementing a solution, not just checking boxes. Keep the end goal in mind and maintain forward momentum.