planning
Skill0 starsChanged 11 months agoMITView on GitHub
Use when you need to plan technical solutions that are scalable, secure, and maintainable.
74 other projects use a version of this, 7 of them edited.
Adopted by
Most recently taken up by
- 14ag/claude-skillstheir own version, first seen Nov 16, 2026
- Ivan-propio/claude-skillstheir own version, first seen Nov 16, 2026
- david33137/claude-skillsedited, first seen Nov 16, 2026
- AshrafDurjoy/genai-shared-patternstheir own version, first seen Nov 16, 2026
- persiyanov/skillstheir own version, first seen Nov 15, 2026
- scolladon/crafttheir own version, first seen Nov 15, 2026
Used with
Projects with it also use ads-management, ai-artist and 5 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.
OpenAnalystIncSkillads-management
Activate for paid advertising campaigns on Google Ads, Meta Ads, LinkedIn Ads, TikTok Ads. Includes ad copywriting, audience targeting, budget optimization, A/B testing, and ROAS tracking. Used by ads-specialist and campaign-manager agents.
Also in 3 projects that use this
OpenAnalystIncSkillai-artist
Write and optimize prompts for AI-generated outcomes across text and image models. Use when crafting prompts for LLMs (Claude, GPT, Gemini), image generators (Midjourney, DALL-E, Stable Diffusion, Imagen, Flux), or video generators (Veo, Runway). Covers prompt structure, style keywords, negative prompts, chain-of-thought, few-shot examples, iterative refinement, and domain-specific patterns for marketing, code, and creative writing.
Also in 3 projects that use this
LucasDuysSkillexecuting
Autonomous task implementation workflow — implement, test, review, commit for each task in the frontier
Also in 3 projects that use this
- +4 more from OpenAnalystInc
Other versions74 projects use a version of this.
Word for word · 0
None found.
Edited · 7
- tmcfarlane/team-avatar★ 11376% same
- duongthinh03/portfolio★ 8592% same
- OpenAnalystInc/10x-Team★ 884% same
- derheissenberg/applicaiton★ 276% same
- truongtv22/theone-training-skills★ 197% same
- david33137/claude-skills★ 045% same
- docaohieu2808/claude-skills★ 045% same
Wrote their own version · 67
- langchain-ai/deepagents★ 31ksame name
- open-metadata/OpenMetadata★ 16ksame name
- atopile/atopile★ 4ksame name
- awslabs/agent-plugins★ 943same name
- xiaolai/vmark★ 918same name
- ryanthedev/code-foundations★ 389same name
- mblode/agent-skills★ 203same name
- markmdev/meridian★ 184same name
- Towow-ai/Flowness★ 107same name
- LucasDuys/forge★ 56same name
57 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 repository31 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-multimodalSkill
- backend-developmentSkill
- better-authSkill
- chrome-devtoolsSkill
- claude-codeSkill
- code-reviewSkill
- databasesSkill
- DebuggingSkill
- devopsSkill
- docs-seekerSkill
- frontend-design-proSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- google-adk-pythonSkill
- mcp-builderSkill
- mcp-managementSkill
- media-processingSkill
- mobile-developmentSkill
- payment-integrationSkill
- Problem-Solving TechniquesSkill
- repomixSkill
- researchSkill
- sequential-thinkingSkill
- shopifySkill
- skill-creatorSkill
- template-skillSkill
- threejsSkill
- ui-stylingSkill
- ui-ux-pro-maxSkill
- web-frameworksSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 7 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
- Distinctive: line 13
Use this skill when:
- Distinctive: line 23
Always honoring YAGNI, KISS, and DRY principles.
- Distinctive: line 54
DO NOT implement code - only create plans
- Distinctive: line 56
Ensure self-contained plans with necessary context
- Very specific: line 93
$CK_ACTIVE_PLANenv var: Only set for explicitly activated plans (via session state) - Very specific: line 100
Check
$CK_ACTIVE_PLANfirst: If set and valid directory, ask "Continue with existing plan? - Very specific: line 101
Check
$CK_SUGGESTED_PLANsecond: If set, inform user "Found suggested plan from branch: {path}" - Distinctive: line 103
Ask user if they want to activate it or create new
- Very specific: line 105
Update on create: Run node .claude/scripts/set-active-plan.cjs plans/...
- Distinctive: line 109
All agents writing reports MUST:
- Very specific: line 110
Check Plan Context section injected by hooks for Reports Path
- Very specific: line 111
Only $CK_ACTIVE_PLAN plans use plan-specific reports path
“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
Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.
When to Use
Use this skill when:
- Planning new feature implementations
- Architecting system designs
- Evaluating technical approaches
- Creating implementation roadmaps
- Breaking down complex requirements
- Assessing technical trade-offs
Core Responsibilities & Rules
Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise.
1. Research & Analysis
Load: references/research-phase.md
Skip if: Provided with researcher reports
2. Codebase Understanding
Load: references/codebase-understanding.md
Skip if: Provided with scout reports
3. Solution Design
Load: references/solution-design.md
4. Plan Creation & Organization
Load: references/plan-organization.md
5. Task Breakdown & Output Standards
Load: references/output-standards.md
Workflow Process
- Initial Analysis → Read codebase docs, understand context
- Research Phase → Spawn researchers, investigate approaches
- Synthesis → Analyze reports, identify optimal solution
- Design Phase → Create architecture, implementation design
- Plan Documentation → Write comprehensive plan
- Review & Refine → Ensure completeness, clarity, actionability
Output Requirements
- DO NOT implement code - only create plans
- Respond with plan file path and summary
- Ensure self-contained plans with necessary context
- Include code snippets/pseudocode when clarifying
- Provide multiple options with trade-offs when appropriate
- Fully respect the
./docs/development-rules.mdfile.
Plan Directory Structure
plans/
└── {date}-plan-name/
├── research/
│ ├── researcher-XX-report.md
│ └── ...
├── reports/
│ ├── XX-report.md
│ └── ...
├── scout/
│ ├── scout-XX-report.md
│ └── ...
├── plan.md
├── phase-XX-phase-name-here.md
└── ...Active Plan State
Prevents version proliferation by tracking current working plan via session state.
Active vs Suggested Plans
| Type | Env Var | Meaning |
| Active | $CK_ACTIVE_PLAN | Explicitly set via set-active-plan.cjs - use for reports |
| Suggested | $CK_SUGGESTED_PLAN | Branch-matched, hint only - do NOT auto-use |
How It Works
Plan context is managed through:
$CK_ACTIVE_PLANenv var: Only set for explicitly activated plans (via session state)$CK_SUGGESTED_PLANenv var: Branch-matched plans shown as hints, not directives- Session temp file:
/tmp/ck-session-{id}.jsonstores explicit activations only - SubagentStart hook: Injects differentiated context (Active vs Suggested)
Rules
- Check
$CK_ACTIVE_PLANfirst: If set and valid directory, ask "Continue with existing plan? [Y/n]" - Check
$CK_SUGGESTED_PLANsecond: If set, inform user "Found suggested plan from branch: {path}"- This is a hint only - do NOT auto-use it
- Ask user if they want to activate it or create new
- If neither set: Proceed to create new plan
- Update on create: Run
node .claude/scripts/set-active-plan.cjs plans/...
Report Output Location
All agents writing reports MUST:
- Check
Plan Contextsection injected by hooks forReports Path - Only
$CK_ACTIVE_PLANplans use plan-specific reports path $CK_SUGGESTED_PLANplans use defaultplans/reports/(not plan folder)- Use naming:
{agent}-{date}-{slug}.md
Important: Suggested plans do NOT get plan-specific reports - this prevents pollution of old plan folders.
Quality Standards
- Be thorough and specific
- Consider long-term maintainability
- Research thoroughly when uncertain
- Address security and performance concerns
- Make plans detailed enough for junior developers
- Validate against existing codebase patterns
Remember: Plan quality determines implementation success. Be comprehensive and consider all solution aspects.
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.

