plan

Create plan files with options and decision logs for feature work.

16|3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/YehudaFrankel/clankbrain --skill plan-yehudafrankel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/YehudaFrankel/clankbrain/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/YehudaFrankel/clankbrain --skill plan-yehudafrankel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps product teams organize work by creating a dedicated plan file, drafting multiple options with trade-offs, and tracking the final decision in memory.

Core Features & Use Cases

  • Open or create the plan file in memory at .claude/memory/plans, derive a slug from the feature name, and seed the plan with Problem, Options, and Decisions sections.
  • Generate 2–4 distinct options with Build cost, User friction, and Payoff ratings, plus notes on trade-offs and a Build cost comparison.
  • Display and update the live decision and propagate decisions to the memory for future sessions.
  • Use case: when planning a new feature, you run plan to capture problem framing, option exploration, and the eventual decision path.

Quick Start

Say "plan [feature]" to create or open a plan for the given feature and begin drafting.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I document feature planning options and track decisions in a markdown file?

You can document feature planning by creating a dedicated plan file in memory that organizes Problem, Options, and Decisions sections, generating 2–4 options with build cost, friction, and payoff ratings.

What is the best way to compare feature build costs and user friction during product planning?

Comparing feature build costs and friction is handled by drafting multiple options with specific ratings for build cost, user friction, and payoff, alongside notes on trade-offs and a build cost comparison to guide the decision path.

Can I use this to maintain a live decision log for ongoing feature development?

Yes, you can maintain a live decision log by creating or reading a dedicated plan file at .claude/memory/plans, displaying and updating the live decision, and propagating decisions to memory for future sessions.

How do I create a persistent plan file for a new feature idea?

To create a persistent plan file, you run the plan command with a feature name, which derives a slug from the name and automatically seeds a new plan file with structured Problem, Options, and Decisions sections.

Does this workflow require any external dependencies or specific components to run?

No external dependencies or components are required, as this workflow operates independently to generate plan files and decision logs directly within the local .claude/memory/plans directory structure.