Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/chorus-openspec-aware
Opt-in OpenSpec-mode authoring for Chorus PM workflows in Kiro CLI. Detects the local `openspec` CLI, scaffolds `openspec/changes/<slug>/` on disk, and mirrors Markdown files into Chorus document drafts via the `chorus-api.sh` wrapper. Required reading for the chorus-proposal, chorus-develop, and chorus-yolo skills whenever the user has the `openspec` CLI installed.
Passed 17 of 20 test cases with the skill, and 4 of 20 without it.
and 16 more in the full report
14 fixed5 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our repository uses spec-lite mode (CHORUS_SPEC_MODE=lite). What local directory path should hold the durable spec file for a feature slugged tenant-isolation?
| Checked | Without skill | With skill |
|---|---|---|
| Stores the durable spec at .chorus/specs/tenant-isolation/spec.md. | Missed | Passed |
| Avoids referencing or creating an openspec/ directory. | Passed | Passed |
The instructions your model reads when the skill loads.
This skill is a shared sub-procedure invoked by the Chorus stage skills (/chorus-proposal, /chorus-develop, /chorus-yolo) for spec-driven authoring through the OpenSpec CLI. It is the default whenever OpenSpec is usable, and a no-op otherwise:
CHORUS_SPEC_MODE=openspec or unset, and CHORUS_OPENSPEC_MODE not off, an openspec/ directory at the project root, and the openspec CLI on PATH.SPEC_MODE — spec-lite (the default when OpenSpec isn't usable) or free-form (=off).See also —
chorus-spec-lite(the lightweight fallback): OpenSpec (this skill) stays the default whenever usable. When OpenSpec is absent or disabled — orCHORUS_SPEC_MODE=lite— the mode resolves to spec-lite: a durable local.chorus/specs/<slug>/spec.md(never synced) + per-change dated folders<slug>/<YYYY-MM-DD>-<change-slug>/of Chorus-typed docs mirrored 1:1 into Chorus via the same--arg-filetransport. See/chorus-spec-lite.
When you reach a point in proposal / develop / yolo where this skill is referenced, read the resolved mode from the ## Spec Mode section (see §1) and branch on it.
The Chorus chorus main agent's agentSpawn hook resolves the spec mode once at spawn (via the shared bin/resolve-spec-mode.sh) and writes a ## Spec Mode section into your startup context; when the resolved mode is a usable OpenSpec it also carries a CHORUS_OPENSPEC_ACTIVE=1 line. If you see that section, use it; otherwise run the manual fallback below. That line is present only when CHORUS_SPEC_MODE is openspec or unset, and all three of these hold:
CHORUS_OPENSPEC_MODE is not set to off (explicit opt-out wins).openspec/ directory (i.e. someone ran openspec init here).openspec CLI is on PATH.Both signals (2) and (3) are required because the OpenSpec authoring path needs the working directory and the CLI — having one without the other leaves the workflow unrunnable. If signal (2) holds but (3) does not, surface a "OpenSpec repo detected — install with: npm i -g @fission-ai/openspec" hint to the user rather than silently choosing free-form.
If your agentSpawn context includes it, you will see something like:
## Spec Mode
CHORUS_SPEC_MODE=openspec (default — openspec/ directory + openspec CLI both present)
CHORUS_OPENSPEC_ACTIVE=1 (openspec/ directory + openspec CLI both present)
or (resolved to lite / off — no CHORUS_OPENSPEC_ACTIVE=1 line):
## Spec Mode
test cases passed, vs 4 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.