make-decisions

Drains the needs-decision GitHub issue queue by presenting options, recording rulings, and removing labels.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill make-decisions-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: make-decisions
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/make-decisions
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill make-decisions-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open questions labelled needs-decision pile up on a GitHub project board and block work from being ranked and promoted. This Skill reads every queued issue, presents each as a briefed question with options and a recommendation, records the architect's ruling on the issue, and removes the label so downstream triage can proceed. ## Core Features & Use Cases - Queue Sweeps: Detects issues that already have a ruling recorded but still carry the label, and issues that are labelled but have no prepared question, handling each appropriately. - Decision Briefing: Presents each question with a plain-language briefing, verbatim prepared options, and a pros/cons table covering every alternative before asking via AskUserQuestion. - Same-Turn Close-Out: Applies each ruling immediately — comments the decision, splices the chosen option's pre-written body text into the issue, refreshes review markers, and removes the needs-decision label. - Use Case: Run daily before standup: the Skill lists all open needs-decision issues on the repo, walks the architect through each fork with a recommendation, and leaves the queue empty so /fill-ready can rank and promote the unblocked items. ## Quick Start Run /make-decisions to review and rule on every open needs-decision issue on the board.

Frequently Asked Questions about make-decisions

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

FAQPage Schema
How do I process a queue of GitHub issues waiting on decisions?▼

List open issues with the needs-decision label using gh issue list, present each as a question with options and a recommendation, then record the ruling as a comment and remove the label. This Skill automates that full loop in one run.

How to present decision options to a stakeholder for approval?▼

Write a short briefing covering what the thing is, what happens today, the real dispute, and what each side costs, then present options in a pros/cons table with an honest case for and against every alternative. Ask via AskUserQuestion in batches of up to four.

Does this Skill move or prioritize issues on the project board?▼

No. It never moves cards or chooses what the team works on. Removing the needs-decision label is the entire delivery; a separate fill-ready workflow ranks and promotes the unblocked items.

What happens when the answer is not one of the prepared options?▼

If the decision-maker reframes the question, the block is rewritten and the label stays on for the next run. If the answer changes the blast radius or matches no option, a task-reviewer agent is re-run on that issue with the new decision.

When should an item be relabelled senior instead of needs-decision?▼

Relabel senior when preparing the question would take more than a few minutes of reading, when an item has been deferred twice, or when the ruling is that the work is hard either way. The two labels are orthogonal and can coexist while a ruling is outstanding.