Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →chorus-aidlc/chorus-idea
Chorus Idea workflow — claim ideas, run elaboration rounds, and prepare for proposal creation.
Passed 13 of 17 test cases with the skill, and 7 of 17 without it.
and 9 more in the full report
10 fixed7 passed either way3 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/19/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
Idea 'idea-304' is already in resolved elaboration status, but the owner submitted follow-up feedback. If chorus_pm_start_elaboration is called on this idea, what parameter flag is set on the new round and what happens to the idea status?
| Checked | Without skill | With skill |
|---|---|---|
| States that isAppended is set to true on the new round. | Missed | Passed |
| States that the idea status remains elaborated. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill covers the Ideation stage of the AI-DLC workflow: claiming Ideas, running structured elaboration rounds to clarify requirements, and preparing for Proposal creation.
Ideas are the starting point of the AI-DLC pipeline. Humans (or Admin agents) create Ideas describing what they need. The PM Agent claims an Idea, runs elaboration to clarify requirements, and then moves on to /chorus-proposal to create a Proposal with document and task drafts.
Idea status lifecycle (3 stored states):
open --> elaborating --> elaborated
All post-elaboration progress (planning, building, verifying, done) is derived from the state of linked Proposals and Tasks. No agent should set Idea status directly beyond elaboration -- all transitions are side-effects of claiming, releasing, or completing elaboration.
Idea Management:
| Tool | Purpose |
|---|---|
chorus_pm_create_idea | Create a new idea in a project (on behalf of humans). Optional parentUuid derives a child idea from an existing same-project idea (single-parent lineage). |
chorus_edit_idea | Edit an existing idea's title, description, and/or lineage parent. parentUuid: another same-project idea to reparent under, null to detach to top-level, omit to leave unchanged (cycle-checked + same-project). Single-parent weak lineage — a parent shows a read-only +N derived rollup but never blocks either idea's flow. Records an "edited" activity and signals presence. |
chorus_claim_idea | Claim an open idea (open -> elaborating) |
chorus_release_idea | Release a claimed idea (elaborating -> open) |
chorus_pm_assign_idea | Assign an idea to an agent (must hold idea:write) or a user, on a human's behalf — the counterpart to chorus_claim_idea (self-claim). Silently takes over any existing assignee; an open idea moves to elaborating, any other status is preserved. Optional instanceUuid pins an agent assignment to a specific AgentInstance (agent-only) — but a project-fixed cwd target configured for the owner takes precedence and supplies the instance automatically, overriding instanceUuid. Assigning a new owner wakes it best-effort (offline still persists the assignment); re-assigning the same owner may update its pin/cwd but is wake-deduplicated. Assigning to a user notifies them with no daemon wake. Requires idea:admin. |
chorus_move_idea | Move an Idea to a different Project. Cascade-migrates the Idea and its full lineage subtree (all descendant Ideas; the moved root is detached from any parent left behind), all linked Proposals (any status), all materialized Documents and Tasks, and all related Activities atomically. Comments, TaskDependency, AcceptanceCriterion, AgentSession, SessionTaskCheckin, Notification history, and Task assignees are NOT modified. Returns moved: { ideas, proposals, documents, tasks, activities } counts. Requires idea:write (no project:* bit) plus Editor access on both the source and target projects — for an agent, its owner's effective level; a target you cannot see returns Target project not found. Fails without moving anything if a live assignee in the moved set lacks Editor on the target; the error names every blocked assignee. |
Requirements Elaboration:
| Tool | Purpose |
|---|---|
chorus_pm_start_elaboration | Generate an elaboration round (first, follow-up, or appended-after-resolution) |
chorus_pm_validate_elaboration | Mark the whole elaboration complete (requires idea:admin; requires human confirmation first) — callable by the Idea's assignee, or a non-assignee idea:admin gateway (wakes the assignee) |
chorus_pm_skip_elaboration | Skip elaboration for trivially clear Ideas |
test cases passed, vs 7 / 17 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.