Borrowing it
Nothing to install: this file belongs to GGPrompts/TFE. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GGPrompts/TFE/main/.claude/commands/phased-plan.mdgit clone --depth 1 https://github.com/GGPrompts/TFEWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ggprompts/tfe/phased-plan)<a href="https://agentmods.dev/commands/ggprompts/tfe/phased-plan"><img src="https://agentmods.dev/badge/commands/ggprompts/tfe/phased-plan.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00010 | $0.01818 |
| Opus 5 | $0.00005 | $0.00909 |
| Sonnet 5 | $0.00002 | $0.00364 |
| Haiku 4.5 | $0.00001 | $0.00182 |
Grade A, and why
phased-plan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phased Plan: Multi-Phase Execution with Auto-Compacting
You are executing a multi-phase plan where each phase runs in fresh context for maximum accuracy.
CRITICAL INSIGHT: Fresh context = better accuracy. Even if context window has room, compacting between phases improves results!
How This Works
After the user provides a phased plan, you will:
- Execute Phase 1 - Work on first phase completely
- Auto-compact - Create summary using Desktop Commander
- Execute Phase 2 - Start fresh with Phase 1 summary
- Auto-compact - Cumulative summary of Phases 1-2
- Continue - Each phase gets fresh context
Command Format
The user will provide phases in one of these formats:
Format 1: Inline
/phased-plan
Phase 1: Research syntax highlighting libraries for Go
Phase 2: Choose library and implement basic highlighting
Phase 3: Add language detection for code blocks
Phase 4: Integrate with preview rendering
Phase 5: Test and optimize performance
Format 2: With Goal
/phased-plan Implement syntax highlighting in preview
Then you ask for the phases.
Your Execution Process
Phase Execution Pattern:
For each phase:
-
Announce Phase Start
═══════════════════════════════════════════════ 📋 PHASE N/TOTAL: [Phase Description] ═══════════════════════════════════════════════ Previous phases summary: [Cumulative summary of completed phases] Now executing: [Current phase] -
Execute the Phase
- Work on the phase completely
- Show progress as you go
- Complete all tasks for this phase
-
Phase Completion
✅ PHASE N COMPLETE What was accomplished: - [Key achievements] - [Files modified] - [Important decisions] -
Git Commit (Optional but Recommended)
📝 Phase complete! Ready to commit? Suggested commit message: Phase N: [Phase description] - [Achievement 1] - [Achievement 2] - [Files modified] Use: auto-compact --commit -g "Phase [N+1]" → This will: commit changes + compact + continue
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 293 lines · 10 tokens per session scan A 72779c99d2e9
phased-plan is a command published in the GitHub repository GGPrompts/TFE (20 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,818 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.