agentleFS
Sign inStart free
motao123motao123/dev-workflow-kit/planning/SKILL.md

planning

Skill1 starsChanged 5 months agoMITView on GitHub

Use when a task needs scope clarification, acceptance criteria, implementation slicing, dependency mapping, or a verification plan before coding begins. This skill turns fuzzy requests into concrete execution plans.

69 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use Problem-Solving Techniques, executing 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.
  • truongtv22Skill

    Problem-Solving Techniques

    Apply systematic problem-solving techniques for complexity spirals (simplification cascades), innovation blocks (collision-zone thinking), recurring patterns (meta-pattern recognition), assumption constraints (inversion exercise), scale uncertainty (scale game), and dispatch when stuck. Techniques derived from Microsoft Amplifier project patterns adapted for immediate application.

    Also in 5 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

  • mrgoonieSkill

    web-frameworks

    Build modern full-stack web applications with Next.js (App Router, Server Components, RSC, PPR, SSR, SSG, ISR), Turborepo (monorepo management, task pipelines, remote caching, parallel execution), and RemixIcon (3100+ SVG icons in outlined/filled styles). Use when creating React applications, implementing server-side rendering, setting up monorepos with multiple packages, optimizing build performance and caching strategies, adding icon libraries, managing shared dependencies, or working with TypeScript full-stack projects.

    Also in 5 projects that use this

  • mrgoonieSkill

    mcp-management

    Manage Model Context Protocol (MCP) servers - discover, analyze, and execute tools/prompts/resources from configured MCP servers. Use when working with MCP integrations, need to discover available MCP capabilities, filter MCP tools for specific tasks, execute MCP tools programmatically, access MCP prompts/resources, or implement MCP client functionality. Supports intelligent tool selection, multi-server management, and context-efficient capability discovery.

    Also in 5 projects that use this

  • renathoazSkill

    verifying

    Verify work before claiming done.

    Also in 3 projects that use this

  • truongtv22Skill

    mobile-development

    Build modern mobile applications with React Native, Flutter, Swift/SwiftUI, and Kotlin/Jetpack Compose. Covers mobile-first design principles, performance optimization (battery, memory, network), offline-first architecture, platform-specific guidelines (iOS HIG, Material Design), testing strategies, security best practices, accessibility, app store deployment, and mobile development mindset. Use when building mobile apps, implementing mobile UX patterns, optimizing for mobile constraints, or making native vs cross-platform decisions.

    Also in 4 projects that use this

  • +6 more from mrgoonie

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 62 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill before implementation when the task is unclear, large, risky, or cross-cutting.

    line 9
  2. Distinctive:

    Use this skill when:

    line 13
  3. Distinctive:

    Do not use this skill for obvious one-line fixes or pure explanation-only questions.

    line 20
  4. Distinctive:

    Read the relevant code, docs, and local instructions first.

    line 24
  5. Very specific:

    use systematic-debugging if execution stalls on unclear failures

    line 45
  6. Very specific:

    use ship-readiness before merge or release

    line 46

“Common” is measured: kept by at least 6 in 10 of the 62 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

Use this skill before implementation when the task is unclear, large, risky, or cross-cutting.

Trigger Conditions

Use this skill when:

  • the user asks how to approach a task
  • requirements are incomplete or ambiguous
  • the task spans multiple files, packages, or layers
  • the team needs acceptance criteria before coding
  • implementation order, risk, or dependencies are unclear

Do not use this skill for obvious one-line fixes or pure explanation-only questions.

Workflow

  1. Read the relevant code, docs, and local instructions first.
  2. Clarify the desired outcome and constraints.
  3. Break the work into the smallest meaningful slices.
  4. Identify risks, dependencies, and unclear assumptions.
  5. Define a concrete verification approach.
  6. Recommend the execution order.

Output

For non-trivial work, provide:

  • goal summary
  • scope boundaries
  • step-by-step plan
  • risks and dependencies
  • verification plan
  • recommended next skill if relevant

Coordination

After planning:

  • continue in the active implementation workflow
  • use systematic-debugging if execution stalls on unclear failures
  • use ship-readiness before merge or release

Invocation Examples

  • "Use planning to break this feature into implementation slices and acceptance criteria."
  • "Use planning before we touch this multi-package refactor."
  • "Use planning to define the safest order for this migration and its verification."

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.

Check your setup, free