plan

Generate structured phase-based plans from project issues into PLAN.md.

69|7|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/TaylorHuston/local-life-manager --skill plan-taylorhuston
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/TaylorHuston/local-life-manager/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/TaylorHuston/local-life-manager --skill plan-taylorhuston

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates structured, phase-based plans (PLAN.md) from issues or spikes, enabling teams to break work into actionable phases with checkpoints.

Core Features & Use Cases

  • Phase-based planning: Generate PLAN.md with task, spike, and bug phase structures.
  • Context-aware guidance: Cross-reference issue details, specs, and ADRs to inform planning.
  • Use Case: After creating an issue with /issue, run /plan to produce a ready-to-follow plan that can be committed to the project repository.

Quick Start

  • /plan 001
  • /plan 001 --project coordinatr
  • /plan SPIKE-003
  • /plan 003 --second-opinion

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a phased project plan from software issues?

Generate a structured, phase-based project plan by running the /plan command with an issue identifier. It reads issue details and specs to produce a PLAN.md file with defined, executable phases and checkpoints.

What is the best way to break down a software spike into actionable phases?

The best way to break down a software spike is to use phase-based planning that cross-references issue details, specs, and ADRs. This generates a PLAN.md file with structured checkpoints to guide consistent execution and collaboration.

Can I generate a plan for an issue in a different project repository?

Yes, you can generate a plan for an issue in a different project repository by using the --project flag. This applies cross-project referencing to ensure the plan pulls context from the correct project specs and architectural decisions.

How do I get a second opinion on a generated project management plan?

To get a second opinion on a generated project management plan, append the --second-opinion flag to your command. This provides an alternative perspective on the proposed phases before you commit the PLAN.md file to your repository.

Does phase-based planning work with both bug fixes and new feature tasks?

Yes, phase-based planning works with both bug fixes and new feature tasks. It applies across tasks, spikes, and bugs within software-project workflows, enabling consistent planning structures and actionable phases for any issue type.