create-plan
Skill38 starsChanged 2 months agoMITView on GitHub
Create a new plan as a Neotoma entity, optionally linked to objectives, releases, or other plans.
40 other projects use a version of this.
Adopted by
Most recently taken up by
- artberri/skillstheir own version, first seen Nov 8, 2026
- Pubx-ai/skillstheir own version, first seen Nov 8, 2026
- mattmireles/gemma-tuner-multimodaltheir own version, first seen Nov 1, 2026
- fnayou/dotfilestheir own version, first seen Oct 25, 2026
- knwoop/clear-plan-skillstheir own version, first seen Oct 14, 2026
- mhylle/claude-skills-collectiontheir own version, first seen Oct 9, 2026
Used with
Projects with it also use codebase-migrate, support-ticket-triage 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.
ComposioHQSkillcodebase-migrate
Run large codebase migrations and multi-file refactors. Uses the Composio CLI to coordinate issue tracking, batched PRs, and CI verification while the agent executes the transforms locally across hundreds of files.
Also in 5 projects that use this
ComposioHQSkillsupport-ticket-triage
Triage customer support tickets/emails/chats into categories, priority, and next action; draft responses and create reproducible steps; use for Zendesk/Intercom/Help Scout exports or pasted threads.
Also in 5 projects that use this
corticalstackSkilliterate-plan
Revise an existing implementation plan in flow/plans/ based on feedback, researching when needed. Explicit-only; run only when invoked via /iterate-plan or explicitly asked.
Also in 4 projects that use this
hebertzhuSkilldevelop-web-game
Use when building or iterating on a web game and you need a tight implement-test-observe loop; prefer the bundled Playwright client, inspect screenshots and text state, and validate every meaningful change before moving on.
Also in 3 projects that use this
petestewartSkilldatadog-logs
Query Datadog logs via the Logs Search API v2. Use when the user asks to "check the logs", "search logs", "find errors in Datadog", "look up logs for", "show me production logs", "check for errors", "search Datadog", or any request involving log search, error investigation, or production debugging that requires Datadog log data.
Also in 3 projects that use this
- +7 more from ComposioHQ
Other versions40 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 40
- ComposioHQ/awesome-codex-skills★ 17ksame name
- composio-community/awesome-codex-skills★ 16ksame name
- netease-youdao/LobsterAI★ 6.2ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- freestylefly/wesight★ 969same name
- gittower/git-flow-next★ 458same name
- JetBrains/youtrackdb★ 443same name
- OpenFn/lightning★ 321same name
- dannys-code-corner/incan★ 73same name
- DasDigitaleMomentum/opencode-processing-skills★ 60same name
30 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 repository101 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- .cursor/rules/autonomous_execution.mdcCursor rule
- .cursor/rules/cursor_rules_editing.mdcCursor rule
- .cursor/rules/cursor_rules_sync.mdcCursor rule
- .cursor/rules/cursor_rules_sync_requirement.mdcCursor rule
- site_pages/llms.txtllms.txt
- advisorySkill
- analyzeSkill
- auditSkill
- commitSkill
- create-planSkill
- create_planSkill
- create-prototypeSkill
- create_prototypeSkill
- create_prSkill
- create-releaseSkill
- create_releaseSkill
- create-ruleSkill
- create_ruleSkill
- debugSkill
- draft-illustrationSkill
- draft_illustrationSkill
- endSkill
- evaluate_positioningSkill
- final-reviewSkill
- final_reviewSkill
- fix-feature-bugSkill
- fix_feature_bugSkill
- learnSkill
- manage-error-debuggingSkill
- manage_error_debuggingSkill
- neversight_learn_skills.dev_obviously_awesomeSkill
- process_issuesSkill
- process_prsSkill
- publish-planSkill
- publish_planSkill
- publishSkill
- pullSkill
- pushSkill
- recover_sqlite_databaseSkill
- releaseSkill
- report-errorSkill
- report_errorSkill
- reportSkill
- reviewSkill
- run-feature-workflowSkill
- run_feature_workflowSkill
- setup-commandsSkill
- setup_commandsSkill
- setup-cursor-copiesSkill
- setup_cursor_copiesSkill
- store-neotomaSkill
- store_neotomaSkill
- sync-env-from-1passwordSkill
- sync_env_from_1passwordSkill
- analyzeSkill
- auditSkill
- commitSkill
- create-prototypeSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 7 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Create a new plan entity in Neotoma with title = {{input:title}}.
- Very specific: line 15
Follow the complete workflow in foundation/development/plan_workflow.md.
- Distinctive: line 24
Run alignment check (summary → user confirms)
- Distinctive: line 26
Create relationships to related entities
- Distinctive: line 33
Ask the user for any missing required fields:
- Distinctive: line 52
After collecting fields, produce a concise summary:
- Distinctive: line 57
Ask: "Does this accurately capture what you want this plan to do?"
- Very specific: line 63
Use store or submit_entity with:
- Distinctive: line 65
All collected fields as snapshot fields
- Distinctive: line 81
Do not wait for a response before completing this skill.
“Common” is measured: kept by at least 6 in 10 of the 38 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
Create New Plan
Create a new plan entity in Neotoma with title = {{input:title}}.
Follow the complete workflow in foundation/development/plan_workflow.md. Configuration is read from foundation-config.yaml.
This workflow can also be triggered automatically via .cursor/rules/plan_detection.mdc when you mention planning-related patterns in natural language (e.g., "create plan", "new plan"). Both paths execute the same workflow.
Workflow Overview
Implements Checkpoint 0 of the plan creation workflow:
- Collect required plan fields from the user
- Run alignment check (summary → user confirms)
- Store plan as a Neotoma
planentity - Create relationships to related entities
- Optionally rebuild the
neotoma-plansmirror
Tasks
Collect required fields:
Ask the user for any missing required fields:
title— Short, imperative namedescription— Problem being solved and why it mattersscope— What is explicitly in scopeout_of_scope— What is explicitly out of scopesuccess_criteria— Measurable conditions for completionstatus— Default todraft
Optional fields to offer (collect if relevant):
priority(P0/P1/P2/P3)phasetarget_releasedeliverablesdependencies(canonical names of plans this plan requires)testing_notesobservability_notes
Alignment check:
After collecting fields, produce a concise summary:
- Problem it solves and why it exists
- What is explicitly in scope and out of scope
- Critical constraints or invariants
Ask: "Does this accurately capture what you want this plan to do?"
Incorporate corrections and re-summarize if changes are substantial. Do not proceed until the user confirms.
Store the plan:
Use
storeorsubmit_entitywith:entity_type: plan- All collected fields as snapshot fields
- Create relationships (if relevant entities are mentioned or known):
REFERS_TOfor objectives, releases, or parent plansDEPENDS_ONfor plans this plan requiresINFORMED_BYfor issues, feedback, or research
Confirm and offer mirror rebuild:
Plan stored: {canonical_name} To refresh plans/ in the repo, run: neotoma mirror rebuild --profile neotoma-plansDo not wait for a response before completing this skill.
Required Documents
Load before starting:
foundation/development/plan_workflow.md(workflow)foundation-config.yaml(configuration)
Inputs
title(string): Short plan name, e.g. "Add selective mirror profiles"
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.

