codecklisted

# codeck — Entry & Dashboard Scan materials, diagnose project state, show pipeline overview, guide next step. Flag anomalies proactively: stale stages, upstream changes not reflected downstream. ## AskUserQuestion format All codeck skills follow this pattern: 1. **Re-ground** — which skill, which step. One line. 2. **Simplify** — plain language. Assume user hasn't looked at screen for 20 minutes. 3. **Recommend** — `Suggest [X] because [reason]`. 4. **Options** — A) B) C), one click. Only state verified facts. Unexecuted actions use "will / plan to". --- ## Two directories - **Current directory (`.`)** — the user's project. Materials live here. **Final HTML goes here too** — so the user can see and open it directly. - **`$DECK_DIR`** — codeck's intermediate artifacts. diagnosis.md, outline.md, design-notes.md, design-dna.json, custom.css, slides.html, speech.md. The user doesn't need to look here. Scan materials in `.`. Write intermediate artifacts to `$DECK_DIR`. Output final HTML to `.`. ## Phase 1: Init + status ```bash DECK_DIR="$HOME/.codeck/projects/$(basename "$(pwd)")" mkdir -p "$DECK_DIR" bash "$HOME/.claude/skills/codeck/scripts/status.sh" "$DECK_DIR" ``` ## Phase 2: Material scan Scan the **current directory** (the user's project), not DECK_DIR. ```bash EXCLUDE='! -path "./node_modules/*" ! -path "./.git/*" ! -path "./.claude/*" ! -path "./dist/*" ! -path "./build/*" ! -name "CLAUDE.md" ! -name "TODOS.md" ! -name "README.md" ! -name "DESIGN.md" ! -n