execute-phase
Skill0 starsChanged 7 months agoMITView on GitHub
Human-attended execution of the next plan phase. Reads .plan/ files to orient, proposes scope for confirmation, executes items, verifies the build, and updates all plan files. Use when resuming work on a multi-session project with the human present.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- takleb3rry/claude-global-appbuilding-skillstheir own version, first seen Nov 8, 2026
- buildomator/buildomatortheir own version, first seen Nov 4, 2026
- Pitcocy/skillstheir own version, first seen Nov 1, 2026
- gtrabanco/agentic-workflowtheir own version, first seen Sep 22, 2026
- alchemiststudiosDOTai/harness-engineeringtheir own version, first seen Mar 17, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- alchemiststudiosDOTai/harness-engineering★ 104same name
- buildomator/buildomator★ 102same name
- gtrabanco/agentic-workflow★ 23same name
- takleb3rry/claude-global-appbuilding-skills★ 6same name
- Pitcocy/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- autopilot-executeSkill
- close-planSkill
- deep-modules-auditSkill
- docs-auditSkill
- lint-fixSkill
- living-design-systemSkill
- phased-planSkill
- responsive-auditSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 19 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Read these files in order:
- Distinctive: line 31
Before writing any code, state:
- Distinctive: line 42
Test as you go — don't batch all testing to the end
- Distinctive: line 43
If you hit a blocker, note it and ask the user
- Distinctive: line 44
If something doesn't match the spec, flag it — don't silently diverge
- Distinctive: line 45
Follow patterns from MEMORY.md and CONVENTIONS.md
- Distinctive: line 47
After completing each item, note it:
- Distinctive: line 54
After completing items, run the project's build/verify command:
- Distinctive: line 61
If the build fails:
- Distinctive: line 62
Read the error output
- Distinctive: line 65
If stuck, ask the user for help
- Distinctive: line 69
When all items in the phase are complete, verify the exit criteria from PLAN.md:
- Distinctive: line 70
Run any tests or build commands
- Very specific: line 79
Check off completed items: - [ ] → - [x]
- Distinctive: line 86
Add any new decisions to the Key Decisions table (increment the # counter)
- Distinctive: line 87
Add any new gotchas to Gotchas & Warnings
- Distinctive: line 88
Update Architecture Notes if anything structural changed
- Distinctive: line 89
Update Technical Context with new paths, commands, etc.
- Distinctive: line 92
If anything deviated from the spec or plan, log it
- Distinctive: line 93
If the spec itself was updated, note that too
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Execute Phase
Resume a multi-session project by reading the plan state, executing the next phase, and maintaining context continuity. The human is present — confirm scope before executing, ask when blocked.
Step 1 — Orient (Read Plan State)
Read these files in order:
CLAUDE.md— Project identity, current state, key files, commands.plan/PLAN.md— Find the current phase and next uncompleted item.plan/MEMORY.md— Absorb all shared context, decisions, gotchas.plan/DRIFT.md— Check for any spec changes since last session.agents/CONVENTIONS.md— Build patterns and rules (if exists)
Then state clearly:
📍 Current Phase: {N} — {Name}
📋 Next Item: {N.X} — {Description}
📝 Items remaining in phase: {count}
⚠️ Gotchas to watch: {any relevant from MEMORY.md}Step 2 — Plan the Session
Before writing any code, state:
- What items you will tackle this session
- Any open questions that need resolving first
- Any risks or dependencies
Wait for user confirmation before proceeding.
Step 3 — Execute
Work through items sequentially:
- Complete each item fully before moving to the next
- Test as you go — don't batch all testing to the end
- If you hit a blocker, note it and ask the user
- If something doesn't match the spec, flag it — don't silently diverge
- Follow patterns from MEMORY.md and CONVENTIONS.md
After completing each item, note it:
✅ {N.X} — {Description} — DoneBuild Gate
After completing items, run the project's build/verify command:
# Read BUILD_CMD from autopilot.config, or use project defaults
# e.g., npm run typecheck && npm run lintIf the build fails:
- Read the error output
- Fix the issue
- Re-run until it passes
- If stuck, ask the user for help
Step 4 — Check Exit Criteria
When all items in the phase are complete, verify the exit criteria from PLAN.md:
- Run any tests or build commands
- Demonstrate the working functionality
- Confirm with the user
Step 5 — Close Session (Update Plan Files)
This step is mandatory. Do not skip.
Update .plan/PLAN.md:
- Check off completed items:
- [ ]→- [x] - Update header metadata:
Status:→ "In Progress" or "Phase N Complete"Current Phase:→ Current or next phase numberLast Session:→ Session number and today's date
Update .plan/MEMORY.md:
- Add any new decisions to the Key Decisions table (increment the # counter)
- Add any new gotchas to Gotchas & Warnings
- Update Architecture Notes if anything structural changed
- Update Technical Context with new paths, commands, etc.
Update .plan/DRIFT.md:
- If anything deviated from the spec or plan, log it
- If the spec itself was updated, note that too
Append to .plan/SESSION-LOG.md:
## Session {N} — Phase {X}: {Phase Name} ({date})
**What happened:**
- {Summary of work done}
**Items completed:**
- [x] {N.X} — {Description}
- [x] {N.Y} — {Description}
**Issues encountered:**
- {Any blockers, surprises, or decisions made — or "None"}
**Handoff to next session:**
- Next: {next unchecked item or next phase}
- {Critical context the next session needs immediately}
- {Any open questions to resolve}
---Update .agents/TENSIONS.md:
- Append any friction noticed during the session
Rules
- Never skip the orient step — Even if you think you remember, read the files. Context from a previous session is unreliable.
- Never skip the close step — The next session depends on accurate plan files. This is the shared memory.
- Flag drift, don't hide it — If you need to change something from the spec, say so explicitly and log it.
- One phase per session — Don't start the next phase in the same session. Close cleanly and let the next session start fresh.
- Ask before big decisions — If you discover something that changes the approach, stop and discuss with the user before proceeding.
- Test at phase boundaries — Every phase should end with working, verified functionality.
- Build gate is mandatory — The build/typecheck command must pass before you mark items complete.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

