feature-planner

Generate phase-based feature plans with quality gates and approval workflows.

Updated Dec 26, 2025

Ready to run

npx skills add https://github.com/landfill/devtool-and-rule --skill feature-planner-landfill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-planner
Source: https://github.com/landfill/devtool-and-rule/tree/main/skills/feature-plan
Command: npx skills add https://github.com/landfill/devtool-and-rule --skill feature-planner-landfill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill generates structured, phase-based feature plans with quality gates and incremental delivery, ensuring clear scope, test-driven development, and explicit approvals before work begins.

Core Features & Use Cases

Phase-based planning: 3-7 phases, each delivering runnable functionality within 1-4 hours
Quality Gates: Red-Green-Refactor cycles, with measurable test coverage targets
Documentation: auto-generates plan docs at docs/plans/PLAN_<feature-name>.md
Approval Workflow: Uses explicit user approval before proceeding to next phase

Quick Start

Provide a feature name and context, then run the planner to generate a complete phase-based plan with gated quality checks. Review the plan, then request approval to proceed.

Frequently Asked Questions about feature-planner

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

FAQPage Schema

How do I create a phase-based feature plan with quality gates?▼

Phase-based feature planning breaks work into 3-7 phases of 1-4 hours each, with quality gates between phases. This Skill automates that structure, generating roadmaps with Red-Green-Refactor cycles, test coverage targets, and explicit approval checkpoints before proceeding to the next phase.

What does a structured feature plan document include?▼

A structured feature plan documents scope, deliverables, test-driven development cycles, quality gates, user approvals, and rollback strategies organized by phase. This Skill auto-generates these plans as docs/plans/PLAN_<feature-name>.md with measurable test coverage targets and risk assessment for each phase.

Can I use phase-gated planning for breaking down large features into smaller tasks?▼

Yes. Phase-gated planning organizes large features into incremental, runnable phases with explicit scope and approval workflows. Each phase delivers testable functionality within 1-4 hours, making it ideal for task breakdown, roadmap creation, and development strategy structuring.

How does test-first development fit into a phase-based roadmap?▼

Test-first development integrates through Red-Green-Refactor cycles enforced at each quality gate. This Skill embeds test coverage targets and measurable quality checks into every phase, ensuring code meets standards before progressing and satisfying test-driven development requirements.

What happens before I can proceed to the next phase in a feature plan?▼

Before advancing phases, explicit user approval is required after quality gates are met. This includes verification of test coverage targets, Red-Green-Refactor completion, and any risk assessment or rollback strategy validation for that phase.