Create Plan
Create a new plan as a Neotoma entity, optionally linked to objectives, releases, or other plans.
Get the complete skill folder, including its scripts and reference files.
·
When to use this skill
Use Create Plan when an AI agent needs a reusable SKILL.md workflow for this job: Create a new plan as a Neotoma entity, optionally linked to objectives, releases, or other plans.
When not to use it
Skip Create Plan when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/create-plan # Save SKILL.md to ~/.claude/skills/create-plan/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/create-plan/SKILL.md. For a shared project, commit the folder at .claude/skills/create-plan/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Create Plan skill for this task: Collect required plan fields from the user. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 74/100
- Practical detail
- 74/100
- Source evidence
- 56/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# 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:
1. Collect required plan fields from the user 2. Run alignment check (summary → user confirms) 3. Store plan as a Neotoma `plan` entity 4. Create relationships to related entities 5. Optionally rebuild the `neotoma-plans` mirror
## Tasks
1. **Collect required fields:**
Ask the user for any missing required fields: - `title` — Short, imperative name - `description` — Problem being solved and why it matters - `scope` — What is explicitly in scope - `out_of_scope` — What is explicitly out of scope - `success_criteria` — Measurable conditions for completion - `status` — Default to `draft`
Optional fields to offer (collect if relevant): - `priority` (P0/P1/P2/P3) - `phase` - `target_release` - `deliverables` - `dependencies` (canonical names of plans this plan requires) - `testing_notes` - `observability_notes`
2. **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.
3. **Store the plan:**
Use `store` or `submit_entity` with: - `entity_type: plan` - All collected fields as snapshot fields
4. **Create relationships** (if relevant entities are mentioned or known): - `REFERS_TO` for objectives, releases, or parent plans - `DEPENDS_ON` for plans this plan requires - `INFORMED_BY` for issues, feedback, or research
5. **Confirm and offer mirror rebuild:**
``` Plan stored: {canonical_name}
To refresh plans/ in the repo, run: neotoma mirror rebuild --profile neotoma-plans ```
Do 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"
Intended uses
- Collect required plan fields from the user
- Run alignment check (summary → user confirms)
- Store plan as a Neotoma plan entity
- Create relationships to related entities
- Optionally rebuild the neotoma-plans mirror
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.