Phase 0: PM Planning (순수 로직)

Automate product management planning with scoping, prioritization, and risk assessment.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/vp-k/auto-complete-loop --skill phase-0-pm-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Phase 0: PM Planning (순수 로직)
Source: https://github.com/vp-k/auto-complete-loop/tree/main/skills/pm-planning
Command: npx skills add https://github.com/vp-k/auto-complete-loop --skill phase-0-pm-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, bash, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the initial Product Management planning phase, ensuring a thorough understanding of the project's scope, user needs, and potential risks before development begins.

Core Features & Use Cases

  • Project Scoping: Determines project size (Small, Medium, Large) based on requirements.
  • User & Value Definition: Establishes Problem Statements, Personas, Jobs-to-be-Done (JTBD), and Trade-offs.
  • Requirement Prioritization: Uses MoSCoW, ICE, and Kano methods for feature prioritization and round-based planning.
  • Risk Assessment: Identifies and prioritizes assumptions and conducts a pre-mortem analysis to uncover potential failures.
  • Stakeholder Mapping: For large projects, maps stakeholders and outlines communication plans.
  • Use Case: Kickstart a new software project by defining its core purpose, target audience, essential features, and potential pitfalls, ensuring alignment before any code is written.

Quick Start

Initiate the PM planning phase for a new project using the provided user requirements.

Frequently Asked Questions about Phase 0: PM Planning (순수 로직)

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

FAQPage Schema
How do I automate project scope definition and user needs analysis for software development?

Automating project scope definition involves analyzing user requirements to determine project size, identify personas, define Jobs-to-be-Done (JTBD), and map trade-offs. This ensures a thorough understanding of user needs before development begins.

What is the best way to prioritize features using MoSCoW, ICE, and Kano methods?

Feature prioritization using MoSCoW, ICE, and Kano methods categorizes requirements by must-have criteria, impact-confidence-ease scoring, and customer satisfaction factors. This structured approach enables round-based planning for software projects.

How do I conduct a pre-mortem analysis and risk assessment for a new software project?

Conducting a pre-mortem analysis and risk assessment identifies and prioritizes project assumptions to uncover potential failures before development starts. This structured risk evaluation prevents pitfalls and ensures project alignment.

Do I need bash and jq to run automated PM planning scripts?

Yes, you need bash and jq dependencies to execute the PM planning scripts. These tools process user requirements and automate the structured planning steps, generating project scope, feature priorities, and risk assessments.

Can I use automated PM planning for large projects requiring stakeholder mapping?

Yes, automated PM planning supports large projects by mapping stakeholders and outlining communication plans. It scales the planning phase to include stakeholder analysis alongside standard feature prioritization and risk assessment.