plan

Organize complex projects into structured plans with YAML frontmatter and Obsidian integration.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan units convert sprawling ideas into structured, repeatable plans that teams can implement and track.

Core Features & Use Cases

  • Structured plan templates including TLDR, success criteria, decisions, and task breakdown
  • Obsidian-friendly output with progress tracking and cross-model execution
  • Reusable templates for multi-stakeholder projects and long-running initiatives

Quick Start

Create a new plan named "portfolio automation" and let Claude generate a complete, ready-to-use plan saved to your Obsidian vault.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I break down a complex project into structured tasks for multi-model execution?

To break down a complex project, you need a structured plan template that generates a TLDR, success criteria, decision logs, and task breakdown. This approach organizes sprawling ideas into repeatable plans that support cross-team coordination and multi-model execution.

Can I generate and save project plans directly to my Obsidian vault?

Yes, you can generate project plans and save them directly to your Obsidian vault. The plan output is Obsidian-friendly, supporting YAML frontmatter with name and description, along with built-in progress tracking for long-running initiatives.

What is the best way to track progress and decisions for long-running initiatives?

The best way to track progress for long-running initiatives is using a structured plan with a dedicated decision log and task breakdown. This creates a repeatable framework that teams can implement and monitor over time.

Does this project planning approach require a specific format for cross-team coordination?

Yes, cross-team coordination requires a YAML frontmatter with name and description fields. This structured format ensures the plan is production-ready and supports multi-stakeholder project tracking.

How do I create a reusable template for multi-stakeholder project management?

You create a reusable template by organizing project components into TLDR, success criteria, decisions, and task breakdown sections. This generates a standardized, production-ready plan that multiple stakeholders can implement and track.

When do I need a structured task breakdown instead of a simple project list?

You need a structured task breakdown when managing complex, sprawling ideas that require multi-model execution or cross-team coordination. Simple lists lack the decision logs and success criteria necessary for long-running, multi-stakeholder initiatives.