start-phase

Run /start-phase with a phase number to parse the task table in docs/PROJECT_PLAN.md and create one GitHub Issue per task via gh issue create. Each issue gets phase:N and points:X labels, and issue links are written back into the plan file.

Use gh issue create with --title, --body, and --label flags for each task. This skill automates that loop, applying phase:N and points:X labels and generating a structured body with task ID, points, and acceptance criteria.

You need an authenticated gh CLI (gh auth status), a GitHub repository context, and a clean git working tree. The skill also checks for required labels like phase:N, points:X, and blocked, creating any that are missing.

The skill surfaces the failure, lists which issues were already created, and asks whether to retry or abort. This prevents duplicate issues and lets you recover manually before the plan file is updated.

Yes, it replaces each task's status cell with a link to the created issue, then commits and pushes the change. After this one-time write, the file is treated as read-only until the /retro skill runs at phase end.