/plan

> Create a structured execution plan with objectives, non-negotiables, and time blocks.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Create a structured execution plan with objectives, non-negotiables, and time blocks.

Teams using /plan should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/plan/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/strategy/plan/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/plan/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /plan Compares

Feature / Agent	/plan	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Create a structured execution plan with objectives, non-negotiables, and time blocks.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /plan

> Create a structured execution plan with objectives, non-negotiables, and time blocks.

## Usage
```
/plan "<objective>" [--horizon <days|week|month>] [--for <person>]
```

## What It Does
Produces a structured plan using the plan genre skeleton: objective, non-negotiables (top 3), time blocks, dependencies, and success criteria. Assembles relevant context before planning. Outputs to the appropriate file (rhythm/week-plan.md for weekly, custom for project-specific).

## Implementation
1. **Assemble context** -- `/assemble` relevant topic context.
2. **Define objective** -- single clear sentence of what the plan achieves.
3. **Identify non-negotiables** -- top 3 things that must happen, no exceptions.
4. **Allocate time blocks** -- map tasks to available time slots.
5. **Map dependencies** -- who/what we're waiting on.
6. **Set success criteria** -- how we measure completion.
7. **Write plan** -- output in plan genre skeleton format.

## Examples
```bash
# Plan the week
/plan "Ship AI Masters pricing page" --horizon week

# Plan a project sprint
/plan "Platform MVP launch" --horizon month

# Plan for a specific person
/plan "Bennett's content calendar" --for "Bennett" --horizon week
```

Related Skills

Close Plan

170

from Miosa-osa/canopy

## Command

ads plan

170

from Miosa-osa/canopy

Strategic paid advertising planning with industry-specific templates. Covers platform selection, campaign architecture, budget planning, creative strategy, and phased implementation roadmap. Triggers on: "ad plan", "ad strategy", "campaign planning", "media plan", "PPC strategy", "advertising plan", "media strategy"