One-click install
npx skills add https://github.com/kurone-kito/bmemb --skill issue-authoring-kurone-kito
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-authoring
Source: https://github.com/kurone-kito/bmemb/tree/main/.claude/skills/issue-authoring
Command: npx skills add https://github.com/kurone-kito/bmemb --skill issue-authoring-kurone-kito

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill turns ambiguous or large requests into IDD-ready GitHub issues and roadmaps with clear ownership, dependency edges only when truly needed, and objective acceptance criteria.

Core Features & Use Cases

  • Two-phase drafting: runs bounded clarification, then decomposes and drafts the smallest safe output shape.
  • Reuse-first issue hygiene: extends or reuses existing issues/roadmaps when possible to avoid duplicates and ownership conflicts.
  • Roadmap-ready routing: generates orphan issues, roadmap packages with child issues, or stable non-ready buckets (deferred, needs-decision, blocked-by-human, out-of-scope) based on verifiability and autonomy.
  • Pre-publication boundary enforcement: stops at the approval boundary so drafting does not automatically publish or start execution.

Quick Start

Use the issue-authoring skill to draft an IDD-ready roadmap with child issues for a request that is too large or ambiguous for a single reviewable change.

Frequently Asked Questions about issue-authoring

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

FAQPage Schema
How do I break down ambiguous project requests into actionable GitHub issues?

To break down ambiguous project requests into actionable GitHub issues, this Skill applies phased clarification and task decomposition to draft the smallest safe output shape with clear ownership and objective acceptance criteria.

What is the best way to plan a roadmap with child issues and dependency encoding?

Roadmap planning with child issues and dependency encoding is achieved by routing tasks into readiness buckets and resolving marker-prefixes to generate minimal true dependency edges for orphan or child issues.

How do I avoid duplicate GitHub issues when drafting a new roadmap?

Avoiding duplicate GitHub issues when drafting a new roadmap requires reuse-first logic, which extends or reuses existing issues and roadmaps to prevent ownership conflicts and redundant task entries.

Does this approach automatically publish drafted GitHub issues to my repository?

No, this approach enforces a pre-publication boundary that stops at the user approval boundary without publishing or execution, ensuring drafted GitHub issues require explicit manual review.

How should I handle roadmap tasks that are blocked or need a human decision?

Handling roadmap tasks that are blocked or need a human decision involves routing them into stable non-ready buckets like deferred, needs-decision, or blocked-by-human based on task verifiability and autonomy.