decide-issue

Score implementation options using codebase evidence and annotate issue files.

7|2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill decide-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decide-issue
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/.gemini/skills/decide-issue
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill decide-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves stalled development issues where multiple proposed implementation options exist, preventing decision paralysis and ensuring the best technical path is chosen.

Core Features & Use Cases

  • Evidence-Based Scoring: Automatically gathers codebase evidence to score options across consistency, simplicity, testability, and risk.
  • Automated Resolution: Updates issue frontmatter and annotates the winning implementation directly in the issue file.
  • Use Case: When an issue contains competing architectural approaches, this skill analyzes the codebase to determine which option aligns best with existing patterns and risk profiles.

Quick Start

Run the decide-issue skill on issue FEAT-948 to automatically evaluate and select the best implementation option.

Frequently Asked Questions about decide-issue

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

FAQPage Schema
How do I resolve competing implementation options in an issue tracking system?

Resolve competing implementation options by gathering codebase evidence to score each approach across consistency, simplicity, testability, and risk, then automatically annotating the winning implementation directly in the issue file.

What is evidence-based scoring for architectural decisions in software development?

Evidence-based scoring for architectural decisions analyzes your codebase to objectively validate competing technical approaches, ensuring the selected implementation path aligns with existing patterns and risk profiles rather than subjective preference.

How do I automate the selection of the best technical approach from multiple issue proposals?

Automate technical approach selection by running the decide-issue skill on a stalled issue, which evaluates multiple proposed options against codebase evidence and updates the issue frontmatter with the winning resolution.

Do I need ll-issues CLI integration to evaluate implementation deadlocks?

Yes, evaluating implementation deadlocks requires integration with the ll-issues CLI and codebase analysis tools to properly score options and annotate the resulting decision within the issue files.

When should I use automated codebase analysis to break a development deadlock?

Use automated codebase analysis to break a development deadlock when an issue contains multiple proposed architectural approaches requiring objective validation to prevent decision paralysis and ensure the best technical fit.

What limitations exist when scoring technical approaches using codebase evidence?

Scoring technical approaches using codebase evidence depends entirely on existing codebase patterns and requires ll-issues CLI integration, meaning it cannot evaluate options for greenfield projects lacking established architectural references.