plan-phase

# Plan Phase Plan the next phase of development from the PRD, create GitHub issues, and prepare for implementation. This skill bridges planning and building — it creates the structure but writes no application code. ## Your task Work through the steps below in order. Each step has a hard stop — do not proceed past a CHECKPOINT without explicit user approval. --- > **Tip for the user**: You can activate Claude Code's plan mode (shift+tab) during Steps 1-2 for an extra guardrail against premature code changes. Toggle out of plan mode before Step 3 so that Claude Code can run `gh issue create` commands. ### Step 1: Orient - Read `docs/prd/ROADMAP.md` to identify the current phase and what comes next - Read the PRD overview file (`docs/prd/*-overview.md`) for project context - Read the specific PRD document(s) relevant to the upcoming phase - Read the project's `CLAUDE.md` - Review recent git history and merged PRs to understand current state - Check for any open GitHub issues that may already cover upcoming work ### Step 2: Draft the plan Present a clear, concise plan for the next phase: - **Phase name and PRD reference** (e.g., "Phase 2: Auth & Onboarding — see `02-auth-and-onboarding.md`") - **Scope summary**: What this phase accomplishes in 2-3 sentences - **Proposed issues**: A numbered list of discrete, implementable issues. Each issue should include: - A clear title following the pattern: `feat: ...` or `fix: ...` or `chore: ...` - A one-line description of w...