Skill v1.0.1
currentAutomated scan100/100+5 new
version: "1.0.1" name: pm description: "PM entry shim: force project-manager orchestration when the user invokes /pm or this skill. Boot, routing and dispatch SSOT live in mstar-roles/references/project-manager.md."
PM (entry shim)
Thin launcher only. Boot lists, iteration phases, Assignment templates, and SDD loops are not maintained in this file.
Workflow
Entry spelling differs per host; the active `mstar-host` reference owns it (command form, skill invocation form, session auto-load behaviour, iteration command names). This table keeps the routing only.
| Entry surface | Use | |
|---|---|---|
| Host ships a `/pm` command or exposes this `pm` skill | → `project-manager` for the session (general PM orchestration: single-plan, hotfix, QC waves, dispatch) | |
| Host with no command entry | Same route: `project-manager` via mstar-roles → references/project-manager.md | |
| Formal iteration (host `commands/` where shipped) | Phase 1–5 sequencing by the host commands — without an iteration the shim still serves ordinary per-plan PM |
Iteration lifecycle (optional): host commands/ may sequence Phase 1–5; semantics SSOT → `mstar-iteration`. Not required for ordinary PM work.
Codebase audit (optional): /codebase-audit command → `mstar-audit` — read-only codebase survey producing prioritized, self-contained improvement plans. Output feeds iteration-start §1 Research or normal Prepare → Execute. Dispatched by PM under Task category: audit.
Detect host → `mstar-host` → the reference that detection resolves to (per-host entry, tool shapes and plan-mode bridges live only there).
Load 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, …)
Decision Rules
- Delegate — PM does not implement, QC, or QA in-thread (
project-manager.mdExecution 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`; host Plan mode → the active host reference's plan-mode bridge (nested under
mstar-host). - 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.
Evidence
Successful entry selects project-manager and follows the owning workflow's verification and delivery gates. Loading this shim is not plan completion.
References
Open mstar-roles → references/project-manager.md for PM procedures; open the active mstar-host reference for host entry and routing details.