A planning skill that produces a structured implementation plan from Jira ticket requirements and related Confluence documents, splitting tasks across Frontend, Backend, and Infrastructure.
Tasks
Review the pre-fetched Jira ticket information including title, description, acceptance criteria, and priority
Review the pre-fetched Confluence documents including design documents, specifications, and architecture diagrams
Produce an implementation plan following planning-template.md and present it to the user for review
Inputs
Jira ticket information (title, description, acceptance criteria, priority) obtained in a prior step
Confluence documents (design documents, specifications, architecture diagrams) obtained in a prior step
Outputs
Structured implementation plan with a concise bulleted requirements summary
Technical approach including rationale for architecture decisions
Task breakdown organized across Frontend, Backend, and Infrastructure
Dependencies with blockers explicitly identified
Risks documented with severity and countermeasures
Limitations and checks
Respect existing codebase and architecture patterns
Ask the user when requirements are unclear
Do not descend into overly detailed implementation levels; remain at the planning level
Verify that Jira ticket information (title, description, acceptance criteria, priority) is available before planning
Verify that relevant Confluence documents (design documents, specifications, architecture diagrams) are available before planning
Confirm the requirements summary is concise and in bullet form
Confirm the technical approach states the rationale behind architecture decisions
Confirm tasks are split across Frontend, Backend, and Infrastructure
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control