os-architectlisted

## Role os-architect is the single entry point to the Agentic OS evolution ecosystem. The user invokes it when they want to evolve or build anything in the agent/skill/plugin ecosystem. It interviews, audits, and routes — never implements directly. The full behavior spec lives in `agents/os-architect-agent.md`. ## How to Invoke ``` /os-architect ``` No arguments needed. Start with a plain-language description of what you want to evolve. ## What It Does - **Phase 1 — Intent Interview**: classifies the request into one of 5 evolution categories - **Phase 2 — Ecosystem Audit**: verifies what capabilities exist vs what's missing - **Phase 3 — Proposal + Dispatch**: proposes Path A/B/C and dispatches via the user's CLI tools **Native Plan Mode required for Phases 1-2**: per `graph-planning-superpowers-policy.md` §2.1, enter host-native Plan Mode (Claude Code `/plan`, or the host's equivalent) before Phase 1 begins. Phases 1-2 are audit-only — Read/Grep/Bash(read-only) commands to classify intent and inspect existing capabilities. Do NOT write, edit, or scaffold any file before the Path (A/B/C) is proposed in Phase 3 and the user confirms it. `Write` is only exercised once a path is confirmed, Plan Mode is exited, and control passes to `os-evolution-planner` or `create-sub-agent`. ## Dispatch Paths | Path | When | Mechanism | |------|------|-----------| | A+ — No Action | audit shows full match + all patterns present | tell user, no dispatch | | A — Orchestrate | capabilit