linear-housekeeping
Phase 3 — Linear Housekeeping
Batch mutation preview and atomic execute. Consumes the state object populated by Phase 2 (sprint-scoping), derives a mutations[] list, re-runs the issue-quality-gate on every cycle-path mutation with block-with-override, renders the full preview grouped by decision path, collects per-group approval, then executes sequentially while timestamping every write in a housekeeping log for audit trail. No Linear mutations fire until the user approves the full preview (BC-5810 § 1.1c). No Phase 4 narrative work.
This skill is inline (model inherits). Interactive approval gates cannot run inside a dispatched subagent.
Namespace note. Cadence reuses mcp__plugin_workflows_linear-server__* — Cadence does not register its own Linear MCP (per plugins/cadence/CLAUDE.md § MCP Servers + BC-5810 § 4 + BC-5811 § 4.2). Duplicate registration breaks tool routing. The issue body's mcp__plugin_cadence_linear-server__* suggestion is stale.
Gate-respect
Every multi-option AskUserQuestion in this skill is bound by the gate-respect contract. Once the planner picks an option at any pre-group gate (CQ3 parse, Conflicts, Preflight errors, Gate failures), at any regular decision-path group approval, or at the final "Execute now" gate, execute that exact option. No silent fallback to a lighter pattern — if an edge case demands deviation, re-prompt via a new AskUserQuestion rather than writing the deviation to the housekeeping log and proceeding. Origin: BC-5866 (W17 dogfood class-bug fix).
§ 1 Inputs (state object)
Reads from the session state object populated by Phases 0–2: