planning-with-files
Skill4 starsChanged 7 months agoMITView on GitHub
How to structure implementation plans as files, progressive implementation, plan review process
71 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- AtilaMedeiros/skillstheir own version, first seen Nov 16, 2026
- alibaklaea/claude-skillsedited, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- FimawLLC/fimaw-skillstheir own version, first seen Nov 15, 2026
- OthmanAdi/planning-with-filestheir own version, first seen Nov 10, 2026
- Liang-MH/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use react-best-practices, huashu-design and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
OpenAISkillreact-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Also in 5 projects that use this
XIYBHKSkillhuashu-design
花叔Design(Huashu-Design)——用HTML做高保真原型、交互Demo、幻灯片、动画、设计变体探索+设计方向顾问+专家评审的一体化设计能力。HTML是工具不是媒介,根据任务embody不同专家(UX设计师/动画师/幻灯片设计师/原型师),避免web design tropes。触发词:做原型、设计Demo、交互原型、HTML演示、动画Demo、设计变体、hi-fi设计、UI mockup、prototype、设计探索、做个HTML页面、做个可视化、app原型、iOS原型、移动应用mockup、导出MP4、导出GIF、60fps视频、设计风格、设计方向、设计哲学、配色方案、视觉风格、推荐风格、选个风格、做个好看的、评审、好不好看、review this design。**主干能力**:Junior Designer工作流(先给假设+reasoning+placeholder再迭代)、反AI slop清单、React+Babel最佳实践、Tweaks变体切换、Speaker Notes演示、Starter Components(幻灯片外壳/变体画布/动画引擎/设备边框)、App原型专属守则(默认从Wikimedia/Met/Unsplash取真图、每台iPhone包AppPhone状态管理器可交互、交付前跑Playwright点击测试)、Playwright验证、HTML动画→MP4/GIF视频导出(25fps基础 + 60fps插帧 + palette优化GIF + 6首场景化BGM + 自动fade)。**需求模糊时的Fallback**:设计方向顾问模式——从5流派×20种设计哲学(Pentagram信息建筑/Field.io运动诗学/Kenya Hara东方极简/Sagmeister实验先锋等)推荐3个差异化方向,展示24个预制showcase(8场景×3风格),并行生成3个视觉Demo让用户选。**交付后可选**:专家级5维度评审(哲学一致性/视觉层级/细节执行/功能性/创新性各打10分+修复清单)。
Also in 3 projects that use this
VercelSkillvercel-deploy
Deploy applications and websites to Vercel with a claimable preview. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment". No authentication required - returns preview URL and claimable deployment link.
Also in 3 projects that use this
AnthropicSkillweb-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
Also in 6 projects that use this
JetBrainsSkillwebapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Also in 12 projects that use this
JetBrainsSkillslack-gif-creator
Knowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack.
Also in 6 projects that use this
- +2 more from JetBrains
Other versions71 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- sefaertunc/anthropic-watch★ 1100% same
- alibaklaea/claude-skills★ 010% same
Wrote their own version · 69
- OthmanAdi/planning-with-files★ 28ksame name
- Galaxy-Dawn/claude-scholar★ 5.9ksame name
- microsoft/semantic-link-labs★ 600same name
- mxyhi/ok-skills★ 511same name
- involvex/youtube-music-cli★ 482same name
- xuzeyu91/WebCode★ 278same name
- YYH211/Claude-meta-skill★ 274same name
- junevm/splathash★ 208same name
- xiaoyuge886/aigc★ 198same name
- cohen-liel/hivemind★ 108same name
59 more not listed
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 repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-routingSkill
- backend-conventionsSkill
- claude-md-maintenanceSkill
- coding-principlesSkill
- context-managementSkill
- coordinator-modeSkill
- frontend-design-systemSkill
- git-conventionsSkill
- memory-architectureSkill
- project-patternsSkill
- prompt-engineeringSkill
- review-and-handoffSkill
- security-checklistSkill
- subagent-usageSkill
- testingSkill
- verificationSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 10 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
10
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 63
Before implementing, send the plan through the plan-reviewer agent:
- Distinctive: line 65
Write the IMPLEMENTATION-PROMPT file
- Very specific: line 66
Use /review-plan to trigger review
- Distinctive: line 74
Update the plan file with revisions
- Distinctive: line 76
Don't skip review for non-trivial work.
- Distinctive: line 84
Run verification for that phase
- Distinctive: line 89
If a phase reveals the plan was wrong, STOP.
- Distinctive: line 108
Every plan should define must-haves that carry through from planning to verification:
- Distinctive: line 121
Don't over-plan. The plan should be specific enough to implement without guessing but not so detailed that it's pseudo-code.
- Distinctive: line 124
Every step needs a verification.
- Distinctive: line 127
Keep plans in version control.
“Common” is measured: kept by at least 6 in 10 of the 66 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
Planning with Files
The IMPLEMENTATION-PROMPT Pattern
Large tasks need a written plan before code. The plan lives as a file so it can be reviewed, versioned, and referenced across sessions.
File naming: IMPLEMENTATION-PROMPT-{FEATURE}.md in the project root or docs/ directory.
Structure:
# Implementation: {Feature Name}
## Goal
One sentence. What does success look like?
## Context
What exists today. What needs to change. Links to relevant spec sections.
## Plan
### Phase 1: {Name}
- Step 1: {specific action}
- Verify: {how to confirm it worked}
- Step 2: {specific action}
- Verify: {how to confirm it worked}
### Phase 2: {Name}
...
## Edge Cases
- {case}: {how to handle}
## Out of Scope
- {thing we're explicitly NOT doing}Breaking Large Tasks into Phases
Each phase should be:
- Independently testable
- Committable on its own
- Small enough for one session (or one focused block within a session)
Signs a phase is too big:
- More than 5-7 steps
- Touches more than 3-4 files substantially
- You can't describe the verification in one sentence
Signs a phase is too small:
- It's just one line change
- The verification is "it compiles"
- It doesn't move the feature forward meaningfully
The Plan-Review Workflow
Before implementing, send the plan through the plan-reviewer agent:
- Write the IMPLEMENTATION-PROMPT file
- Use
/review-planto trigger review - The plan-reviewer (Opus) acts as a staff engineer:
- Flags ambiguity
- Identifies missing verification steps
- Checks SPEC.md alignment
- Questions unrealistic scope
- Points out edge cases
- Address ALL feedback before proceeding
- Update the plan file with revisions
Don't skip review for non-trivial work. The 5 minutes spent reviewing saves hours of rework.
Progressive Implementation
Execute one phase at a time:
- Read the plan
- Implement the phase
- Run verification for that phase
- Commit
- Update PROGRESS.md
- Move to next phase
If a phase reveals the plan was wrong, STOP. Update the plan first. Don't improvise your way through a broken plan.
When to Plan vs When to Just Do It
Plan (write an IMPLEMENTATION-PROMPT):
- Multi-file changes
- New features
- Architectural changes
- Anything touching more than 2 modules
Just do it:
- Bug fixes with obvious cause
- Single-file refactors
- Documentation updates
- Config changes
Must-Haves Contract
Every plan should define must-haves that carry through from planning to verification:
- Truths: Observable behaviors that must be true when done (e.g., "POST /api/users returns 201 with a user object")
- Artifacts: Files that must exist with real implementation (e.g., "src/routes/users.js with createUser function")
- Key Links: Connections between artifacts (e.g., "users route imported in src/app.js and registered at /api/users")
These must-haves become the verification checklist. If the plan-reviewer doesn't see them, it should request them. If the verify-app agent can't confirm them, the feature isn't done.
Gotchas
- Plans rot fast. If a plan is more than 2 sessions old and hasn't been started, re-review it before implementing. The codebase may have changed.
- Don't over-plan. The plan should be specific enough to implement without guessing but not so detailed that it's pseudo-code. Trust the implementer to make tactical decisions.
- Every step needs a verification. "Implement the auth module" is not a plan step. "Implement the auth module; verify: login endpoint returns 200 with valid creds and 401 with invalid" is a plan step.
- Keep plans in version control. They're documentation of decisions and intent.
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.

