feature-planner

Name: feature-planner
Availability: InStock
Author: withaicolleague

Convert vague feature ideas into phase-based roadmaps with approval gates.

Updated Jan 27, 2026

Search Tags:#planning #roadmap #strategy #plan #gates #phases #approval

Ready to run

npx skills add https://github.com/withAIcolleague/andongintro --skill feature-planner-withaicolleague

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Feature Planner addresses the challenge of turning vague feature ideas into concrete, phase-based roadmaps with built-in gates and explicit approvals.

Core Features & Use Cases

Phase-based planning: breaks work into 3-7 phases, each delivering runnable functionality within 1-4 hours.
Quality gates: enforce validation and readiness checks before advancing to the next phase.
Approval workflow: incorporate an explicit AskUserQuestion step to obtain stakeholder consent before work begins, ensuring alignment.

Quick Start

Define a four-phase plan with clear deliverables, gates, and an explicit approval step before advancing.

Frequently Asked Questions about feature-planner

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

FAQPage Schema

How do I turn vague feature ideas into a structured product roadmap with phase-based planning?▼

Phase-based planning breaks vague feature ideas into 3-7 structured roadmap phases, each delivering runnable functionality within 1-4 hours. Quality gates enforce validation checks before advancing to the next phase.

What's the best way to add stakeholder approval steps to a development roadmapping workflow?▼

Development roadmapping incorporates an explicit AskUserQuestion step to obtain stakeholder consent before work begins on each phase. This approval workflow ensures alignment and prevents advancing without explicit user confirmation.

Can I enforce Red-Green-Refactor style work within a multi-phase task breakdown?▼

Task breakdown enforces Red-Green-Refactor style work across 3-7 phases with 1-4 hours per phase. It applies YAML metadata to structure the phases and requires user approval before proceeding to subsequent tasks.

Does phase-based planning support quality gates and readiness checks before advancing to the next phase?▼

Quality gates in phase-based planning enforce validation and readiness checks before advancing to the next phase. This ensures each phase delivers its intended functionality and meets criteria before subsequent work begins.

Why does my feature planning require explicit approval before starting each phase?▼

Feature planning requires explicit approval before each phase to solve the problem of misalignment on vague ideas. Incorporating an explicit AskUserQuestion step obtains stakeholder consent, ensuring structured roadmap alignment before work begins.

When do I need to use YAML metadata in a strategy and roadmap planning process?▼

YAML metadata is needed in roadmap planning to enforce structured phase definitions across 3-7 phases. It standardizes task breakdown data and supports the Red-Green-Refactor style work applied during the planning process.