issues

Harvests session findings into clustered, proposal-level GitHub issues after operator confirmation.

9|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/eventbalancer/agent-quorum --skill issues-eventbalancer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issues
Source: https://github.com/eventbalancer/agent-quorum/tree/main/.agents/skills/issues
Command: npx skills add https://github.com/eventbalancer/agent-quorum --skill issues-eventbalancer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Valuable follow-ups, gaps, and improvement ideas surfaced during an agent session are easily lost once the conversation ends. This Skill captures those directions, clusters them, and turns them into durable, proposal-level GitHub issues that feed the delivery flow. ## Core Features & Use Cases - Session Harvesting: Re-reads the current conversation to collect deferred work, unaddressed problems, doc/test gaps, and discussed ideas, grounded only in what was actually said. - Clustering and De-duplication: Merges related directions into the smallest useful set and checks open issues via the GitHub CLI so nothing is filed twice. - Confirmed Issue Creation: Drafts solution-free, proposal-level issues following a strict contract, then creates them with gh issue create and adds them to the repository's project board backlog only after operator approval. - Use Case: After a long investigation session that surfaced several deferred improvements, run /issues to file each cluster as a tracked GitHub issue ready for the requirements and planning flow. ## Quick Start Ask the agent to run /issues to harvest this session's follow-ups and file them as GitHub issues after your confirmation.

Frequently Asked Questions about issues

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

FAQPage Schema
How do I turn conversation follow-ups into GitHub issues?

Run /issues to harvest the current session for deferred work, gaps, and ideas. The agent clusters related directions, drafts proposal-level issues, and creates them with the GitHub CLI only after you confirm.

How do I avoid filing duplicate GitHub issues from a session?

The skill lists open issues with gh issue list and matches each cluster by intent, not just wording. Clusters that already have an issue are dropped and the existing issue number is referenced in the report.

Can I filter the issue harvest to a specific topic?

Yes, pass an optional focus argument such as /issues docs gaps to narrow the harvest to a theme, surface, or subsystem. Empty arguments harvest the whole current session.

Does the skill create issues without my approval?

No. The agent proposes the clustered set with titles, summaries, and labels, then asks for confirmation using a structured question tool or plain chat. No issue is created before explicit approval.

What happens if the GitHub CLI is unavailable?

If gh is unavailable or the repository has no GitHub remote, the skill stops and reports the situation instead of guessing. Issue creation and board placement both depend on the GitHub CLI.

Why do the created issues contain no solution details?

Issues are proposal placeholders describing the problem, evidence, constraints, and open questions only. Solution-side content is withheld so the later requirements and planning steps are not biased toward a chosen approach.