Ask / decision tickets — SOP (Catalyst-wide)

Rules v3 (Ryan, 2026-08-15 → 08-17). Applies to every Catalyst-managed Linear project and every agent, Claude or Codex. Full plugin verb: CTL-1922.

Paths. Commands below name files inside this skill's own directory as ${CLAUDE_SKILL_DIR}/…. Claude Code fills that in. On any other harness, set CLAUDE_SKILL_DIR to the absolute directory that contains this SKILL.md before running them. If you cannot, stop and report skill_dir_unresolved.

0. Setup check (first, every session)

node "${CLAUDE_SKILL_DIR}/scripts/identity-report.mjs" — one line per identity (tenant, human, team, cloud host), CTL-2300. An unresolved line is a stop-and-say: this skill files a decision for a human on a team, and an unresolved identity there is an ask that reaches nobody while looking filed.

1. What an ask ticket is

A ticket that exists ONLY to obtain one human decision or action. It is not the work — that lives on its own tickets, which the ask blocks →. Anything reaching the human as "needs you" must be an ask, never a status paragraph.

2. Creating one (the raising agent)

Then use the verb — it builds the body, files the ticket, reads it BACK out of Linear, and proves the decision trigger can parse the options AND that every --blocks relation landed. It exits 2 rather than leaving you an ask that can never be answered, or that answers into the void: