issue-resolver_skill

This skill analyzes GitHub issues, triages type and priority, and proposes concrete resolution plans using specification driven development.

HTML

22

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill nahisaho/musubi --skill issue-resolver

SKILL.md6.6 KB

Overview

This skill is an Issue Resolver that analyzes GitHub issues, triages them, extracts requirements, and produces actionable resolution plans with Specification Driven Development (SDD) integration. It classifies issue type, estimates impact, and generates semantic branch names and SDD artifacts to turn issues into traceable requirements and tasks. The output is a concise resolution report and optional PR/branch automation.

How this skill works

The resolver parses issue title, body, labels, and checkboxes to determine type (bug, feature, documentation, refactor, unknown) and extract requirements. It runs impact analysis to estimate scope, effort, risk, affected areas, and dependencies. It then generates a semantic branch name and an SDD-aligned plan (EARS requirements, design, tasks, and testing steps) and can produce a markdown preview or create a PR when configured.

When to use it

You need to triage and prioritize new or backlog GitHub issues.
You want automatic extraction of requirements from issue text or checkboxes.
You need a semantic branch name and a reproducible resolution plan.
You want to convert issues into SDD artifacts (EARS requirements, design, tasks).
You want an estimate of scope, effort, and risk before scheduling work.

Best practices

Include clear reproduction steps and checkboxes or numbered requirements in the issue body.
Tag issues with relevant labels (bug, feature, platform) to improve automatic classification.
Keep steering/architecture and tech context files updated so impact analysis aligns with project constraints.
Review the generated SDD requirement statements for correctness before auto-creating branches or PRs.
Use autoCreateBranch and create-pr options only after validating the resolution plan and tests.

Example use cases

Turn a user-reported bug with reproduction steps into an SDD requirement set, branch, and PR template.
Triage a backlog of feature requests and produce prioritized scope/effort estimates and task breakdowns.
Automate requirement extraction from checklist-style issues to feed a requirements management workflow.
Generate an impact analysis report for stakeholder review before allocating engineering effort.
Quickly create a preview markdown report for code review and SDD traceability.

FAQ

Yes — it can generate semantic branch names and create PRs when configured, but enable auto-create options only after reviewing the proposed plan.

How does it extract requirements from an issue?

It parses checkbox items, numbered lists, and lines with keywords like 'should', 'must', or 'needs to' and converts them into concise requirement statements (EARS format if requested).