post-scope-issue-body

Create GitHub Issues with parent-child and blocked-by dependencies from YAML input.

4|1|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/getty104/claude-task-worker --skill post-scope-issue-body
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-scope-issue-body
Source: https://github.com/getty104/claude-task-worker/tree/main/plugin/skills/post-scope-issue-body
Command: npx skills add https://github.com/getty104/claude-task-worker --skill post-scope-issue-body

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github-api, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub Issues with precise formatting and dependencies, saving time and reducing errors in issue management.

Core Features & Use Cases

  • Automated Issue Creation: Creates GitHub Issues with standardized formatting, including sections for summary, requirements, and references.
  • Dependency Management: Handles parent-child relationships and blocked-by relationships between issues.
  • Use Case: When a user requests a new feature or bug fix, this Skill can automatically create a scope issue with all necessary information and dependencies.

Quick Start

To create a new scope issue, use the post-scope-issue-body skill with the following input YAML:

mode: create
title: "New Feature Request"
sections:
  概要: "Implement a new feature for the user interface."
  要件: "- UI elements should be responsive."
  参照情報: "- Documentation: ./ui-design.md — User interface design details."
  優先度: "High"
  見積もり規模: "M"

Frequently Asked Questions about post-scope-issue-body

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

FAQPage Schema
How do I automate GitHub issue creation with dependencies and parent-child relationships?

Automating GitHub issue creation involves using a script that takes YAML input to define issue details and automatically establishes parent-child and blocked-by relationships via the GitHub API.

What is the best way to format GitHub issues with structured sections like requirements and references?

The best way to format GitHub issues with structured sections is to supply YAML input containing specific keys for summary, requirements, and references, which the automation then translates into standardized issue formatting.

Can I use YAML to create GitHub issues with blocked-by relationships?

Yes, you can use YAML to create GitHub issues with blocked-by relationships by defining the issue details and dependencies in the YAML structure, which the script processes through the GitHub API.

Do I need GitHub API access to automate issue creation and dependency management?

Yes, you need GitHub API access to automate issue creation and dependency management, as the script relies on the API to programmatically create issues and establish parent-child links.

How do I define a scope issue for a new feature request using YAML?

To define a scope issue for a new feature request, you create a YAML input specifying the mode, title, and mapped sections such as summary, requirements, and references to generate the formatted issue.