agentleFS
captain-corgicaptain-corgi/marketplace-website/.claude/skills/planning/SKILL.md

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

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.
  • OpenAnalystIncSkill

    ads-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

  • OpenAnalystIncSkill

    ai-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

  • LucasDuysSkill

    executing

    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

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
  1. Distinctive:

    Create detailed technical implementation plans through research, codebase analysis, solution design, and comprehensive documentation.

    line 9
  2. Distinctive:

    Use this skill when:

    line 13
  3. Distinctive:

    Always honoring YAGNI, KISS, and DRY principles.

    line 23
  4. Distinctive:

    DO NOT implement code - only create plans

    line 54
  5. Distinctive:

    Ensure self-contained plans with necessary context

    line 56
  6. Very specific:

    $CK_ACTIVE_PLAN env var: Only set for explicitly activated plans (via session state)

    line 93
  7. Very specific:

    Check $CK_ACTIVE_PLAN first: If set and valid directory, ask "Continue with existing plan?

    line 100
  8. Very specific:

    Check $CK_SUGGESTED_PLAN second: If set, inform user "Found suggested plan from branch: {path}"

    line 101
  9. Distinctive:

    Ask user if they want to activate it or create new

    line 103
  10. Very specific:

    Update on create: Run node .claude/scripts/set-active-plan.cjs plans/...

    line 105
  11. Distinctive:

    All agents writing reports MUST:

    line 109
  12. Very specific:

    Check Plan Context section injected by hooks for Reports Path

    line 110
  13. Very specific:

    Only $CK_ACTIVE_PLAN plans use plan-specific reports path

    line 111

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Initial Analysis → Read codebase docs, understand context
  2. Research Phase → Spawn researchers, investigate approaches
  3. Synthesis → Analyze reports, identify optimal solution
  4. Design Phase → Create architecture, implementation design
  5. Plan Documentation → Write comprehensive plan
  6. 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.md file.

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

TypeEnv VarMeaning
Active$CK_ACTIVE_PLANExplicitly set via set-active-plan.cjs - use for reports
Suggested$CK_SUGGESTED_PLANBranch-matched, hint only - do NOT auto-use

How It Works

Plan context is managed through:

  1. $CK_ACTIVE_PLAN env var: Only set for explicitly activated plans (via session state)
  2. $CK_SUGGESTED_PLAN env var: Branch-matched plans shown as hints, not directives
  3. Session temp file: /tmp/ck-session-{id}.json stores explicit activations only
  4. SubagentStart hook: Injects differentiated context (Active vs Suggested)

Rules

  1. Check $CK_ACTIVE_PLAN first: If set and valid directory, ask "Continue with existing plan? [Y/n]"
  2. Check $CK_SUGGESTED_PLAN second: 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
  3. If neither set: Proceed to create new plan
  4. Update on create: Run node .claude/scripts/set-active-plan.cjs plans/...

Report Output Location

All agents writing reports MUST:

  1. Check Plan Context section injected by hooks for Reports Path
  2. Only $CK_ACTIVE_PLAN plans use plan-specific reports path
  3. $CK_SUGGESTED_PLAN plans use default plans/reports/ (not plan folder)
  4. 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.