feature-planning

Transform feature breakdowns into ordered, dependency-aware execution sequences.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/prulloac/git-blame-vsc --skill feature-planning-prulloac
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-planning
Source: https://github.com/prulloac/git-blame-vsc/tree/main/.agents/skills/feature-planning
Command: npx skills add https://github.com/prulloac/git-blame-vsc --skill feature-planning-prulloac

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Sequence tasks from a feature breakdown into an optimal, dependency-aware execution plan that clarifies order, blockers, and parallelizable work for efficient delivery.

Core Features & Use Cases

  • Determine task order and identify blockers
  • Detect parallelizable work and potential bottlenecks
  • Generate an agent-ready execution sequence for implementation
  • Validate inputs and ensure traceable handoffs between planning and execution

Quick Start

Provide a feature breakdown document and request an execution sequence to generate the ordered plan.

Frequently Asked Questions about feature-planning

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

FAQPage Schema
How do I create a dependency-aware execution sequence from a feature breakdown?

A dependency-aware execution sequence transforms a feature breakdown into an ordered task list that identifies blockers, parallelizable work, and integration points for efficient delivery.

Can I use a feature breakdown to determine task parallelization for AI agents?

Yes, feature breakdowns are consumed to detect parallelizable work and potential bottlenecks, producing an agent-ready execution sequence that defines task order and parallelization.

What is the maximum number of tasks supported in an implementation sequence?

The implementation sequence enforces a range of 5 to 50 tasks per feature breakdown, ensuring the generated dependency graph and batch groupings remain manageable.

Do I need a specific file format to generate an implementation sequence?

Yes, the system consumes a markdown feature breakdown document and outputs the implementation sequence as a markdown file, enforcing dependency graphs and traceable handoffs.

What's the best way to identify blockers and integration points in a feature plan?

Processing a feature breakdown into an execution sequence is the best way to identify blockers, mapping the dependency graph and highlighting integration points for traceable handoffs.

Why does my feature execution sequence fail to group parallelizable tasks?

Sequences fail to group parallel tasks when the feature breakdown lacks clear dependency definitions, which are required to generate batch groupings and validate traceable handoffs.