openspec-aware-chorus

# OpenSpec-aware Authoring (dsh plugin) This skill is a **shared sub-procedure** invoked by the Chorus stage skills (proposal, develop, yolo) whenever the user wants spec-driven authoring through the [OpenSpec CLI](https://github.com/Fission-AI/OpenSpec). It is opt-in: - Activates when **all three** signals hold (see §1): `CHORUS_OPENSPEC_MODE` is not `off`, an `openspec/` directory exists at the project root, and the `openspec` CLI is on `PATH`. - Otherwise the calling skill falls back to its existing free-form behavior. > **Tool namespace:** Chorus MCP tools are exposed under a `mcp__chorus__` prefix on dsh (e.g. `mcp__chorus__chorus_pm_create_proposal`). Bare names are used in prose for readability — prepend `mcp__chorus__` when invoking the MCP tools directly. **Document-mirror calls do NOT go through the MCP harness at all** — they go through the `chorus` CLI (`chorus mcp call`, preferred) or the package-local `chorus-mcp-call.mjs` wrapper (fallback) (see §2 Rule 1), which talk to the Chorus MCP endpoint over HTTP using your API key, independent of the `mcp__chorus__` namespacing. --- ## §1. Detection — read the precomputed value, else run the three checks inline > **dsh difference:** the Claude Code plugin precomputes `CHORUS_OPENSPEC_ACTIVE` in a SessionStart hook. dsh has no SessionStart hook, but the **chorus-dsh bundle precomputes the same value at plugin load** and exports it as the `CHORUS_OPENSPEC_ACTIVE` environment variable — it runs the three checks belo...