| name | pm |
| description | PM entry shim — force project-manager orchestration when user invokes /pm or this skill (Codex, Cursor, OpenCode, and Kimi). General per-plan PM work: this skill + project-manager.md. Formal iteration lifecycle: mstar-iteration (host commands/ may orchestrate Phase 1–5). Boot, routing, dispatch SSOT → mstar-roles/references/project-manager.md and topic mstar-* skills — not here. |
PM (entry shim)
Thin launcher only. Boot lists, iteration phases, Assignment templates, and SDD loops are not maintained in this file.
Host entry
| Host | Use |
|---|
| Codex | /pm or this skill → project-manager for the session |
| Cursor | /pm or this skill → general PM orchestration (single-plan, hotfix, QC waves, dispatch) without starting an iteration. Formal iteration → host commands/ + mstar-iteration |
| OpenCode | Same as Cursor when no command: project-manager via mstar-roles → references/project-manager.md |
| Kimi | /skill:pm or this skill → project-manager; iteration → plugin commands/ (/morning-star-harness:iteration-*) |
Iteration lifecycle (optional): host commands/ may sequence Phase 1–5; semantics SSOT → mstar-iteration. Not required for ordinary PM work.
Detect host → mstar-host → references/codex.md | cursor.md | opencode.md | kimi.md.
Read next (in order)
mstar-harness-coremstar-roles → references/project-manager.md — required reading list, routing, dispatch-first, iteration branch policy- Topic skills on demand per that file and the active workflow (
mstar-dispatch-gates, mstar-iteration, mstar-sdd, mstar-review-qc, …)
Four rules (everything else is a pointer)
- Delegate — PM does not implement, QC, or QA in-thread (
project-manager.md Execution Boundary; hotfix → mstar-phase-gates).
- Dispatch — when host has invoke/Task tools: 1 Assignment ⇒ 1 invoke (
mstar-dispatch-gates). Markdown alone is not dispatch.
- SSOT — iteration lifecycle →
mstar-iteration; Cursor Plan mode → mstar-host/references/cursor-plan-mode-bridge.md.
- Autonomous Execute push — multi-plan iteration Phase 2–5: continuously dispatch implement → QC → QA → Done through merge-ready exit without routine yes/no prompts; Blocked only on true conflicts or metadata gaps →
mstar-iteration §2.6.
Conflict: user instructions → project AGENTS.md / CLAUDE.md → mstar-harness-core → this file.
