tobihagemann/turbo / codex/skills/plan
plan
VerifiedUniversal planning entry: analyze task complexity and route to a direct change or a plan file. Use when the user asks to "plan this task", "plan and implement", or "run $turbo:plan".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| references/direct-mode.md | markdown | 573 B |
| references/plan-mode.md | markdown | 3.2 KB |
references/plan-mode.md
View on GitHub# Plan: Plan Mode
Draft → refine → self-improve → settle lesson edits → mark ready → halt to produce a plan file the user implements after an optional `/compact`.
## Task Tracking
Use `update_plan` to track each phase, restating any remaining steps of a parent workflow alongside them:
1. Run `$draft-plan` skill
2. Run `$refine-plan` skill
3. Run `$self-improve` skill
4. Settle lesson edits
5. Mark plan ready
6. Summarize and halt
## Phase 1: Run `$draft-plan` Skill
Run the `$draft-plan` skill with the input. The input may be a freeform task description, an explicit slug, or a path to a background document. Capture the resolved plan path from `$draft-plan`'s output for the next phases, and the path of any gated plan it also wrote. When it wrote one, call `update_plan` to add an entry right after Phase 2 for running `$refine-plan` on the gated plan's path, restating any remaining steps of a parent workflow.
## Phase 2: Run `$refine-plan` Skill
Run the `$refine-plan` skill with `<path>` from Phase 1. When Phase 1 captured a gated plan, run the `$refine-plan` skill again with that path once the first run finishes.
## Phase 3: Run `$self-improve` Skill
Run the `$self-improve` skill to compound planning learnings.
## Phase 4: Settle Lesson Edits
**Skip** this phase when every file Phase 3 created or changed lies outside this repository or is ignored by git.
Otherwise output as text that `$self-improve` left the remaining files changed and uncommitted, with their paths. Then use `request_user_input` to ask what to do with them before the plan is implemented:
- **Commit and push** — run the `$stage-commit-push` skill for the changes Phase 3 made to those files
- **Commit only** — run the `$stage-commit` skill for the changes Phase 3 made to those files
- **Leave uncommitted** — keep them as they are
## Phase 5: Mark Plan Ready
Update the YAML frontmatter of each plan from Phase 1 to `status: ready`.
## Phase 6: Summarize and Halt
When the workflow file, or your latest `update_plan` call when there is none, lists pending steps of a parent workflow, complete each of them, then continue with this phase's summary.
Present a brief summary of the finished plan: the essence of what it builds and the key decisions behind it, short enough to read at a glance so the user does not have to open the full plan file. When the plan delivers value to a user, developer, or operator, also present a short list of stories capturing what that person gains, in the form "As a <persona>, I want <capability> so that <outcome>". Skip the stories only when no beneficiary or outcome can be named, such as a purely mechanical refactor. Fit both to the plan rather than a fixed template.
Then halt with this message:
> Plan ready at `<plan path>`.
>
> This is a good point to `/compact` before implementing. Then run `$turbo:implement-plan <slug>` to implement.
When Phase 1 captured a gated plan, add a line to that message naming its path and the gate that must pass before running `$turbo:implement-plan` on it. When Phase 4 left files uncommitted, add a line naming them.
## Rules
- Route revisions through `$refine-plan` or `$draft-plan`.
- Hand implementation to the user via the Phase 6 halt; the user runs `$turbo:implement-plan` after an optional `/compact`.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |