corgispec-gh-propose

Generating a GitHub issue tracking plan requires producing proposal, design, and tasks artifacts from a change request. This process creates a parent issue with child issues per task group, establishing end-to-end tracking for your engineering work.

Schema-driven artifact generation builds proposal.md, design.md, and tasks.md in dependency order within a single guided flow. This ensures your spec, design, and tasks package remains consistent and reviewable before implementation begins.

Breaking down a coding change request into tracked GitHub issues involves applying task breakdown logic to generate a parent issue plus child issues per task group. This uses .github.yaml as the canonical local tracking state for conditional issue creation.

Generating engineering planning artifacts inside an isolated git worktree is supported as an optional feature. This worktree isolation prevents the generated proposal, design, and tasks files from polluting your main workspace.

Creating dependency-ordered proposal and design documents is best handled through schema-guided artifact generation. This produces an approval-ready planning package that satisfies dependency-ordered apply requirements for structured engineering review.

Existing GitHub tracking is not required before generating proposal and tasks artifacts. The process conditionally creates a parent issue and child issues per task group via .github.yaml unless tracking is already configured, ensuring flexible integration.