plan-feature

Convert PRD files into hierarchical execution plans with time-boxed phases.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill plan-feature-luyzkk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/luyzkk/Anti-Vibe-Coding/tree/main/skills/plan-feature
Command: npx skills add https://github.com/luyzkk/Anti-Vibe-Coding --skill plan-feature-luyzkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a PRD into a disciplined, executable execution plan by decomposing requirements into vertical slices, senior-level phases, and a hierarchical folder structure for tracking.

Core Features & Use Cases

  • PRD → hierarchical plans: transforms PRD requirements into multiple plans and detailed phases with clear dependencies.
  • Senior complexity judgment: decides granularity (how many plans/phases) based on engineering risk signals rather than fixed thresholds.
  • Profile-aware phase policy: reads an architectural profile and injects the appropriate phase-granularity policy; falls back to the v5.2 behavior when no profile is available.
  • On-demand isolated generation: produces PLAN.md and STATE.md, then generates each planoNN and fase-XX under isolated subagents only when approved.

Quick Start

Plan a feature by pointing to its PRD path: run plan-feature with the PRD file at docs/exec-plans/active/2026-04-20-slug/PRD.md.

Frequently Asked Questions about plan-feature

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

FAQPage Schema
How do I turn a PRD into an executable hierarchical plan?

To turn a PRD into an executable plan, you need a tool that performs vertical-slice decomposition and phase sizing. This skill converts PRD files into hierarchical execution plans with time-boxed phases and dependency tracking.

What is vertical-slice phase decomposition for feature planning?

Vertical-slice phase decomposition is a technique that breaks feature requirements into senior-level phases based on engineering risk. It generates granular execution phases with clear dependencies rather than relying on fixed thresholds.

Can I generate isolated execution plans for specific phases from a PRD?

Yes, you can generate isolated execution plans for specific phases. After creating baseline PLAN.md and STATE.md files, the system generates individual planoNN and fase-XX documents under isolated subagents upon approval.

Does architecture profile affect phase policy during PRD decomposition?

Yes, architecture profiles directly affect phase policy during PRD decomposition. The system reads an architectural profile to inject appropriate phase-granularity policies, falling back to default v5.2 behavior when no profile is detected.

How should I structure my PRD file for automated execution plan generation?

Structure your PRD file as a markdown document outlining feature requirements, typically placed at a path like docs/exec-plans/active/slug/PRD.md. The system reads this file to detect legacy layouts and generate hierarchical plans.