feature-planner

Transforms vague feature requests into actionable plans with defined requirements and risk-prioritized slices.

3|Updated Feb 26, 2026

Search Tags:#design #planning #requirements #handoff #feature #risk-management #vertical-slices

Ready to run

npx skills add https://github.com/ralvarezdev/ralvaskills --skill feature-planner-ralvarezdev

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-planner
Source: https://github.com/ralvarezdev/ralvaskills/tree/main/skills/workflows/feature-planner
Command: npx skills add https://github.com/ralvarezdev/ralvaskills --skill feature-planner-ralvarezdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turns vague feature requests into a well-scoped plan containing a concrete requirement, identified constraints, and a design outline to guide implementation.

Core Features & Use Cases

Requirement clarification: translates vague user requests into explicit outcomes and success criteria.
Constraint discovery: surfaces performance, scope, and risk constraints early.
Design outline & vertical-slice planning: creates a bounded plan with risk-prioritized slices ready for test-first execution.
Hand-off flow: recommends downstream steps to grill-with-docs and tdd for execution.

Quick Start

Provide a vague feature idea and let this skill generate a clarified requirement, a design outline, and a prioritized vertical-slice plan.

Frequently Asked Questions about feature-planner

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

FAQPage Schema

How do I turn a vague feature request into an actionable development plan?▼

To turn a vague feature request into an actionable plan, you clarify the requirement, discover constraints, and generate a risk-prioritized vertical-slice plan. This process translates ambiguous ideas into explicit outcomes and bounded design outlines ready for implementation.

What is vertical-slice planning and when should I use it for feature design?▼

Vertical-slice planning is a technique that breaks feature design into risk-prioritized, test-first execution slices. Use it during early-stage ideas or ambiguous requests to create a bounded plan that surfaces performance and scope constraints before implementation begins.

How do I clarify requirements and identify constraints for an ambiguous feature?▼

Clarifying requirements involves translating vague requests into explicit outcomes and success criteria. Constraint discovery surfaces performance, scope, and risk limitations early, ensuring the resulting design outline and feature plan remain bounded and actionable.

Can I use this approach for large features or only early-stage ideas?▼

You can use this requirement clarification approach for both early-stage ideas and large features. It applies to any ambiguous request where you need a concrete requirement, constraint discovery, design outline, and risk-prioritized vertical-slice task planning.

What are the limitations of planning features with vertical slices?▼

Planning features with vertical slices focuses on test-first execution and risk prioritization, meaning it requires a clear hand-off flow to downstream execution tools. It does not replace direct implementation but instead provides a bounded design outline to guide subsequent development phases.