plan-review-intake

Identify plan review inputs from local .planning files using git and gh.

1|Updated May 7, 2026

Search Tags:#git #workflow #context #plan-review #intake #planning-files

Ready to run

npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-review-intake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review-intake
Source: https://github.com/ChristopherAlphonse/calphonse-skills/tree/main/plan-review-intake
Command: npx skills add https://github.com/ChristopherAlphonse/calphonse-skills --skill plan-review-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds and surfaces the necessary inputs for plan review using only local project files under .planning.

Core Features & Use Cases

Detect and aggregate current plans, requirements, specs, tasks, and reviews from the .planning directory.
Determine repo root, current branch, and base branch with git and GitHub tooling, then return a concise context bundle for planning discussions.
Support deterministic selection by choosing the newest plausible plan when multiple plans match.

Quick Start

Run the plan-review-intake skill against your local repository to surface the active plan and its context from .planning.

Frequently Asked Questions about plan-review-intake

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

FAQPage Schema

How do I gather context for a plan review from local .planning files?▼

Gather plan review context by detecting and aggregating plans, requirements, specs, tasks, and reviews from the .planning directory in your repository. The skill surfaces the selected plan path, branch details, and relevant TODO sources into a concise context bundle.

How do I find the current and base branches for my git planning workflow?▼

Find current and base branches by using git and gh commands when available. The skill detects the repository root with git rev-parse, then determines the current and base branches to return alongside the active plan context.

What is the best way to surface active plans and specs from a local repository?▼

The best way to surface active plans and specs is to run an intake process against the .planning directory. It selects the newest plausible plan when multiple plans match and returns relevant context files for planning discussions.

How do I handle multiple matching plans in a .planning directory?▼

Handle multiple matching plans through deterministic selection. The intake process automatically selects the newest plausible plan when multiple plans match your criteria, ensuring a single active plan path is returned.

Do I need a .planning directory to review local project plans?▼

Yes, you need a .planning directory with appropriate subfolders for plans, requirements, tasks, specs, and reviews. The skill applies to projects with this structure and surfaces context files from those subfolders.

Can I use git and gh to determine repo root and branches for plan context?▼

Yes, the skill detects the repo root with git rev-parse and determines current and base branches via git and gh when available. It returns these details with the selected plan path and relevant context files.