feature-planner

Generate an 8-section PRD with 9-framework prioritization for feature decisions.

17|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/Adelie-Squad/solosquad --skill feature-planner-adelie-squad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-planner
Source: https://github.com/Adelie-Squad/solosquad/tree/main/agents/specialists/feature-planner
Command: npx skills add https://github.com/Adelie-Squad/solosquad --skill feature-planner-adelie-squad

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and scoping product features is chaotic without a repeatable framework. This skill standardizes feature planning by generating a structured 8-section PRD and applying 9-framework prioritization to guide decisions.

Core Features & Use Cases

  • 8-section PRD drafting: Produces a comprehensive PRD document ready for review.
  • 9-framework prioritization: Systematically scores and sorts proposals to align with strategy.
  • Multi-approach comparison: Requires ≥2 approaches per feature; provides rationale if a2 is chosen or rejected.
  • Cross-functional collaboration: Includes roles and collaborators from product, design, and engineering.

Quick Start

Draft an 8-section PRD and perform a 9-framework prioritization to guide feature decisions.

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 comprehensive PRD for a new product feature?

To write a PRD, this skill converts PM insights into a structured 8-section document, covering ideation, scoping, and cross-functional collaboration details ready for team review.

What is the best way to prioritize features for a product roadmap?

The best way to prioritize features is using a 9-framework prioritization approach, which systematically scores and sorts proposals to ensure they align with your overarching product strategy.

Can I use this skill for cross-functional alignment between product, design, and engineering teams?

Yes, you can achieve cross-functional alignment as the generated PRD explicitly includes roles and collaborators from product, design, and engineering to enforce team collaboration.

How do I compare different approaches when planning a feature?

To compare approaches, the feature planning process requires evaluating at least two approaches per feature and documenting the rationale for why a specific approach is chosen or rejected.

When do I need a structured framework for feature planning?

You need a structured framework for feature planning when scoping becomes chaotic, requiring standardized 8-section PRDs and hard decision gates to guide cross-functional team alignment.

Does feature planning with hard gates slow down roadmap execution?

Feature planning with hard gates does not slow execution; it standardizes decision making by enforcing multi-approach comparisons and 9-framework prioritization to prevent chaotic scoping.