plan

Generates standardized PLAN files (.claude/{YYYYMMDD}/PLAN-*.md for multiple frameworks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tak-bro/claude-code --skill plan-tak-bro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/tak-bro/claude-code/tree/main/skills/plan
Command: npx skills add https://github.com/tak-bro/claude-code --skill plan-tak-bro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning across software projects is error-prone without a formal, repeatable strategy. This Skill delivers a base planning workflow that coordinates issue analysis, parallel research, and plan creation for all framework-specific plan skills.

Core Features & Use Cases

  • Guided exploration and issue analysis to identify scope
  • Parallel research to gather patterns and best practices
  • Creation of a standardized PLAN artifact stored at .claude/{YYYYMMDD}/PLAN-*.md
  • Clear handoff boundaries to prevent premature implementation

Quick Start

Enter Plan Mode, generate a new PLAN file in .claude/YYYYMMDD, and review it before implementation.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create a repeatable implementation plan for multiple frameworks?

Repeatable implementation plans are generated by analyzing issue scope and conducting parallel research to produce a standardized PLAN file with boundaries, checklists, and verification commands for frameworks like Angular, React, and Node.js.

What is the best way to structure an end-to-end implementation strategy?

An end-to-end implementation strategy is structured by defining clear handoff boundaries, an implementation checklist, and verification commands, ensuring safe and auditable development before any coding begins.

Does this planning workflow support TypeScript and Kotlin projects?

Yes, this planning workflow supports TypeScript and Kotlin projects, applying a base planning strategy that coordinates issue analysis and plan creation across multiple frameworks.

How do I store and review framework-wide plans before implementation?

Framework-wide plans are stored as concrete PLAN artifacts at .claude/{YYYYMMDD}/PLAN-*.md. You enter Plan Mode to generate the file and review the detailed output structure before starting implementation.

Why do I need a formal planning workflow for software development?

A formal planning workflow prevents error-prone development by guiding issue analysis, parallel research, and plan creation to produce a concrete, auditable PLAN artifact with clear handoff boundaries.

What should a comprehensive software implementation plan include?

A comprehensive software implementation plan should include detailed output structures, boundaries, an implementation checklist, verification commands, and review focus to guide safe and auditable development.