A planning workflow for the next phase of a product requirements document, a set of written development goals. It reviews the project plan and context, drafts work items, and can create GitHub issues after approval.

Use it to choose the next roadmap phase, turn its requirements into development issues, check for duplicates, and prepare the team to build.

It connects product planning to implementation while keeping planning separate from application coding and requiring checkpoints before external changes.

plan-phase — Skill for Claude Code and Codex by joshukraine: A planning workflow for the next phase of a…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/joshukraine/dotfiles/plan-phase

Any agent

npx skills add joshukraine/dotfiles --skill plan-phase

Clone the repo

git clone --depth 1 https://github.com/joshukraine/dotfiles

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/joshukraine/dotfiles/plan-phase.svg)](https://agentmods.dev/skills/joshukraine/dotfiles/plan-phase)

Your own site

<a href="https://agentmods.dev/skills/joshukraine/dotfiles/plan-phase"><img src="https://agentmods.dev/badge/skills/joshukraine/dotfiles/plan-phase.svg" alt="Measured on agentmods" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 927 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00024	$0.00927
Opus 5	$0.00012	$0.00464
Sonnet 5	$0.00005	$0.00185
Haiku 4.5	$0.00002	$0.00093

Measured 4d ago against content hash 14813cc8111e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan-phase scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

claude/.claude/skills/plan-phase/SKILL.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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 what the issue covers
- Estimated complexity (small / medium / large)
Implementation order: Which issues depend on others and the recommended sequence
Out of scope: Anything explicitly deferred to a later phase

Keep the number of issues manageable — typically 3-7 per phase. If the phase is larger, break it into sub-phases.

CHECKPOINT 1: Present the plan and wait for user approval. The user may adjust scope, reorder issues, split or combine items, or request changes. Do not proceed until the user explicitly approves.

Read the full file on GitHub · 91 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

4d ago First seen · 91 lines · 24 tokens per session scan A 14813cc8111e

Subscribe to this mod's changes

plan-phase is a skill published in the GitHub repository joshukraine/dotfiles (422 stars, last pushed 22d ago), licensed MIT. It adds 24 tokens to every session and 927 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Project management dotfiles macos rails vim zsh

factory-mcp

Use the Warp Factory MCP to hand work to a software factory and collaborate with it — bundle local work and send it to the cloud, find factory tasks from a Slack thread / Linear ticket / description, and pull a task down to test or iterate locally and hand it back.

warpdotdev/warp · 58 tokens

github-issue-create

Create a GitHub issue with an auto-generated description. Use when the user asks to open an issue for a bug, feature request, or task.

aiya000/dotfiles · 35 tokens

there-there

Manage There There helpdesk tickets, contacts, and channels using the there-there CLI. Use when the user wants to list, view, reply to, search, or manage tickets; assign team members; manage tags; view contacts; or interact with there-there.app from the command line.

freekmurze/dotfiles · 63 tokens

review-pr

Review an existing GitHub PR — one verified single-pass read of the diff, inline P1–P3 findings, fixes for the P1/P2s pushed to the PR branch, scoped verification, resolved threads, a summary. Escalates to a two-reader second opinion only for large source changes. Use when asked to review and fix a PR, or to run the…

DJRHails/dotfiles · 87 tokens

cmux-fork-session

Fork the current agent session — Claude Code or pi — into a new cmux split pane (or tab): opens a split beside the caller, relaunches this session forked (claude --fork-session / pi --fork), titles it 'fork: ', and keeps that title. Use when the user asks to fork/duplicate/branch the current session into a new split…

DJRHails/dotfiles · 137 tokens

cmux-rebuild

Manage the user's durable dev sessions — zellij sessions on remote hosts (bonbon, taffy) reached over mosh, plus the local host's (trifle) own detached zellij sessions, surfaced as cmux tabs via ssh::durable / zellij::resume. Load when the user wants to rebuild/resurrect lost cmux durable surfaces after a cmux restart…

DJRHails/dotfiles · 232 tokens