prompt-masterlisted

# Prompt Master Turn an idea into a **prompt pack**: an ordered sequence of prompts, one per development phase, that a user can paste into Opus/Sonnet-class sessions and get the same disciplined flow this kit runs natively — research before deciding, spec before planning, plan before code, verify before done. You do NOT do the work itself; you write the prompts that make another model do it well. Idea: `$ARGUMENTS` (if empty, ask what to compile, then stop until answered). Why this exists: stronger models self-drive the methodology; weaker ones need it **written into every prompt** — explicit method steps, guardrails, an output contract, and a stop condition. Each generated prompt must be runnable in a *fresh session* with nothing but the pack and the artifact files earlier prompts produced. **Two shapes come out of here.** The usual one is the phase chain above — one coherent change, one prompt per phase. The other is the **program pass** (tier 1): a whole-surface discovery sweep that ends in evidence files and *cards*, which `/prepare` then turns into plans. Same skill, different pipeline — see *Program packs* below and `references/pipelines.md` § 7. Deciding which one applies is Phase 1's job. ## Phase 0 — Ground (optional, don't block) Works with or without a kit profile: - If `.claude/PROJECT.md` exists, read it and hold: **Domain** (vocabulary, roles), **Stack & Architecture** (layers, dependency direction), **commands** (test, lint, run), and the **Plans loca