Dependency pre-check (before running the workflow)
This workflow entry point write-prd is only responsible for orchestration; installing it alonewill notautomatically install the skills it invokes.
Required skills:pm-demand、pm-clarify、pm-priority、pm-mvp、pm-docs.
New products additionally require pm-brainstorm; it may be skipped only when relevant brainstorming artifacts already exist or the user explicitly skips it.
First use the current platform's skill list to check whether the required skills are available.If dependencies are missing, stop the workflow, do not pretend it has been executed; inform the user of the missing skills and provide installation instructions. Do not install or skip on your own. Full installation command (installing only this entry point is not enough):
npx skills add https://github.com/konglong87/superPM --skill write-prd pm-demand pm-clarify pm-priority pm-mvp pm-docs pm-brainstorm
If Node.js/npm is not available, you can manually install the full skill package according to the repository README; after installation, re-check the skill list, then continue the process.
Workflow contract
When the full pack is installed, also consult skills/_shared/workflow-contract.md; standalone installation follows the complete steps below. For a new product idea, first run /pm-brainstorm unless relevant work already exists or the user explicitly opted out. Inspect existing outputs for relevance and ask which stages to reuse; do not skip a missing prerequisite merely because docs/ exists. Pause between stages that create or overwrite documents; use ordinary chat if AskUserQuestion is unavailable.
Execution flow
- Demand validation — Execute /pm-demand. Confirm user pain points and evidence.
- Requirement clarification — Execute /pm-clarify. Confirm boundary conditions and acceptance criteria.
- Prioritization — Execute /pm-priority. Sort confirmed requirements and record the rationale for trade-offs.
- MVP scoping — Execute /pm-mvp. Include only the prioritized necessary scope.
- Document generation — Execute /pm-docs. Make features and acceptance criteria traceable to requirements, priorities, and the MVP.
When complete, list only the files actually generated; it is recommended to run /pm-prd-review to verify document quality.