phase-issue

Generates structured Phase-N tracking issues on GitHub via gh issue create.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/ozzy-labs/skills --skill phase-issue-ozzy-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: phase-issue
Source: https://github.com/ozzy-labs/skills/tree/main/.claude/skills/phase-issue
Command: npx skills add https://github.com/ozzy-labs/skills --skill phase-issue-ozzy-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Creating consistent, well-structured phase tracking issues by hand is error-prone and slow. This Skill assembles a complete Phase-N issue body—cross-session handoff context, decisions table, per-PR tasks, DoD, and Phase N+1 outlook—and files it with the GitHub CLI. ## Core Features & Use Cases - Structured issue assembly: Builds a fixed-section issue body covering project overview, references, constraints, decisions, tasks, DoD, and outlook. - Two operation modes: Non-interactive mode accepts all items as CLI arguments; interactive mode (Claude Code companion) prompts for missing items via AskUserQuestion. - Safe confirmation flow: Previews the assembled body and requires explicit approval before running gh issue create, with a --draft mode that outputs to stdout instead. - Use Case: After finishing Phase 3 of a project, run the skill with the phase number and title to file a tracking issue, then hand off directly to the /drive workflow for implementation. ## Quick Start Ask the assistant to create a Phase 4 tracking issue titled "API migration" with the decisions and tasks files attached, then confirm the preview to file it with gh.

Frequently Asked Questions about phase-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a GitHub tracking issue from the command line?▼

Use gh issue create with a body file assembled by this skill. Pass the phase number and title as arguments, optionally adding --description, --tasks-file, --decisions-file, and --dod to populate each section non-interactively.

How do I generate a phase issue without interactive prompts?▼

Pass all required items as arguments: phase number, title, and optional flags like --description, --refs, --donts, --tasks-file, --dod, and --outlook. When all items are supplied, no AskUserQuestion prompts are triggered for those fields.

Can I preview the issue body before filing it on GitHub?▼

Yes. The skill always shows a body preview and asks for confirmation before running gh issue create. Use the --draft flag to output the assembled body to stdout instead of filing the issue.

Does this skill work outside Claude Code?▼

The core workflow is defined in the canonical SKILL.md and works in non-interactive mode with arguments. The interactive prompting flow using AskUserQuestion is specific to the Claude Code companion variant.

What happens if I leave decisions or tasks unspecified?▼

Unspecified optional sections are left as TBD placeholders in the issue body. In interactive mode you are asked individually whether to fill each item or leave it as TBD before the body is assembled.