Individual skill
create-plans
Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not enterprise documentation. Handles briefs, roadmaps, phase plans, and context handoffs.
skills/create-plans/SKILL.md
Source commit 1757615b99ab789a72ff2d02e9f6112af2a15c04
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,987
- Repository last updated
- Apr 1, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
README.mddoc · 9,888 bytesSKILL.mdcore · 17,800 bytesSKILL.mdcore · 17,800 bytesSKILL.mdcore · 17,800 bytesSKILL.mdcore · 17,800 bytesSKILL.mdcore · 17,800 bytesreferences/checkpoints.mddoc · 20,553 bytesreferences/cli-automation.mddoc · 17,132 bytesreferences/context-management.mddoc · 3,747 bytesreferences/domain-expertise.mddoc · 5,086 bytesreferences/git-integration.mddoc · 2,266 bytesreferences/hierarchy-rules.mddoc · 4,142 bytesreferences/milestone-management.mddoc · 13,671 bytesreferences/plan-format.mddoc · 11,960 bytesreferences/research-pitfalls.mddoc · 7,443 bytesreferences/scope-estimation.mddoc · 12,308 bytesreferences/user-gates.mddoc · 2,266 bytestemplates/brief.mddoc · 3,500 bytestemplates/continue-here.mddoc · 1,821 bytestemplates/issues.mddoc · 3,591 bytestemplates/milestone.mddoc · 3,057 bytestemplates/phase-prompt.mddoc · 6,831 bytestemplates/research-prompt.mddoc · 6,957 bytestemplates/roadmap.mddoc · 4,890 bytestemplates/summary.mddoc · 4,600 bytesworkflows/complete-milestone.mddoc · 8,706 bytesworkflows/create-brief.mddoc · 2,401 bytesworkflows/create-roadmap.mddoc · 3,600 bytesworkflows/execute-phase.mddoc · 31,503 bytesworkflows/get-guidance.mddoc · 2,036 bytesworkflows/handoff.mddoc · 3,227 bytesworkflows/plan-chunk.mddoc · 1,495 bytesworkflows/plan-phase.mddoc · 10,167 bytesworkflows/research-phase.mddoc · 2,748 bytesworkflows/resume.mddoc · 2,669 bytesworkflows/transition.mddoc · 3,761 bytes
Read excerpt
<essential_principles>
<principle name="solo_developer_plus_claude">
You are planning for ONE person (the user) and ONE implementer (Claude).
No teams. No stakeholders. No ceremonies. No coordination overhead.
The user is the visionary/product owner. Claude is the builder.
</principle>
<principle name="plans_are_prompts">
PLAN.md is not a document that gets transformed into a prompt.
PLAN.md IS the prompt. It contains:
- Objective (what and why)
- Context (@file references)
- Tasks (type, files, action, verify, done, checkpoints)