New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Plan Phase

by joshukraine in joshukraine/dotfiles

Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.

MITAuto-check passedProduct & Project Management

Install Plan Phase

skills CLI
$ npx skills add joshukraine/dotfiles --skill plan-phase -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install joshukraine/dotfiles plan-phase --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/joshukraine/dotfiles.git skills-src && mkdir -p .claude/skills && cp -r skills-src/claude/.claude/skills/plan-phase .claude/skills/plan-phase && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
plan-phase
GitHub stars
429
Token cost
~995 tokens
SKILL.md length
515 words
Files
1
Skills in repo
24
Repo updated
First seen
Licence
MIT

At a glance

Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.

  • Works in 4 steps: Orient → Draft the plan → Create GitHub issues → …
  • Tasks that involve PRD writing
  • SKILL.md covers Your task and Important
  • Calls gh

What it does

Plan Phase is an agent skill from joshukraine/dotfiles. Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.

Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering PRD writing. It works with GitHub. The repository describes itself as: :roundpushpin: My dotfiles for macOS using Neovim, Zsh, and Ghostty + Tmux. The licence is MIT.

When your agent uses it

  • Tasks that involve PRD writing

Example prompts

  • “/plan-phase”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Orient
  2. Draft the plan
  3. Create GitHub issues
  4. Report and hand off

What it can do on your machine

Read from SKILL.md and the folder at commit b59ad5b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Plan Phase loads about 995 tokens when it runs. Until then it costs about 28 tokens; SKILL.md has 515 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~995

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from joshukraine/dotfiles at commit b59ad5b, republished under its MIT licence (© joshukraine). 515 words, ~995 tokens.

Download SKILL.mdSave it as .claude/skills/plan-phase/SKILL.md (or your agent's skills folder).
name
plan-phase
description
Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.
disable-model-invocation
true

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.

Show full SKILL.md (212 more words)Show less
Step 3: Create GitHub issues

After plan approval, create each issue on GitHub using the gh CLI:

bash
gh issue create --title "feat: [title]" --body "[description]"

Each issue body should include:

  • Context: Which PRD phase and document this relates to (e.g., "Phase 2, 02-auth-and-onboarding.md")
  • Requirements: Specific acceptance criteria drawn from the PRD
  • Technical notes: Key implementation details, relevant files, patterns to follow
  • Dependencies: Any issues that must be completed first

Create the issues in implementation order. Record each issue number as it is created.

Step 4: Report and hand off

After all issues are created, present a summary:

text
Phase: [name]
Issues created:
  #41 - feat: Add User model with Devise authentication (medium)
  #42 - feat: Add Pundit authorization policies (small)
  #43 - feat: Add admin dashboard with user management (large)

Recommended starting point:
  /resolve-issue 41

CHECKPOINT 2: Present this summary and wait for user approval before any implementation begins. Do not write application code, create branches, or modify any files beyond GitHub issues.

When the user is ready to begin, suggest the /resolve-issue command for the first issue in sequence.

Important

  • This skill creates GitHub issues only. It does not write application code, create branches, modify source files, or run tests.
  • Both checkpoints are hard stops. Do not proceed without explicit approval.
  • If a context window clear is needed, it is safe to do so after Step 4 — the issues exist on GitHub and will survive the clear.
  • Keep issues focused. Each issue should be completable in a single PR. If an issue feels too large, split it.

© joshukraine, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in claude/.claude/skills/plan-phase of joshukraine/dotfiles.

Open the folder on GitHubat commit b59ad5b

Compare with similar skills

Plan Phase next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Plan Phase compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Plan Phase this skilljoshukraine/dotfiles429—~995Automated safety check: PassMIT
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Ouroboros PM InterviewQ00/ouroboros6.2k—~5.7kAutomated safety check: PassMIT
To Issuessmallnest/pigo476—~1.9kAutomated safety check: PassMIT
Write A Prdbestofjs/bestofjs3.1k1 repos~722Automated safety check: PassMIT
Write Update Tidb Docspingcap/docs615—~2.3kAutomated safety check: PassCustom licence

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Ouroboros PM Interview

    Q00/ouroboros

    Runs a guided product-manager interview that classifies each question automatically and produces a Product Requirements Document.

    6.2k GitHub stars~5.7k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed

  • To Issues

    smallnest/pigo

    Decompose a PRD and/or SPEC into implementable Issues and create them in your chosen platform (GitHub, Local, or Baidu iCafe).

    476 GitHub stars~1.9k tokensUpdated 26 days ago
    Product & Project ManagementAuto-check passed

  • Write A Prd

    bestofjs/bestofjs

    Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue.

    3.1k GitHub starsUsed in 1 repo~722 tokens
    Product & Project ManagementAuto-check passed

  • Write Update Tidb Docs

    pingcap/docs

    Write new TiDB documentation or update existing TiDB documentation from code changes, PRs, issues, design docs, product specs, rough drafts, existing docs, or short feature descriptions.

    615 GitHub stars~2.3k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Write Product Spec

    bholmesdev/hubble.md

    Write a PRODUCT.md spec for a significant Hubble user-facing feature, focused only on user experience and observable behavior.

    1.5k GitHub stars~966 tokensUpdated 8 days ago
    Product & Project ManagementAuto-check passed

More from joshukraine/dotfiles

All 24 skills in this repo

  • Todoist CLI

    joshukraine/dotfiles

    Manage Todoist tasks, projects, labels, filters, sections, comments, reminders, and workspaces via the td CLI.

    429 GitHub starsUsed in 1 repo~6.9k tokens
    Auto-check passed

  • Autopilot Triage

    joshukraine/dotfiles

    Vet open issues for autonomous resolution and queue the qualifying ones with the autopilot-queued label — the start-of-day "fill the queue" half of the triage → run split.

    429 GitHub stars~2.1k tokensUpdated 3 days ago
    Auto-check passed

  • Checkpoint

    joshukraine/dotfiles

    Quick 2-minute status update on current phase, completed work, blockers, and health check.

    429 GitHub stars~600 tokensUpdated 3 days ago
    Auto-check passed

  • Create PR

    joshukraine/dotfiles

    Create a pull request with auto-generated description, issue linking, ROADMAP updates, and PR-metadata validation.

    429 GitHub stars~1.3k tokensUpdated 3 days ago
    Auto-check passed

  • Debrief

    joshukraine/dotfiles

    Detailed technical walkthrough covering architecture, test coverage, product tour, and key design decisions.

    429 GitHub stars~2.5k tokensUpdated 3 days ago
    Auto-check passed

  • Drift Check

    joshukraine/dotfiles

    Pre-PR advisory check for deviations from the project spec. An agent skill from joshukraine/dotfiles.

    429 GitHub stars~1.2k tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about Plan Phase

What does Plan Phase do?

Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building. Plan Phase is an agent skill from joshukraine/dotfiles. Plan the next PRD phase by drafting issues, creating GitHub issues, and bridging planning to building.

When should I use Plan Phase?

Plan Phase fits situations like: tasks that involve PRD writing.

How do I install Plan Phase in Claude Code?

Run `npx skills add joshukraine/dotfiles --skill plan-phase -a claude-code`. Or copy the skill folder (claude/.claude/skills/plan-phase in joshukraine/dotfiles) into .claude/skills/plan-phase in your project. Claude Code loads it when a task matches its description.

How do I install Plan Phase in Codex?

Run `npx skills add joshukraine/dotfiles --skill plan-phase -a codex`. Or copy the skill folder (claude/.claude/skills/plan-phase in joshukraine/dotfiles) into .agents/skills/plan-phase in your project. Codex loads it when a task matches its description.

Can I use Plan Phase in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add joshukraine/dotfiles --skill plan-phase -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-phase, .gemini/skills/plan-phase, .github/skills/plan-phase and .opencode/skills/plan-phase in your project.

What does Plan Phase need to run?

Going by SKILL.md and its folder, Plan Phase needs the command-line tools its instructions call (gh).

Does Plan Phase access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Plan Phase safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Plan Phase use?

Plan Phase is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Plan Phase use?

About 995 tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Plan Phase?

Skills that share tags, products or a category with Plan Phase: CCPM Project Management (automazeio/ccpm, 8.4k stars), Ouroboros PM Interview (Q00/ouroboros, 6.2k stars), To Issues (smallnest/pigo, 476 stars) and Write A Prd (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Plan Phase?

joshukraine (a GitHub user) maintains it in joshukraine/dotfiles, which has 429 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on October 6, 2026.

Source: joshukraine/dotfiles on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.