speckit-workflows.phasestoissues

Creating GitHub issues from spec-kit files involves parsing spec.md, tasks.md, and plan.md to generate a parent phase issue and individual child task issues, applying workflow labels and validating the GitHub remote for safe operations.

Linking tasks to parent phase issues works by creating a main phase issue capturing the implementation plan, then generating individual task issues from tasks.md and attaching them as sub-issues to maintain traceability and accountability.

Automating GitHub issue creation from spec-kit requires a repository leveraging the spec-kit workflow with valid spec.md, tasks.md, and plan.md files, and requires validating the GitHub repository remote to ensure safe operations.

The best way to structure GitHub issue bodies from planning files is to extract the phase description, acceptance criteria, and implementation plan from spec.md and plan.md, applying appropriate workflow labels to format the output safely.

Automated issue generation validates the GitHub remote repository to satisfy safety requirements, ensuring that issues are only created in the correct linked repository and preventing accidental writes to unauthorized or incorrect targets.