pm-iteration

Create an end-to-end iteration plan with scope, goals, and prioritized requirements.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill turns messy iteration inputs into a structured execution plan, so product teams can define scope, set measurable goals, prioritize requirements, and produce a realistic schedule.

Core Features & Use Cases

  • Iteration scope & goal setting: Define the iteration range and translate objectives into measurable outcomes (e.g., KPI targets, feature delivery, top feedback fixes).
  • Requirement capture & prioritization: Collect requirements for the iteration and rank them into P0/P1/P2 with clear “must/should/could” guidance.
  • Resource allocation & scheduling: Estimate effort across front-end/back-end/design/QA, assess risks and dependencies, and generate an iteration plan document in the repo’s docs folder.
  • V2 parallel analysis (structured planning): Supports parallel sub-assessments for requirement analysis, effort estimation, dependency identification, and risk evaluation to improve accuracy.

Quick Start

Tell the agent: “Plan my 第X次迭代(建议2周),基于我已准备的迭代编号、输入来源(A-G)、2个核心目标、需求清单与各需求的P0/P1/P2优先级,最后生成迭代计划文档并给出后续建议。”

Frequently Asked Questions about pm-iteration

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

FAQPage Schema
How do I turn iteration goals into a shippable sprint plan?

Turn iteration goals into a shippable sprint plan by defining the iteration scope, setting measurable targets, and prioritizing requirements into a structured execution schedule with allocated resources.

How do I prioritize requirements for a 2-week product iteration?

Prioritize iteration requirements by ranking captured inputs into P0, P1, and P2 tiers, applying clear must, should, and could guidance to align engineering effort with delivery goals.

What is the best way to allocate engineering resources for growth iteration work?

Allocate engineering resources for growth iterations by estimating effort across front-end, back-end, design, and QA, then assessing dependencies to generate a realistic versioned schedule.

Does this iteration planning approach document risks and acceptance criteria?

Yes, iteration planning documents risks and acceptance criteria by enforcing structured outputs, verifying prerequisites, and writing a versioned plan file directly into the repository.

Can I use this for sprint scheduling with complex dependency identification?

Yes, you can use this for sprint scheduling with complex dependencies because it supports parallel sub-assessments for requirement analysis, effort estimation, dependency identification, and risk evaluation.