feature-planning

Creates phased, multi-PR-ready project plans with linked documentation files.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ctdio/dotfiles --skill feature-planning-ctdio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-planning
Source: https://github.com/ctdio/dotfiles/tree/main/claude/skills/feature-planning
Command: npx skills add https://github.com/ctdio/dotfiles --skill feature-planning-ctdio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? Complex software features often lead to disorganized development, missed dependencies, and difficult code reviews. This Skill provides a structured framework to break down large features into manageable, phase-based plans, ensuring clarity, efficient multi-PR implementation, and reduced development friction.

Core Features & Use Cases

  • Phased Implementation Strategy: Breaks down complex features into stackable, shippable Pull Requests (PRs) with clear goals, deliverables, and dependencies for a smooth rollout.
  • Agent-Friendly Documentation: Generates detailed, navigable plans in ~/.ai/plans/ using progressive disclosure, allowing AI agents (or humans) to quickly gather context at various depths.
  • Context Preservation: Documents key architectural decisions, trade-offs, potential gotchas, and testing strategies for future reference, minimizing rework and confusion.
  • Use Case: A product manager requests a new "User Onboarding Flow" feature that involves multiple backend and frontend changes. This skill can be used to generate a comprehensive plan, outlining database schema changes, API modifications, UI components, and testing strategies across several development phases, ensuring a predictable and successful launch.

Quick Start

Use the feature-planning skill to create a detailed plan for the "User Onboarding Flow" feature. Break it down into logical phases.

Frequently Asked Questions about feature-planning

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

FAQPage Schema
How do I break down a complex software feature into manageable phases?

Phase-based feature planning divides large features into stackable, shippable pull requests with clear goals and dependencies. This Skill creates structured plans in ~/.ai/plans/ that document each phase's deliverables, technical details, and architectural decisions, enabling smooth multi-PR rollouts and reducing implementation friction.

What should a feature plan include for multi-PR development?

A comprehensive feature plan includes phased technical details, API contracts, database schema changes, architecture decisions, testing strategies, and implementation guidance. This Skill generates standardized documentation artifacts that preserve context, document trade-offs, and anticipate edge cases across all development phases.

How do I document feature decisions and dependencies for future reference?

Feature planning captures architectural decisions, rationale, trade-offs, and gotchas in agent-friendly documentation using progressive disclosure. Context notes and technical details across phases create a navigable record that minimizes rework and clarifies dependencies for team members and AI tools.

Can I use feature planning for agile and phased software rollouts?

Yes. This Skill structures complex features into agile-compatible phases with defined deliverables per phase. It suits phased development, multi-PR implementations, and progressive rollouts where clear dependencies and documented decisions are critical for coordination and code review efficiency.

What's the difference between ad-hoc feature notes and structured feature planning?

Structured feature planning provides standardized templates, progressive disclosure for context depth, and explicit traceability across phases. Unlike ad-hoc notes, it generates consistent documentation for architecture, testing, and implementation guidance, making plans reusable and agent-navigable.

Do I need design documentation before starting feature planning?

Feature planning works best after initial design decisions are made. It captures and organizes existing technical architecture, API design, and schema choices into phases. You can refine these during planning, but basic product and technical alignment accelerates plan generation.