issue

Generate issues from natural-language descriptions and update planning documents.

11|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/pillip/claude-dev-kit --skill issue-pillip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue
Source: https://github.com/pillip/claude-dev-kit/tree/main/skills/issue
Command: npx skills add https://github.com/pillip/claude-dev-kit --skill issue-pillip

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Converts natural-language descriptions into actionable issues and automatically updates related planning and design documents, reducing manual handoffs and ensuring alignment across the sprint workflow.

Core Features & Use Cases

  • Create a single issue or a batch of issues from a natural-language description.
  • Auto-update issues.md, STATUS.md, and related planning/design docs to reflect new work.
  • Maintain coherent issue numbering, dependencies, and sprint coherence across multiple documents.

Quick Start

Provide a natural-language description of the work to create one or more issues and trigger updates to project planning docs.

Frequently Asked Questions about issue

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

FAQPage Schema
How do I convert natural language descriptions into tracked issues for sprint planning?

You can convert natural language descriptions into tracked issues by generating single or batch issue blocks from text and mapping them directly into the sprint planning workflow. This automatically updates related planning and design documents.

How do I auto-update issues.md and STATUS.md when adding new issues to a sprint?

To auto-update issues.md and STATUS.md, the system validates formatting against these planning documents when finalizing new issues. It automatically reflects the new work across related project docs to maintain sprint coherence.

Can I generate a batch of issues from a single natural language description?

Yes, you can generate batch issue blocks from a single natural language description. The system maintains coherent issue numbering and dependencies across multiple documents while mapping them into the sprint workflow.

What is the best way to maintain coherent issue numbering across multiple planning documents?

The best way to maintain coherent issue numbering is to validate formatting against issues.md and planning documents before finalizing. This ensures dependencies and sprint coherence are preserved when auto-updating related design docs.

Does this issue generation workflow require manual handoffs to update design docs?

No, this issue generation workflow eliminates manual handoffs by automatically updating related planning and design documents. It ensures alignment across the sprint workflow directly from the natural language input.