What problem does it solve?
Teams using Chorus for AI-driven project management who also author specs with the OpenSpec CLI face duplicated effort: documents live in local openspec/changes/ folders but must be re-typed into Chorus document drafts, burning tokens and risking content drift. This skill automates detection, scaffolding, and byte-exact mirroring between the two systems.
Core Features & Use Cases
- Three-check OpenSpec detection: Reads the precomputed
CHORUS_OPENSPEC_ACTIVE value or runs inline checks for the openspec CLI, an openspec/ directory, and the opt-out environment variable.
- Byte-exact document mirroring: Fills the
content field of Chorus document drafts from local file bytes via chorus mcp call --arg-file (or a package-local wrapper fallback), never re-typed by the LLM.
- Full lifecycle coverage: Scaffolds
openspec/changes/<slug>/, maps proposal.md/design.md/spec.md to prd/tech_design/spec document types, and runs openspec archive with spec mirror-back after the last task is verified.
- Use Case: A product manager asks their dsh agent to draft a proposal for a new CSV export feature; the skill detects OpenSpec mode, scaffolds the change folder, creates the Chorus proposal with a slug provenance line, and mirrors all spec documents into Chorus drafts without re-typing content.
Quick Start
Ask your agent to draft a Chorus proposal for your feature idea using OpenSpec mode, and it will detect the openspec CLI, scaffold the change folder, and mirror the documents into Chorus drafts automatically.