041-planning-plan-mode
This Claude Code skill guides creation of structured development plans for Java projects using Cursor Plan mode, incorporating sections like Requirements Summary, Approach with Mermaid diagrams, Task Lists, and Execution Instructions. Use it when designing implementation strategies, refactoring approaches, or planning feature development with outside-in TDD methodology, requiring interactive context gathering and plan validation before artifact generation.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/041-planning-plan-mode && cp -r /tmp/041-planning-plan-mode/skills/041-planning-plan-mode ~/.claude/skills/041-planning-plan-modeSKILL.md
# Java Design Plan Creation for Cursor Plan Mode Guide the process of creating a structured plan using Cursor Plan mode. **This is an interactive SKILL**. Plans follow a consistent section structure suitable for Java feature implementation, refactoring, or API design. **What is covered in this Skill?** - Plan mode workflow: enter Plan mode, gather context, draft plan, iterate - YAML frontmatter: name, overview, todos, isProject - Required sections: Requirements Summary, Approach (with Mermaid), Task List, Execution Instructions, File Checklist, Notes - London Style (outside-in) TDD pattern - Plan execution discipline: update Status after each task before advancing - Plan storage: ask user for preferred folder and filename convention before creating artifact ## Constraints Gather context before drafting. Include Execution Instructions in every plan. Never advance to next task without updating the plan's Status column. - **MANDATORY**: Run `date` before starting to get date prefix for plan filename - **MUST**: Read the reference template fresh—do not use cached content - **MUST**: Ask one or two questions at a time; never all at once - **MUST**: Validate summary (Does this capture what you need?) before proposing plan creation - **MUST**: Wait for user to confirm proceed before generating the plan - **MUST**: Ask the user where they want to store the plan before generating the plan artifact - **MUST**: Include Execution Instructions section in every generated plan ## When to use this skill - Create a plan with Cursor Plan mode - Write a plan with Claude Plan mode - Design an implementation plan - Structure a development plan - Create a structured design plan - Refactor the plan - Improve the plan - Update the plan ## Workflow 0. **Get current date** Run `date` before planning and use it to derive the plan filename prefix `YYYY-MM-DD`. 1. **Read reference and gather context** Read `references/041-planning-plan-mode.md` and ask one or two questions at a time to clarify requirements, constraints, and target scope. 2. **Validate summary and confirm proceed** Summarize understanding, ask Does this capture what you need?, and wait for explicit proceed before creating the plan artifact. 3. **Confirm plan storage location** Ask where the user wants to store the plan (for example, `.cursor/plans/` or another folder) and confirm the target filename pattern before writing. 4. **Generate structured plan artifact** Create the plan at the confirmed location using required sections and YAML frontmatter, including Execution Instructions. 5. **Apply execution discipline** When executing tasks from the plan, update the Status column after each task before moving to the next one. ## Reference For detailed guidance, examples, and constraints, see [references/041-planning-plan-mode.md](references/041-planning-plan-mode.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project