041-planning-plan-mode
SolidUse when creating a plan using Plan model and enhancing structured design plans in Cursor Plan mode for Java implementations. Use when the user wants to create a plan, design an implementation, structure a development plan, or use plan mode for outside-in TDD, feature implementation, or refactoring work. This should trigger for requests such as Create a plan with Cursor Plan mode; Write a plan with Claude Plan mode; Design an implementation plan; Structure a development plan. Part of cursor-rules-java project
Install
Quality Score: 93/100
Skill Content
Details
- Author
- jabrena
- Repository
- jabrena/cursor-rules-java
- Created
- 1 years ago
- Last Updated
- today
- Language
- Java
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
plan-mode
Use when the user asks to enter Plan mode, says /prompts:plan or /plan, or wants a structured execution plan written to plan/.
plan
Implementation planning skill. Decomposes a design doc, PRD, roadmap, or directly-stated topic into atomic, sequenced issues with dependency graphs and complexity classifications. Use when given a DESIGN-*.md, PRD-*.md, or ROADMAP-*.md to plan, or when the user says "break this into issues", "plan the implementation", "create issues for this", "decompose this", "what tasks do we need", or "make a plan for X". Also use for direct topic planning without a source document. Produces either a self-contained PLAN doc (single-pr) or GitHub milestone and issues (multi-pr).
plan-creating-project-plans
Comprehensive project planning standards for plans/ directory including folder structure (ideas.md, backlog/, in-progress/, done/), stage-aware naming convention (backlog/done use YYYY-MM-DD__identifier/, in-progress uses identifier/ with no date prefix), five-document file organization (README.md, brd.md, prd.md, tech-docs.md, delivery.md for multi-file default; single README.md for trivially-small single-file exception), BRD/PRD content-placement rules, Gherkin acceptance criteria, and the mandatory structured multiple-choice grilling gates (pre-write and post-write) for resolving design decisions with the user. Essential for creating structured, executable project plans.