From cairn
Start a structured conversation about a named open question in the current milestone requirements — surfaces alternatives, trade-offs, and a recommendation to help the user reach a decision.
How this skill is triggered — by the user, by Claude, or both
Slash command
/cairn:discuss-open-questionThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Facilitates a deliberation on a named open question or deferred entry in the current milestone's `requirements.md` where the user cannot give an immediate answer. The goal is a concrete decision by the end of the conversation — not a design document.
Facilitates a deliberation on a named open question or deferred entry in the current milestone's requirements.md where the user cannot give an immediate answer. The goal is a concrete decision by the end of the conversation — not a design document.
/discuss-open-question <Short Title>
The <Short Title> must match (case-insensitive) the title of an existing Open question or Deferred entry in the document.
Example:
/discuss-open-question Arc drive technique
Follow ${CLAUDE_PLUGIN_ROOT}/shared/get-current-milestone.md to resolve <MILESTONE_DIR>. Never use a hardcoded backlog path.
Read <MILESTONE_DIR>/requirements.md. Find the entry matching the title. If no match is found, report the error and list available titles.
Before forming a view, read any source files, scripts, or design documents that bear on the question. Prefer reading the actual code over reasoning from memory. The goal is to ground the discussion in the real project state.
Open with a concise framing of what is actually at stake — one or two sentences, no preamble. Then structure the response as:
Alternatives — enumerate the realistic options (typically two to four). For each:
Recommendation — state a single preferred option with a brief rationale. Be direct; avoid hedging. If two options are genuinely equivalent, say so and explain what should break the tie.
What would change your mind — name one or two conditions under which a different option would be the right call. This helps the user push back productively.
After the opening, invite the user to push back, ask follow-up questions, or narrow the choice. Respond to each follow-up by updating your reasoning — do not simply repeat the prior framing. The conversation ends when:
When the user lands on an answer, offer to invoke /answer-open-question with that answer to record it in the document. Do not edit the document yourself — that is answer-open-question's responsibility.
<MILESTONE_DIR>/requirements.md — this skill is purely conversational.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub uhappylogic/cairn --plugin cairn