opsx-plan-to-issues

To convert OpenSpec tasks.md into GitHub issues, run the plan-to-issues command to parse tasks into a structured plan.json and automatically create corresponding GitHub issues with task checkboxes and acceptance criteria for progress tracking.

The plan-to-issues process skips OpenSpec changes that lack a tasks.md file, have already been tracked in an existing plan.json, or fail prerequisite checks like GitHub authentication and required repository labels.

You track OpenSpec change progress in GitHub by generating issues linked to a plan.json file. The Skill updates each change's plan.json with a tracking_issue reference, ensuring traceability between your specs and GitHub.

Yes, you need GitHub authentication to generate issues from OpenSpec. The Skill verifies authentication and ensures required repository labels exist before creating issues and updating your plan.json files.

GitHub issues generated from OpenSpec tasks include a standardized title, a summary of the change, listed delta specs, and a task checklist with acceptance criteria, all linked back to the plan.json via a tracking_issue.