# Plan

Use when a request needs shaping before any code is written, a rough or vague prompt...

- Repository: https://github.com/jeremylongshore/tons-of-skills-marketplace (2890 stars)
- Category: Design
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plan -g -a claude-code -y`
Codex: `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plan -g -a codex -y`
Cursor: `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plan -g -a cursor -y`
Gemini CLI: `npx skills add jeremylongshore/tons-of-skills-marketplace --skill plan -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add jeremylongshore/tons-of-skills-marketplace`

## Description

Use when a request needs shaping before any code is written, a rough or vague prompt to sharpen, an ambiguous idea to design, or a clear-enough task to decompose. One chain-starter that amplifies the prompt, designs the approach, and decomposes it into a batched task file, skipping whichever phases the request doesn't need, then STOPS at a build-location gate (build here, hand off to another session, or just keep the plan). Plan never implements. Trigger with /hyperflow:plan, "design this", "plan this", "decompose this", "how should we", "what's the best way to", "break this down", "enhance this prompt".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Plan

One chain-starter that folds three phases, **amplify** (sharpen the prompt), **design** (brainstorm and spec the approach), **decompose** (write the batched task file), into a single flow, then **stops at a build-location gate** (Step 12). Each phase skips itself when the request doesn't need it: a clear task bounces straight to decomposition; an already-structured prompt skips amplify.

**Plan never implements.** It is **thinking, not building**, no source code is written here, and it does not silently chain into `/hyperflow:dispatch`. The only writes are to `.hyperflow/specs/`, `.hyperflow/tasks/`, `.hyperflow/features/`, `.hyperflow/memory/`, and (another-session mode) the committed `.hyperflow-handoff/` package. When the task file is ready, plan **always** asks where to build it (this session / another session / stop), that gate fires on every run, and the user's choice is the only thing that ever starts a build. It drives **Layer 0.5 (Triage)**, **Layer 4 (Brainstorming/Spec)**, **Layer 0 (Project Analysis)**, **Layer 6 (Memory)**, and **Layer 7 (Task Templates)**.

**Plan runs at maximum thinking depth.** Engage extended / ultra reasoning across triage, analysis, design, and decomposition, plan is the chain's one think-heavy front door and pays the reasoning cost once so the build runs faithfully. Every substantive step **uses tools** (Agents to do the work, `Write` to persist artefacts); a plan that exists only in chat is a violation.

**Every agent runs on the current session model, there is no model-tier routing and no model configuration.** Roles (Classifier, Searcher, Writer, Analyst, Planner, Reviewer) differ by responsibility, not by model.

## Iron Rules

The rest: https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/HEAD/plugins/ai-agency/hyperflow/skills/plan/SKILL.md