agentleFS
Sign inStart free
markmhendricksonmarkmhendrickson/neotoma/.claude/skills/create_plan/SKILL.md

create_plan

Skill38 starsChanged 2 months agoMITView on GitHub

Create New Plan

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    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
  1. Very specific:

    Create a new plan entity in Neotoma with title = {{input:title}}.

    line 11
  2. Very specific:

    Follow the complete workflow in foundation/development/plan_workflow.md.

    line 13
  3. Distinctive:

    Run alignment check (summary → user confirms)

    line 22
  4. Distinctive:

    Create relationships to related entities

    line 24
  5. Distinctive:

    Ask the user for any missing required fields:

    line 31
  6. Distinctive:

    After collecting fields, produce a concise summary:

    line 50
  7. Distinctive:

    Ask: "Does this accurately capture what you want this plan to do?"

    line 55
  8. Very specific:

    Use store or submit_entity with:

    line 61
  9. Distinctive:

    All collected fields as snapshot fields

    line 63
  10. Distinctive:

    Do not wait for a response before completing this skill.

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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
<!-- Source: .cursor/skills/create-plan/SKILL.md -->

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 .claude/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"

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