planner
Skill9 starsChanged 7 months agoNo licenceView on GitHub
Main planner agent. Triggered by /planner, or natural language such as: "plan the project", "I have a brief", "break this down", "create a roadmap", "plan this feature", "detail the login feature", "what's blocking", "what's the status", "where are we", "resume planning", "continue the plan". Do NOT trigger for /product-designer, /ds-designer, or executor commands.
We split this skill into the rules it gives an agent
8 rules. 0 are common, 2 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 24 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.
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- penpot/penpot★ 62ksame name
- am-will/codex-skills★ 1ksame name
- toonight/get-shit-done-for-antigravity★ 952same name
- Vinix24/vnx-orchestration★ 63same name
- Tariux/AI-Skills-Not-Awesome★ 49same name
- openclosed-org/axum-harness★ 48same name
- FlineDev/TandemKit★ 42same name
- digitalocean-labs/do-app-platform-skills★ 38same name
- jackstine/forgectl★ 8same name
- Victorcorcos/skills★ 7same name
19 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.
Used alongsideProjects with it also use reviewer, debugger and 4 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.
MicrosoftSkillreviewer
ASP.NET Core ハンドブックの記事をレビューする。Use when: 記事をレビューする、ドキュメントを校正する、コードレビューする、PRをレビューする。技術ドキュメントのレビュー、品質チェック、校正。
Also in 5 projects that use this
JohnJBorenSkilldebugger
Systematic debugging workflows, root cause analysis, and troubleshooting patterns
Also in 3 projects that use this
- MicrosoftSkill
review-plan
Review an implementation plan produced by the Plan agent. It is CRITICAL to review plans before handing off to implementation — plans often have gaps, incorrect assumptions, or suboptimal sequencing that are cheaper to catch now than after coding. Use when the user asks to 'review the plan', 'check my plan', 'is this plan ready', or after the Plan agent produces a plan.md.
Also in 3 projects that use this
tesla0225Skillorchestrator
Issue/要件を受けたら分解→担当割当→実装→検証→統合を回す手順。未整備なら /repo-init でbootstrap。
Also in 4 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- build-frameSkill
- ddd-helpSkill
- ddd-updateSkill
- design-system-helpSkill
- ds-add-variantSkill
- ds-auditSkill
- ds-buildSkill
- ds-designerSkill
- ds-docSkill
- ds-feedbackSkill
- ds-handoffSkill
- ds-helpSkill
- ds-initSkill
- ds-memorySkill
- ds-planSkill
- ds-specSkill
- ds-tokenSkill
- ds-updateSkill
- ds-verifySkill
- exec-architectSkill
- exec-backendSkill
- exec-code-mapperSkill
- exec-featureSkill
- exec-frontendSkill
- exec-mapSkill
- exec-resumeSkill
- executorSkill
- exec-verifierSkill
- exec-write-memorySkill
- pd-annotateSkill
- pd-conceptSkill
- pd-defineSkill
- pd-designSkill
- pd-discoverSkill
- pd-gap-reportSkill
- pd-handoffSkill
- pd-new-projectSkill
- pd-resumeSkill
- pd-screen-builderSkill
- pd-statusSkill
- pd-write-memorySkill
- plan-featureSkill
- plan-projectSkill
- plan-resumeSkill
- plan-statusSkill
- plan-write-memorySkill
- product-designerSkill
- product-design-helpSkill
- resolve-componentSkill
- resolve-tokenSkill
- validate-componentSkill
- write-memorySkill
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.