| name | mstar-roles |
| description | Morning Star role prompt hub — `agents/*.md` shells plus full behavior in `references/*.md`, each with a **Required Skill Dependencies** list (which `mstar-*` topic skills to load after `mstar-harness-core`). Always load for any Morning Star role (`project-manager`, `product-manager`, `architect`, `fullstack-dev`, `fullstack-dev-2`, `frontend-dev`, `qa-engineer`, `qc-specialist*`, `ops-engineer`, `writing-specialist`, `prompt-engineer`). Cross-role **Role → typical topic skills** summary in this SKILL.md; per-role lists in `references/*.md` are authoritative for that role's session. Full topic skill index → **`mstar-harness-core`**. |
Load Order (Required)
When a Morning Star role starts work in a session:
- Read
mstar-harness-core first (SKILL.md), then only the topic mstar-* skills required for this role/task (see matrix below — do not read all topic skills by default).
- Read this
mstar-roles skill.
- Resolve role mapping and parameter table below.
- Read the corresponding
references/<role>.md file — each role file lists Required Skill Dependencies for that role (canonical per-role load list).
- Expand placeholders from role parameters before execution.
If any conflict appears, mstar-harness-core remains the authoritative source for lifecycle, gates, routing, and invariants. The table below is the cross-role summary; when a role file lists different on-demand skills, follow the role file for that session.
Role Reference Mapping
| Agent id | Reference file | Parameterized slots |
|---|
project-manager | references/project-manager.md | — |
product-manager | references/product-manager.md | — |
architect | references/architect.md | — |
fullstack-dev | references/fullstack-dev-shared.md | role_id, track |
fullstack-dev-2 | references/fullstack-dev-shared.md | role_id, track |
frontend-dev | references/frontend-dev.md | — |
qa-engineer | references/qa-engineer.md | — |
qc-specialist | references/qc-specialist-shared.md | role_id, reviewer_index, focus, report_suffix |
qc-specialist-2 | references/qc-specialist-shared.md | role_id, reviewer_index, focus, report_suffix |
qc-specialist-3 | references/qc-specialist-shared.md | role_id, reviewer_index, focus, report_suffix |
ops-engineer | references/ops-engineer.md | — |
writing-specialist | references/writing-specialist.md | — |
prompt-engineer | references/prompt-engineer.md | — |
Role → typical topic skills (after mstar-harness-core)
| Role | Typical adds |
|---|
project-manager | mstar-dispatch-gates, mstar-phase-gates, mstar-plan-conventions, mstar-roles ref; + references/project-manager/qa-trigger-matrix.md for QA gate tiers; + mstar-review-qc before QC; + mstar-branch-worktree / mstar-plan-artifacts as the round requires; + mstar-skill-authoring for skill work; + mstar-iteration for iteration lifecycle (start/drive/close); + mstar-strategy for strategic alignment; + mstar-compound / mstar-compound-refresh pre-loaded by mstar-iteration § iteration-close |
fullstack-dev*, frontend-dev | mstar-coding-behavior, mstar-dispatch-gates, mstar-branch-worktree (if repo writes); plan path symbols from mstar-plan-conventions (minimal); mstar-design-md when implementing styled UI |
qc-specialist* | mstar-branch-worktree, mstar-plan-artifacts (review bundle paths); references/qc-specialist/ (workflow, checklist, template, lenses); mstar-design-md when reviewing UI |
qa-engineer | mstar-branch-worktree, mstar-plan-artifacts (closing R#); references/qa-engineer/acceptance-gate.md; mstar-design-md when verifying visual output |
architect, product-manager | mstar-phase-gates (Prepare), mstar-plan-artifacts (knowledge/specs); mstar-design-md (creator + design intent); mstar-strategy (STRATEGY.md creation/maintenance) |
ops-engineer | mstar-coding-behavior, mstar-branch-worktree |
prompt-engineer | All topic skills when editing harness text |
Use skill names (not absolute filesystem paths) in role references.
Role references/*.md files include explicit NEVER sections (anti-recursion, tool misuse, Git discipline). Treat those bullets as hard gates alongside mstar-harness-core; do not treat them as optional style tips.
Parameter Table (SSOT)
Dev track (fullstack-dev family)
| role_id | track | Meaning |
|---|
fullstack-dev | primary | Backend-led primary implementation track |
fullstack-dev-2 | parallel_secondary | Second implementation track for parallel independent modules |
QC reviewer (qc-specialist* family)
Default (SDD): plan QC tri-review — qc-specialist / qc-specialist-2 / qc-specialist-3 → {SDD_DIR}/review/qc1.md…qc3.md + qc-consolidated.md when Execution mode: sdd.
Exception (inline / hotfix): single-seat → {SDD_DIR}/review/qc.md (QC mode: single).
| role_id | reviewer_index | focus | report_suffix |
|---|
qc-specialist | 1 | Architecture coherence and maintainability risk | qc1 → {SDD_DIR}/review/qc1.md |
qc-specialist-2 | 2 | Security and correctness risk | qc2 → {SDD_DIR}/review/qc2.md |
qc-specialist-3 | 3 | Performance and reliability risk | qc3 → {SDD_DIR}/review/qc3.md |
PM consolidated (tri mode): {SDD_DIR}/review/qc-consolidated.md (same folder; no <plan-id> basename prefix) + durable main-plan summary. Naming SSOT: mstar-plan-artifacts/references/plan-files-and-reports.md.
Maintenance Rules
- Edit behavior in
references/*.md.
- Edit role family parameters in this file.
- Keep shared-family roles (
fullstack-dev*, qc-specialist*) on one shared reference file.
- Add new roles by updating mapping, parameters (if needed), and adding corresponding
agents/*.md shell.
