feature-planner

Plan and document feature specs with acceptance criteria and data flow.

Updated Mar 17, 2026

Search Tags:#planning #requirements #spec #edge-cases #feature #acceptance-criteria

Ready to run

npx skills add https://github.com/SPRAGE/dev-template --skill feature-planner-sprage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-planner
Source: https://github.com/SPRAGE/dev-template/tree/main/templates/python/.claude/skills/feature-planner
Command: npx skills add https://github.com/SPRAGE/dev-template --skill feature-planner-sprage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers plan individual features for an existing project, ensuring requirements, edge cases, data flows, acceptance criteria, and dependencies are considered before implementation.

Core Features & Use Cases

Interactive brainstorming to clarify requirements
Generates a structured feature spec file placed in a features/ folder
Asks targeted questions to cover edge cases, data flow, dependencies
Produces a clean, actionable spec ready for implementation

Quick Start

Plan a feature for an existing project and generate a complete feature spec.

Frequently Asked Questions about feature-planner

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

FAQPage Schema

How do I write a feature spec with acceptance criteria and edge cases for an existing project?▼

To write a feature spec, define the scope, data flow, acceptance criteria, edge cases, and dependencies. This skill interactively asks targeted questions to clarify requirements, then generates a structured spec file in a features/ folder ready for implementation.

What should be included in a feature planning document for software development?▼

A feature planning document should include a summary, motivation, detailed description, data flow, acceptance criteria, edge cases, dependencies, scope, and open questions. This ensures requirements are fully considered before development begins.

Can I use interactive brainstorming to clarify requirements before coding a new feature?▼

Yes, interactive brainstorming clarifies requirements before coding by asking targeted questions about edge cases, data flow, and dependencies. This produces a clean, actionable feature spec capturing all necessary production requirements.

What is the best way to document data flow and dependencies for a new software feature?▼

The best way to document data flow and dependencies is through a structured feature spec. This skill guides you interactively to capture scope, data flow, and dependencies, outputting a production-ready spec file for your project.

Does planning a feature spec help identify open questions and edge cases?▼

Planning a feature spec helps identify open questions and edge cases by interactively questioning requirements. The generated spec file includes dedicated sections for edge cases and open questions, ensuring potential issues are documented before implementation.