skills.rest
FernanSuoza
FernanSuozaCOMMUNITY
Explore all skills by this author →
GitHub

prod-feature-organization-and-planning

Group backlog items into features with metadata, linked stories, and acceptance criteria.

Updated Mar 22, 2026
Search Tags:#planning#roadmap#prioritization#governance#backlog#feature#stories
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill prod-feature-organization-and-planning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prod-feature-organization-and-planning
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/prod-feature-organization-and-planning
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill prod-feature-organization-and-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog items often lack a coherent structure, making planning, prioritization, and stakeholder communication difficult.

Core Features & Use Cases

  • Group related backlog items into features with metadata to guide planning and ensure alignment with goals.
  • Provide feature overviews, linked stories, and acceptance criteria to improve transparency and governance.
  • Enable quick start and ongoing maintenance of feature backlog to support iterative delivery.

Quick Start

Organize the current backlog into a concise feature plan and generate the initial FEAT backlog items.

Frequently Asked Questions about prod-feature-organization-and-planning

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

FAQPage Schema
How do I organize a product backlog into clear features for roadmap planning?▼

To organize a product backlog into features, group related backlog items, stories, and bugs into coherent structures with metadata to improve planning and stakeholder visibility.

What is the best way to structure backlog items for prioritization and governance?▼

Structuring backlog items for prioritization involves creating feature metadata, linking child stories, and establishing priorities, scope, and acceptance criteria to guide governance and alignment.

How do I group related user stories and bugs under a single feature?▼

Group related user stories and bugs by identifying coherent features within the backlog, linking the child stories to the parent feature, and generating feature overviews to consolidate visibility.

Can I use this approach to define scope and acceptance criteria for backlog features?▼

Yes, you can define scope and acceptance criteria for backlog features by applying feature metadata to grouped backlog items, ensuring transparency and clear governance for iterative delivery.

How do I generate an initial feature backlog from existing unstructured items?▼

Generate an initial feature backlog by quickly organizing existing unstructured items into a concise feature plan, creating the initial FEAT backlog items to support ongoing maintenance and delivery.

When do I need to group backlog items into features instead of keeping a flat list?▼

You need to group backlog items into features when the flat list lacks coherent structure, making planning, prioritization, and stakeholder communication difficult and obscuring roadmap goals.

Related Skills

Explore More Product & Management Skills→
blazefluzblazefluz

Work Intake Manager

Convert natural language requests into structured user stories, epics, and bug reports.

Community
Advanced
shalevaminshalevamin

sprint-plan

Estimate team capacity, select stories, map dependencies, and identify risks for sprint planning.

Community
Intermediate
EpiphyticEpiphytic
7

roadmap-management

Plan and prioritize product roadmaps using RICE, MoSCoW, and ICE frameworks.

Official
Intermediate
C0ntr0lledCha0sC0ntr0lledCha0s
3

planning-sprints

Automate sprint planning and backlog refinement with prioritization frameworks.

Community
Intermediate