plan-story

Generate step-by-step implementation plans for Jira issues across database, API, tests, and frontend layers.

6|1|Updated Dec 13, 2017

Search Tags:#planning #development #codebase #implementation #story #jira

Ready to run

npx skills add https://github.com/esassoc/neptune --skill plan-story

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-story
Source: https://github.com/esassoc/neptune/tree/main/.claude/skills/plan-story
Command: npx skills add https://github.com/esassoc/neptune --skill plan-story

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of creating detailed, step-by-step implementation plans for new software stories, ensuring all aspects of development are considered.

Core Features & Use Cases

Jira Integration: Fetches story details directly from Jira.
Requirement Summarization: Parses and clarifies requirements, assumptions, and out-of-scope items.
Codebase Exploration: Analyzes the existing codebase to identify relevant components and patterns.
Structured Planning: Generates a comprehensive plan covering database, API, frontend, and testing layers.
Use Case: When starting a new feature development, use this Skill to generate a complete plan, from database schema changes to frontend component implementation, ensuring consistency and thoroughness.

Quick Start

Use the plan-story skill to generate an implementation plan for Jira ticket NPT-123.

Frequently Asked Questions about plan-story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate an implementation plan for a Jira issue?▼

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.

How does automated codebase exploration improve software development planning?▼

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.

What's the best way to structure a feature implementation plan across different software layers?▼

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.

Can I use this implementation planning tool with my existing Jira stories?▼

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.

Does the generated development plan include specific file path references?▼

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.

How do I clarify requirements and out-of-scope items when starting new feature development?▼

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.