planning
Skill0 starsChanged 36 days agoApache-2.0View on GitHub
How to turn an approved spec into a bite-sized, no-placeholders implementation plan.
74 other projects use a version of this.
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-skillstheir own version, 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 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.
truongtv22SkillProblem-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
LucasDuysSkillexecuting
Autonomous task implementation workflow — implement, test, review, commit for each task in the frontier
Also in 3 projects that use this
mrgoonieSkillweb-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
mrgoonieSkillmcp-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
renathoazSkillverifying
Verify work before claiming done.
Also in 3 projects that use this
truongtv22Skillmobile-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
Other versions74 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 74
- 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
- tmcfarlane/team-avatar★ 113same name
- Towow-ai/Flowness★ 107same name
64 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 repository21 other files it gives its agents.
- browserbaseSkill
- cairnSkill
- developmentSkill
- dispatchSkill
- house-styleSkill
- kimi-subagentSkill
- lean-design-standardSkill
- mergeSkill
- nexus-authSkill
- nexus-jiraSkill
- orchestrateSkill
- orchestratorSkill
- releaseSkill
- remote-opsSkill
- reviewSkill
- securitySkill
- specSkill
- ticket-pipelineSkill
- vision-reviewSkill
- workflow-basicsSkill
- writing-skillsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Write the plan so someone with zero context for this codebase can execute it.
- Distinctive: line 14
Write complete content in every step.
- Distinctive: line 15
Follow TDD in the steps: failing test first, then the minimal code.
- Distinctive: line 19
Never write "TBD", "implement later", "add error handling", "write tests for the above", or "similar to Task N".
“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
Write the plan so someone with zero context for this codebase can execute it. Document the files, the code, the tests, and how to verify.
Steps
- Map the file structure first: which files are created or modified, and what each is responsible for. One clear responsibility per file; prefer small focused files.
- Break the work into tasks. Each task is self-contained. Each step inside a task is one action (write the failing test, run it, implement, run it, commit).
- Write complete content in every step. If a step changes code, show the code. Exact file paths. Exact commands with expected output.
- Follow TDD in the steps: failing test first, then the minimal code.
- Self-review against the spec: every spec requirement maps to a task; method/property names are consistent across tasks; no placeholders.
No placeholders
Never write "TBD", "implement later", "add error handling", "write tests for the above", or "similar to Task N". Repeat the real content. These are plan failures.
Platform
- Save the plan to
docs/YYYY-MM-DD-<feature>-plan.mdand commit it. - Decompose the work into single-ticket units (one NEX ticket per PR).
- Where the plan depends on existing code you haven't confirmed, flag it as a "confirm against live code" seam — don't invent APIs.
- To execute the plan, load the development skill.
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.

