pm-feature

Decompose product requirements into detailed development specifications from PRD and prototype inputs.

46|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/konglong87/superPM --skill pm-feature-konglong87
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-feature
Source: https://github.com/konglong87/superPM/tree/main/skills/02-solution-design/pm-feature
Command: npx skills add https://github.com/konglong87/superPM --skill pm-feature-konglong87

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you break down complex product features into detailed, development-ready specifications instead of vague feature lists.

Core Features & Use Cases

  • Feature decomposition from PRD/Prototype: Extracts feature modules, priorities, and page/interactions/statuses from PRD and prototype documents (or MVP/inputs if missing).
  • End-to-end design coverage: Produces scenarios, main/branch flows, UI elements, data logic, exception handling, technical implementation notes, and test points.
  • Quality guardrails: Enforces a verification checklist and generates the final document into docs for downstream execution.
  • Use Case: Before sprint planning or technical review, input a PRD and prototype so the team receives clear build tasks and risks tied to each feature.

Quick Start

Ask the AI to run pm-feature to break down a specific complex feature for development using your PRD and prototype documents.

Frequently Asked Questions about pm-feature

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

FAQPage Schema
How do I break down complex product features for development preparation?

Feature decomposition transforms product requirements into detailed, build-ready specs by extracting feature modules, priorities, and page interactions from PRD and prototype documents to prepare for technical review.

What should be included in UI specifications and data logic for technical review?

UI specifications and data logic for technical review should include scenarios, main and branch flows, UI elements, data logic, exception handling, technical implementation notes, and test points.

How do I split complex features from a PRD into multi-dimensional specs?

Splitting complex features from a PRD requires extracting feature modules and priorities, documenting scenarios and branch flows, and specifying UI, data, exception, and technical details into a structured output document.

Can I generate development-ready specs if I only have an MVP input instead of a full PRD?

Yes, you can generate development-ready specs using MVP inputs if full PRD and prototype documents are missing, extracting feature modules and priorities to produce end-to-end design coverage.

Does feature decomposition help with sprint planning and task allocation?

Feature decomposition helps with sprint planning by providing clear build tasks and risks tied to each feature, ensuring the team receives structured documents for downstream execution.

What is the best way to handle exception handling and test points during feature decomposition?

The best way to handle exception handling and test points during feature decomposition is to enforce a verification checklist that specifies data logic, technical implementation notes, and test points in the final document.