council-resolve

Resolve active governance threads and apply lifecycle verdicts to channel state.

Updated May 7, 2026
One-click install
npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-resolve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council-resolve
Source: https://github.com/tmalcolm-0607/mad-council-claw/tree/main/.claude/skills/council-resolve
Command: npx skills add https://github.com/tmalcolm-0607/mad-council-claw --skill council-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need for time-consuming formal council reviews for routine thread resolutions, and automates the application of pending governance lifecycle verdicts (such as ownership transfers or triage decisions) that would otherwise require manual, error-prone state updates across channel files.

Core Features & Use Cases

  • Informal Thread Resolution: Mark active threads as resolved without a formal council review, automatically triggering a 60-minute archive timer to keep workspaces clean.
  • Lifecycle Verdict Application: Atomically apply pending governance verdicts (OWNERSHIP_TRANSFER, TRIAGE_ACCEPT, TRIAGE_REJECT) to channel state, with automatic file renaming to mark verdicts as consumed and prevent duplicate processing.
  • MAD Task Integration: Automatically check off referenced task IDs in tasks.md for MAD-enabled channels when resolving threads, reducing manual follow-up work.
  • Use Case: A software engineering team using the MAD Council governance system can use this skill to quickly close out completed feature threads or apply a pending triage accept verdict to move a work item to "ready" status without scheduling a full council review session.

Quick Start

Use the council-resolve skill to resolve the active thread "v4-aligned-training" in the es-training channel with a summary noting all seed runs are complete and tasks T003 through T006 are finished.

Frequently Asked Questions about council-resolve

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

FAQPage Schema
How do I close governance threads without a formal council review?

Thread resolution without formal council review is achieved by marking active threads as resolved, which automatically triggers a 60-minute archive timer to keep workspaces clean and applies pending lifecycle verdicts atomically.

How does atomic channel state update work when applying pending lifecycle verdicts?

Atomic channel state updates apply pending governance verdicts like OWNERSHIP_TRANSFER or TRIAGE_ACCEPT to channel state safely, automatically renaming files to mark verdicts as consumed and prevent duplicate processing or concurrency conflicts.

Can I automate task checkoff in tasks.md when resolving MAD-enabled channel threads?

Yes, MAD task integration automatically extracts referenced task IDs and checks them off in tasks.md when resolving threads in MAD-enabled channels, eliminating manual follow-up work for completed feature tasks.

What is the best way to process ownership transfers in a MAD Council workflow?

Processing ownership transfers is handled by applying pending OWNERSHIP_TRANSFER verdicts atomically to channel state, ensuring concurrency safety and compliance with governance rules without scheduling a full council review session.

Do I need a formal council session to apply triage decisions to channel state?

No, applying triage decisions does not require a formal council session; pending TRIAGE_ACCEPT or TRIAGE_REJECT verdicts can be applied directly to channel state with automatic file renaming to prevent duplicate processing.