plan-story

To generate an implementation plan for a Jira issue, the Skill fetches story details, summarizes requirements, explores the codebase, and structures actionable steps across database, API, frontend, and testing layers.

Automated codebase exploration improves software development planning by analyzing existing patterns and components, ensuring the generated implementation plan adheres to current architecture and provides accurate file path references.

The best way to structure a feature implementation plan is by organizing tasks systematically across database schema, API, frontend components, and testing layers, ensuring full architectural coverage and actionable development steps.

Yes, you can use this with existing Jira stories by providing the ticket identifier, which triggers the system to fetch issue details and parse requirements, assumptions, and out-of-scope items automatically.

Yes, the generated development plan includes specific file path references. It analyzes your codebase to identify relevant components and patterns, providing actionable steps that directly point to the necessary files.

To clarify requirements and out-of-scope items when starting new feature development, the Skill parses fetched Jira issue details to summarize explicit requirements, assumptions, and boundaries before generating the implementation plan.