pm-change

Collect requirement changes, assess impact, determine approval levels, and record execution plans.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product and project teams avoid uncontrolled scope creep by systematically capturing requirement changes, evaluating their impact, and recording decisions and execution plans.

Core Features & Use Cases

  • Structured change intake: Collects change source, type, and execution context through guided questioning to ensure nothing critical is missing.
  • Impact assessment & approval routing: Evaluates affected areas (functions, timeline, architecture, testing, UX, data migration, integrations, cost) and maps impact to an approval level (PM / PM+Tech / CCB / steering committee).
  • Change record & traceability: Writes a complete change log to docs/04-风控管理/需求变更记录.md, including summaries, decision outcomes, and execution status.

Quick Start

Tell the AI: "Run the pm-change workflow to document a new requirement change, assess its impact and approval level, and update the change record in docs/04-风控管理/需求变更记录.md."

Frequently Asked Questions about pm-change

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

FAQPage Schema
What is requirement change management and when do I need a structured change control process?

Requirement change management systematically captures change requests and assesses their impact on scope, timeline, and architecture. You need this process during in-project scenarios to prevent uncontrolled scope creep and ensure traceable risk decisions.

How do I assess the impact of a requirement change and determine the necessary approval level?

Assess requirement change impact by evaluating affected areas like functions, technical architecture, testing scope, and data migration. Map the resulting impact to an approval level, routing the decision to the PM, PM+Tech, CCB, or steering committee.

How to document a requirement change request and maintain traceability for risk management?

Document a requirement change request by collecting the change source, type, and execution context. Maintain traceability by writing the summary, decision outcome, and execution status to a structured change record log in docs/04-风控管理/需求变更记录.md.

Can I use this change control workflow for technical architecture and third-party integration updates?

Yes, this change control workflow applies to in-project scenarios involving technical architecture, third-party integrations, UX, and data migration. It guides multi-step intake to ensure all affected impact dimensions are covered before approval routing.

What is the best way to manage scope creep and record execution plans for product workflow changes?

The best way to manage scope creep is through structured impact assessment and approval routing for product workflow changes. This ensures execution plans are recorded with full traceability, capturing decision outcomes and updating the change log systematically.