/setup-build-kb

User input: $ARGUMENTS

Parse $ARGUMENTS:

• Empty → full build (all phases)
• Phase number (e.g., 3) → resume from that phase
• "experience" / "bundles" / "skills" / "pubs" / "reframing" / "significance" → run only that component
• "status" → show what's built and what's missing

---

Startup

1. Read CLAUDE.md — check KB Corrections Log
2. Read config.md — load:
   • Personal Info (positions, institutions, dates)
   • Role Types table (defines which bundles to create)
   • Provenance Flags (propagate to all KB files)
   • Document Preferences (bullet variant defaults)
3. Read knowledge_base/extractions/_INVENTORY.md — verify extractions exist
4. Scan resume_builder/ to see what's already built

Pre-flight check:

• If _INVENTORY.md is empty or has no entries: "No extractions found. Run /setup-extract first." Stop.
• If fewer than 2 extractions: warn "Only [N] extraction(s) found. KB quality improves with more papers. Continue anyway?"

Progress: "Found [N] extractions across [M] positions. Config has [K] role types defined."

---