twl:co-issue

To convert user requirements into structured GitHub Issues, this Skill orchestrates a multi-phase workflow that decomposes requests, refines each issue, and aggregates creation across projects. It enforces strict phase progression and user confirmation for safety.

Managing cross-repository GitHub Issue creation is handled by a thin orchestration layer that processes requirements across a multi-phase flow. It constructs a DAG for level-based dispatch, ensuring structured issue creation across multiple GitHub projects.

Yes, you need an explore-summary input created beforehand to start the GitHub Issue generation workflow. The workflow processes requirements beginning from Phase 2, relying on this mandatory pre-explored summary to initiate the refinement and creation phases.

The multi-phase workflow enforces safety constraints during issue creation by implementing strict phase progression and gating mechanisms. It requires explicit user confirmation at critical stages, ensuring controlled decomposition, per-issue refinement, and aggregate creation.

Yes, you can use this workflow to dispatch GitHub Issues across different project levels. It utilizes DAG construction and level-based dispatch to organize and create issues hierarchically, managing cross-repository references throughout the orchestrated flow.

You should use an orchestrated workflow instead of manually creating GitHub Issues when dealing with scattered requirements that need structured decomposition and cross-repository management. It provides gating, per-issue refinement, and aggregate creation to handle complex issue generation safely.