speckit-council-triage

Applies council suggestions to plan.md and writes the append-only decision record.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-council-triage-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-council-triage
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/speckit-council-triage
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill speckit-council-triage-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After an adversarial council reviews a spec-kit plan, someone must decide what to do with every suggestion it raised. This Skill dispositions each council suggestion (accepted, rejected, or deferred), applies accepted fixes to plan.md, and writes a permanent, auditable decision record so no review feedback is silently dropped. ## Core Features & Use Cases - Suggestion Dispositioning: Assigns exactly one disposition with mandatory written rationale to every row in the council's suggestions.md, enforcing the D13.5 reasoning requirement for rejections and deferrals. - Convergence & Delta Check: When blocking suggestions exist, commits one plan revision and dispatches a chairman subagent in delta-check mode to confirm resolution, never allowing a second full council round. - Autonomy Gate Handling: Reads profile.yaml to either leave the human gate pending or auto-write the approval section under full_auto mode, while refusing to auto-approve through unresolved blocking findings. - Use Case: After running /speckit-council on a feature plan, invoke this Skill to triage the round: it edits plan.md with accepted fixes, appends the Round N section to council/decision-record.md, records traces, and reports the next command to run. ## Quick Start Run /speckit-council-triage in a spec-kit repository after a council round has produced suggestions.md, optionally passing triage leanings such as "reject R1-S02" as arguments.

Frequently Asked Questions about speckit-council-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply council review suggestions to a spec-kit plan?

Run /speckit-council-triage after a council round completes. It reads round-N/suggestions.md, assigns each suggestion a disposition with rationale, edits plan.md for accepted items, commits the revision, and appends the round record to council/decision-record.md.

What happens when a council suggestion is marked blocking?

Blocking suggestions default to accepted, driving exactly one plan revision commit. The Skill then dispatches a chairman subagent in delta-check mode to verify each blocking ID is resolved, and escalates to a human if any remain blocking.

Can council triage auto-approve the human gate?

Yes, but only when profile.yaml sets gates.council.mode to auto under full_auto and the round converged cleanly with zero unresolved blocking items. A residual blocking finding always prevents auto-approval and requires human intervention.

Why must rejected or deferred suggestions include rationale?

The decision-record contract (D13.5/R3) mandates substantive reasoning for every non-acceptance so future readers understand the decision. Deferred items must also name a resurfacing point, such as a follow-up spec or an entry in the decisions-and-ideas log.

What are the prerequisites for running council triage?

The repository needs spec-kit initialized with a .specify/ directory, an existing plan.md for the feature, and at least one council round with suggestions.md written by /speckit-council. The council extension must be installed under .specify/extensions/council/.

Is it safe to re-run council triage on the same round?

Yes. The Skill is idempotent: if decision-record.md already contains a complete Round N section with convergence resolved, it reports completion and stops without re-applying edits or duplicating commits.