issue-creation-orchestration

Create one level of child issues from Project, Epic, or Feature parents and trigger asynchronous review.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/langadventurellc/claude-marketplace --skill issue-creation-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-creation-orchestration
Source: https://github.com/langadventurellc/claude-marketplace/tree/main/plugins/task-trellis/skills/issue-creation-orchestration
Command: npx skills add https://github.com/langadventurellc/claude-marketplace --skill issue-creation-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates issue creation with automatic review to ensure created issues accurately reflect the original requirements.

Core Features & Use Cases

  • Creates only the immediate child issues (one level down) from a given parent issue: Project -> Epics, Epic -> Features, Feature -> Tasks.
  • Automatically spawns an issue-creation-review pass to verify that the created issues align with the original requirements.
  • Performs a codebase reconciliation before creation to detect gaps between documented scope and actual state and adjusts the scope accordingly.

Quick Start

Use the issue-creation-orchestration skill to generate and review the immediate child issues for a given parent issue. The workflow will read the parent, research the codebase, create only one level of child issues, and spawn a review task to validate results.

Frequently Asked Questions about issue-creation-orchestration

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

FAQPage Schema
How do I automate hierarchical issue creation for Trellis projects?

Automated issue creation generates exactly one level of child issues from a parent Project, Epic, or Feature. It reads the parent issue, reconciles scope against the actual codebase, and creates immediate child Epics, Features, or Tasks to keep Trellis projects aligned.

How does automated issue review work after creating child issues?

Automated issue review spawns an asynchronous issue-creation-review subagent immediately after child issues are generated. This subagent validates that the newly created Epics, Features, or Tasks accurately reflect the original user requirements preserved during the creation process.

Can I generate an entire project hierarchy of issues at once?

No, hierarchical issue generation enforces a strict stop-after-one-level policy. It only creates immediate child issues from a given parent, meaning Projects yield Epics, Epics yield Features, and Features yield Tasks, preventing the generation of multi-level deep hierarchies in a single pass.

Why does issue creation check the codebase before generating child issues?

Codebase reconciliation detects gaps between documented project scope and actual state before creating child issues. This research step adjusts the generated issue scope according to real code, ensuring that created Epics, Features, or Tasks reflect current development reality.

What is the best way to ensure generated project issues match original requirements?

Issue creation orchestration preserves original user input mandatorily and passes it to an asynchronous review subagent. This automated review validates that generated child issues align with the original requirements, ensuring accurate hierarchical project tracking.

Do I need to manually review issues created by the orchestration workflow?

Manual review is unnecessary as the workflow automatically spawns an issue-creation-review pass. This subagent checks that created child issues align with original requirements, though users can still inspect the preserved original input and generated issues afterward.