Plan Pipeline

CommunityPopular

FlorianBruniaux

plan-pipeline

Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.

Overview

Publisher	FlorianBruniaux
Repository	`claude-code-ultimate-guide`
Skill name	`plan-pipeline`
Stars	6K
Forks	782
Bundled files	Instructions only
License	CC-BY-SA-4.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by FlorianBruniaux on GitHub. Read the source before you install it.

Installation

Install the Plan Pipeline AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/examples/skills/plan-pipeline

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-guide.git /tmp/claude-code-ultimate-guide
mkdir -p .claude/skills
cp -r /tmp/claude-code-ultimate-guide/examples/skills/plan-pipeline .claude/skills/plan-pipeline

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Plan Pipeline in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Plan Pipeline on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Plan Pipeline is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Plan Pipeline Orchestrator

Orchestrates the complete plan-to-execution pipeline. Can run the full pipeline or a single isolated stage.

Stages

Stage	Skill	Purpose
1	`/plan-pipeline:ceo-review`	Challenge the brief, lock product direction
2	`/plan-pipeline:eng-review`	Lock architecture, diagrams, and test matrix
3	`/plan-pipeline:start`	5-phase planning: PRD, research, ADRs, task list
4	`/plan-pipeline:validate`	2-layer validation before any code is written
5	`/plan-pipeline:execute`	Worktree isolation, parallel agents, quality gate, PR

Usage


/plan-pipeline                     # full pipeline, asks for context
/plan-pipeline --from=start        # skip gates, start from planning phase
/plan-pipeline --from=validate     # validate an existing plan
/plan-pipeline --from=execute      # execute a validated plan

When to Use Each Stage

ceo-review: use before any significant feature when the direction is not locked. Especially valuable when the request is specific (specificity signals collapsed solution space).

eng-review: use after direction is locked. Required for features with async components, external dependencies, or multi-step flows.

start: use for any non-trivial feature touching more than 2 files or involving architecture decisions.

validate: always before execute. The cost of validation is negligible against the cost of discovering issues mid-execution.

execute: after validate confirms all issues are resolved.

Workflow

Collect context: what are we building, and what stage do we start from?
ceo-review: product direction gate (can be skipped with --from=eng-review or later)
eng-review: architecture gate (can be skipped with --from=start or later)
CHECKPOINT: ask user to confirm direction and architecture before planning
start: run 5-phase planning, produce docs/plans/plan-{name}.md
CHECKPOINT: present plan for review before validation
validate: 2-layer validation (structural + specialist agents)
execute: worktree isolation -> parallel agents -> quality gate -> PR

Dependency Graph


   ceo-review
        |
   eng-review
        |
      start
        |
    validate
        |
    execute

Notes

Each stage writes its output to disk before the next stage begins. If the pipeline is interrupted, resume with --from=<stage> using the correct stage name. All decisions are recorded in docs/plans/plan-{name}.md and the corresponding ADRs in docs/adr/.

Frequently asked questions

What does the Plan Pipeline AI skill do?

Why use Plan Pipeline on TypingMind?

Because you install it once and use it with any model. Plan Pipeline is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Plan Pipeline in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/FlorianBruniaux/claude-code-ultimate-guide/tree/main/examples/skills/plan-pipeline. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Plan Pipeline?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Plan Pipeline?

As many as you like. As long as a model supports skills, you can use Plan Pipeline with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Plan Pipeline AI skill free?

Yes. It is published on GitHub by FlorianBruniaux under the CC-BY-SA-4.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Docker Patterns

affaan-m

CommunityPopular

Patrones de Docker y Docker Compose para desarrollo local, seguridad de contenedores, networking, estrategias de volúmenes y orquestación de múltiples servicios.

E2e Testing

Patrones de pruebas E2E con Playwright, Page Object Model, configuración, integración CI/CD, gestión de artefactos y estrategias para pruebas inestables.

Eval Harness

Framework formal de evaluación para sesiones de Claude Code que implementa principios de desarrollo orientado a evals (EDD)

Frontend Patterns

Patrones de desarrollo frontend para React, Next.js, gestión de estado, optimización de rendimiento y buenas prácticas de UI.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Plan Pipeline Orchestrator

Stages

Usage

When to Use Each Stage

Workflow

Dependency Graph

Notes

Frequently asked questions

Related AI Skills

Set up your own AI workspace now