Dependency installation pre-check (before executing the workflow)
This workflow entry plan-launch is only responsible for orchestration; installing it alonewill notautomatically install the skills it invokes.
Required skills:pm-risk、pm-cross、pm-agile、pm-release。
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 is not enough):
npx skills add https://github.com/konglong87/superPM --skill plan-launch pm-risk pm-cross pm-agile pm-release
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. Reuse relevant existing artifacts after confirmation. Pause before each next stage; if AskUserQuestion is unavailable, ask in ordinary chat and wait. Do not claim a release is safe merely because a plan document exists.
Execution flow
- Risk assessment — Execute /pm-risk. Identify risks, mitigation measures, and rollback trigger conditions.
- Cross-team coordination — Execute /pm-cross. Clarify owners, dependencies, and escalation paths.
- Agile delivery — Execute /pm-agile. Clarify the remaining delivery work and checkpoints.
- Release planning — Execute /pm-release. Develop the launch and rollback plan based on risks, owners, and delivery status.
When complete, list only the files actually created; formal launch still requires real acceptance and approval by the decision-maker.