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.