← ClaudeAtlas

pipeline-scaffoldlisted

Creates a new ICM pipeline from a domain description. Generates numbered stage folders with CONTEXT.md contracts (Inputs/Process/Outputs), reference and output directories, and a root CONTEXT.md. Use when: setting up a new staged workflow, creating a production pipeline, scaffolding an ICM workspace.
mcmespinaa/folder-structure-protocol · ★ 3 · Data & Documents · score 66
Install: claude install-skill mcmespinaa/folder-structure-protocol
# Pipeline Scaffold Skill Creates a new ICM (Interpretable Context Methodology) pipeline — a sequential, human-reviewed AI workflow built from numbered stage folders and file-based handoffs. ## Trigger Use this skill when: - The user asks to create, scaffold, or set up a new pipeline or staged workflow - The user says "new pipeline", "scaffold stages", "create workflow", "set up ICM", "build a pipeline for X" - The user wants to convert an existing process into a staged folder structure ## Procedure ### Step 1: Gather Domain Description Ask the user for: - **Domain/purpose** — What does this pipeline produce? (e.g., "podcast production", "course deck", "content research") - **Stages** — What are the major steps? Accept natural language: "research, then script, then production" is enough. If the user gives a vague request like "set up a pipeline for video production", infer reasonable stages and confirm before proceeding. Default to 3-5 stages — fewer is better. Do NOT proceed without at least a domain name and stage list. ### Step 2: Determine Pipeline Root Confirm the target directory. Options: - Current project root (default) - A subdirectory (e.g., `workspaces/podcast-pipeline/`) - A new directory (create it) If the target already contains numbered stage folders, warn the user and ask whether to overwrite or create alongside. ### Step 3: Generate Stage Folder Structure For each stage, create: ``` {NN}_{stage-name}/ CONTEXT.md # Stage contract (Step 4