implementation-planning

Generate structured multi-phase implementation plans from ticket descriptions.

5|1|Updated Sep 6, 2009

Search Tags:#planning #documentation #research #codebase #implementation #phases #software

Ready to run

npx skills add https://github.com/bnadlerjr/dotfiles --skill implementation-planning-bnadlerjr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-planning
Source: https://github.com/bnadlerjr/dotfiles/tree/main/claude/skills/implementation-planning
Command: npx skills add https://github.com/bnadlerjr/dotfiles --skill implementation-planning-bnadlerjr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning complex software implementations from a ticket or requirement is time-consuming and error-prone without a structured approach.

Core Features & Use Cases

Interactive research gathering and parallel analysis to understand the current state.
Structured phase-based planning with explicit "What We're NOT Doing" boundaries.
Traceability to source files and existing documentation to validate decisions.

Quick Start

Provide a task or ticket description to generate a structured, multi-phase implementation plan.

Frequently Asked Questions about implementation-planning

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

FAQPage Schema

How do I plan software implementations from a ticket description?▼

Planning software implementations requires coordinating research, structure, and verification to produce a ticket-driven plan. This approach captures context gathering, parallel research, phased outlines, and traceability to source files to validate decisions.

What is a ticket-driven implementation plan?▼

A ticket-driven implementation plan is a structured document that outlines phase-by-phase development steps, explicitly defines what is not being built, and maintains traceability to source files and existing documentation to validate technical decisions.

How do I structure a multi-phase implementation plan with research?▼

Structure a multi-phase implementation plan by applying interactive research gathering and parallel analysis to understand the current state, then outlining explicit phases with approval checkpoints and boundaries for what is excluded from the scope.

Can I define what is not doing in a software implementation plan?▼

Yes, structured implementation planning explicitly defines "What We're NOT Doing" boundaries to prevent scope creep. This ensures phase-based development remains focused on documented requirements and avoids unintended codebase modifications.

How do I trace implementation phases back to source files and documentation?▼

Trace implementation phases back to source files and documentation by generating a plan that validates decisions through interactive research gathering, ensuring every phase maintains explicit traceability to existing codebase files and project documentation.