spring-planning
Implementation Plan Creation
create an implementation plan in docs/plans/yyyymmdd-<task-name>.md with interactive context gathering.
step 0: parse intent and gather context
before asking questions, understand what the user is working on:
-
parse user's command arguments to identify intent:
- "add feature Z" / "implement W" → feature development
- "fix bug" / "debug issue" → bug fix plan
- "refactor X" / "improve Y" → refactoring plan
- "migrate to Z" / "upgrade W" → migration plan
- generic request → explore current work
-
gather relevant context quickly — use direct spring-explore skill, NOT an Explore agent. keep discovery under 30 seconds:
CRITICAL: do NOT launch an Explore agent. the goal is a quick scan, not exhaustive analysis. if more context is needed, ask the user in step 1.
More from amplicode/spring-skills
java-debug
>
16spring-explore
>
15spring-data-jpa
Rules and guidelines for working with Spring Data JPA in the project. ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves changing entity structure, adding new entities, modifying field annotations, updating database mappings, creating or modifying Spring Data repositories, or defining query projections (interfaces, DTOs).
14mapper-creator
>
14spring-security-configuration
>
14dto-creator
>
13