← ClaudeAtlas

scaffold-pipelinelisted

Static reference for scaffold pipeline ordering, dependencies, and phase structure. Use ONLY for questions about pipeline design, step ordering, or dependency constraints — NOT for status, progress, or "what's next" queries (those go through scaffold-runner).
zigrivers/scaffold · ★ 3 · Data & Documents · score 69
Install: claude install-skill zigrivers/scaffold
# Scaffold Pipeline Reference This skill is a **static reference** for pipeline ordering and dependency constraints. It does NOT handle status checks, progress queries, or navigation. **Activation boundary:** If the user asks "where am I?", "what's next?", "pipeline status", or anything about their current progress → **do not use this skill**. The `scaffold-runner` skill handles all status/navigation via the `scaffold` CLI. Use this skill ONLY when the user asks about: - Pipeline design: "what phases are there?", "what's the ordering?" - Dependency rules: "what depends on what?", "can I run X before Y?" - Step reference: "what commands are in phase 3?", "is design-system optional?" ## Phases 16 phases, each with a slug (used in frontmatter) and display name. Canonical source: `src/types/frontmatter.ts` `PHASES` constant. | # | Slug | Display Name | Description | |---|------|-------------|-------------| | 0 | `vision` | Product Vision | Transforms your idea into a strategic vision document covering who it's for, what makes it different, and what success looks like. | | 1 | `pre` | Product Definition | Translates your vision into a PRD with features, personas, and success criteria, then breaks it into user stories with testable acceptance criteria. | | 2 | `foundation` | Project Foundation | Researches and documents technology choices, creates coding standards with linter configs, defines testing strategy, and designs directory layout. | | 3 | `environment` | Development