piv-plan-implementation

Generates a context-rich implementation plan from a tracker ticket or feature description.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-plan-implementation-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: piv-plan-implementation
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/piv-plan-implementation
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill piv-plan-implementation-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing code without a plan leads to missed requirements, inconsistent patterns, and repeated clarification loops. This Skill turns a Jira/Linear/GitHub ticket or free-form feature request into a complete, one-pass-ready implementation plan before any code is written. ## Core Features & Use Cases - Ticket-Aware Planning: Fetches the ticket from your tracker (Jira via Atlassian MCP, GitHub via gh), follows links up to the epic and architecture page, and inherits existing decisions instead of re-deciding them. - Codebase Intelligence: Analyzes project structure, naming conventions, testing patterns, dependencies, and integration points, then cites specific file:line references to mirror. - Clarifying Gate: Pauses after analysis to ask 3-6 targeted questions with recommended defaults, recording unanswered items as explicit assumptions rather than guessing silently. - Use Case: You receive ticket ACC-30 for a new API endpoint. The Skill fetches the ticket and its epic's architecture doc, scans your codebase for matching patterns, asks you to confirm scope boundaries, then writes a phased plan with step-by-step tasks, validation commands, and acceptance criteria to .claude/plans/. ## Quick Start Ask the agent to plan the implementation for ticket ACC-30, or describe a feature you want built, and it will produce a detailed plan file before any code is written.

Frequently Asked Questions about piv-plan-implementation

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

FAQPage Schema
How do I create an implementation plan from a Jira ticket?▼

Pass the ticket key or URL as the argument. The plan is built by fetching the ticket via the Atlassian MCP, reading its summary and acceptance criteria, then following links to the epic and architecture page so existing decisions are inherited rather than re-decided.

How to plan a feature before writing code with an AI agent?▼

Provide a ticket reference or free-form feature description. The workflow runs codebase analysis, external documentation research, and a clarifying question gate, then writes a phased plan with step-by-step tasks and validation commands to .claude/plans/.

Does it work with GitHub issues and Linear tickets?▼

Yes. GitHub issues are fetched with gh issue view, Jira tickets via the Atlassian MCP, and Linear or other tracker URLs are handled the same way. Free-form feature descriptions without any ticket are also supported.

What happens if I skip the clarifying questions?▼

If you decline to answer, every unresolved item is recorded as an explicit assumption in the plan's Open Questions section, and affected tasks carry a GOTCHA note naming the guess. Nothing is assumed silently.

Where is the generated implementation plan saved?▼

Plans are written as Markdown files to the .claude/plans/ directory with a kebab-case descriptive filename, such as add-user-authentication.md. The directory is created automatically if it does not exist.