plan-feature

Name: plan-feature
Availability: InStock
Author: piercingxx

Convert feature requests into scoped specifications with acceptance criteria and delivery slices.

1|Updated Jul 9, 2026

Search Tags:#edge cases #acceptance criteria #feature planning #effort estimation #product specification #non-goals #delivery slicing

Ready to run

npx skills add https://github.com/PiercingXX/xx-stack --skill plan-feature-piercingxx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/PiercingXX/xx-stack/tree/main/runtime/skills/plan-feature
Command: npx skills add https://github.com/PiercingXX/xx-stack --skill plan-feature-piercingxx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents ambiguous feature requests by converting them into a scoped, implementation-ready specification with clear trade-offs, acceptance criteria, and delivery slices.

Core Features & Use Cases

Feature Scoping & Non-Goals: Defines what is in scope and explicitly rules out what is not for v1, including the reasoning behind exclusions.
Acceptance Criteria & Edge Cases: Produces Given/When/Then acceptance criteria and documents likely edge cases with expected behavior.
Delivery Slicing & Effort Sizing: Breaks work into independent slices and provides a practical effort estimate for planning and execution.

Quick Start

Ask the AI to produce a complete Feature Specification for your requested feature, including non-goals, acceptance criteria, edge cases, delivery slices, effort estimate, and the critical implementation files section.

Frequently Asked Questions about plan-feature

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

FAQPage Schema

How do I turn an ambiguous feature request into a testable product specification?▼

To turn an ambiguous feature request into a testable product specification, you define clear trade-offs, scope boundaries, and acceptance criteria. This process converts vague asks into implementation-ready work units with explicit non-goals and documented edge cases.

What is the best way to define non-goals and edge cases during feature planning?▼

Defining non-goals and edge cases during feature planning involves explicitly ruling out out-of-scope items for v1 and documenting expected behaviors for likely edge cases. This approach ensures your delivery slicing remains focused and prevents scope creep during implementation.

How do I break down a product specification into delivery slices with effort estimation?▼

To break down a product specification into delivery slices with effort estimation, you divide the scoped requirements into independent, testable work units. This provides a practical effort estimate for each slice, streamlining execution and planning.

How does writing Given/When/Then acceptance criteria help with feature scoping?▼

Writing Given/When/Then acceptance criteria helps with feature scoping by converting ambiguous asks into structured, testable work units. This method clarifies expected behaviors and ensures the product specification is implementation-ready before development begins.

Can I use this feature planning approach for v1 scenarios with scoped trade-offs?▼

Yes, you can use this feature planning approach for v1 scenarios with scoped trade-offs. It applies directly to product scoping and converting ambiguous asks into testable units, specifically handling v1 planning scenarios by defining clear boundaries and exclusions.