council

Automate planning council discussions on YouTrack and Jira tickets via /council.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/LarryHsiao/Skadi --skill council-larryhsiao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: council
Source: https://github.com/LarryHsiao/Skadi/tree/main/skills/council
Command: npx skills add https://github.com/LarryHsiao/Skadi --skill council-larryhsiao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Council skill automates the process of planning conversations around issue-tracker tickets. It coordinates a read-only subagent (Erestor) to draft a plan, post it as a ticket comment, and wait for human verdict, ensuring that every decision is sourced from Elrond's review and that progress is tracked in a structured, versioned thread.

Core Features & Use Cases

  • Structured counsel workflow: /council invokes a cycle where Erestor drafts a plan, posts it as a comment, and awaits Elrond's verdict.
  • Tracker-agnostic routing: Works with YouTrack and Jira backends, using a hybrid routing strategy to determine the appropriate ticket and thread.
  • Safety and loop-safety: Enforces the five-counsel turn limit, read-only drafting unless Elrond provides fresh counsel, and ensures no writes without a human decision.
  • Open questions handling: Supports clarifying questions via [PARLEY] to resolve ambiguities before drafting the next version.
  • Working-directory discipline: Reads a per-project working directory binding to ensure Erestor drafts with context about the correct repo.

Quick Start

Invoke /council TICKET-ID to start or continue a planning round for that ticket.

Frequently Asked Questions about council

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

FAQPage Schema
How do I automate ticket planning discussions for Jira and YouTrack issues?

You can automate ticket planning discussions by invoking the /council command with a ticket ID. This starts a structured workflow where a read-only subagent drafts a plan, posts it as a comment, and awaits a human verdict.

What is a turn-based counsel workflow for issue tracker tickets?

A turn-based counsel workflow enforces a structured cycle where an automated agent drafts a plan, posts it as a ticket comment, and waits for human approval. It limits drafting iterations to five turns and prevents automated writes without human review.

Can I use automated ticket planning with both Jira and YouTrack backends?

Yes, automated ticket planning supports both Jira and YouTrack backends. It uses a hybrid routing strategy to determine the appropriate ticket and thread, reading the summary, description, and comment thread to generate plans.

How do I resolve ambiguities before an agent drafts a ticket plan?

You can resolve ambiguities using the [PARLEY] command to ask clarifying questions. This ensures the planning agent has the necessary context before drafting the next version of the ticket plan.

What are the limitations of automated ticket planning workflows?

Limitations include a strict five-counsel turn limit and read-only drafting unless fresh human counsel is provided. The workflow ensures no automated writes occur without a human decision and requires a per-project working directory binding for context.