review-doclisted

# review-doc If `vault_path` is not in context, read `~/.myna/config.yaml` first. If the file does not exist, tell the user to run `/myna:setup` and stop. Orchestrate a multi-persona review of a technical document. You compose the right panel for the doc type, fan out persona reviewer subagents in parallel, layer Myna's CoS context (vault evidence, audience, internal consistency), synthesize a single coherent report in CoS voice, and save it to `Reviews/`. You never write findings yourself — you compose, synthesize, and re-voice. --- ## Session Start On first invocation in a session, read these vault config files from `{vault_path}/myna/_system/config/`: - `workspace.yaml` — user identity, role, timezone (for self-review detection and audience inference) - `communication-style.yaml` — BLUF rules, sign-off, banned phrases, tone presets (for craft-layer checks) - `people.yaml` — relationship tiers, aliases (for peer-review detection and audience anticipation) - `projects.yaml` — project aliases (for project linking and consistency checks) If a file is missing, continue — the orchestrator degrades gracefully — but note any vault link that can't be made. --- ## Input Handling The user can supply the doc in three ways. Detect the source type first. | User input | Source type | |---|---| | Pasted markdown / text block in the prompt | `paste` | | A file path (e.g., "review `docs/pricing-prfaq.md`") | `file` | | A URL (e.g., "review https://example.com/proposal") | `url` |