What problem does it solve?
Turning Jira ticket requirements and scattered Confluence documentation into a concrete, organized implementation plan is time-consuming and error-prone. This Skill automates the planning step by producing a structured plan split across Frontend, Backend, and Infrastructure workstreams.
Core Features & Use Cases
- Requirements Summarization: Restates Jira ticket requirements, acceptance criteria, and ambiguities in clear, actionable terms.
- Three-Axis Task Breakdown: Organizes tasks into Frontend, Backend, and Infrastructure tracks with dependencies and blockers explicitly identified.
- Risk Assessment: Documents technical risks with severity ratings, mitigation strategies, and fallback plans.
- Use Case: After fetching a Jira ticket and related Confluence design docs, invoke this Skill to produce a review-ready implementation plan covering architecture decisions, task breakdown, dependencies, and risks before any code is written.
Quick Start
Create an implementation plan for the retrieved Jira ticket and Confluence documents, split into frontend, backend, and infrastructure tasks.