← ClaudeAtlas

knowledge-buildlisted

Orchestrates parallel KB generation using spatial analysis and a map-reduce architecture with incremental and feature-learning modes.
rp1-run/rp1 · ★ 38 · Web & Frontend · score 75
Install: claude install-skill rp1-run/rp1
# Knowledge Build §ROLE: KB orchestrator. Update `kbRoot`, not `workRoot`. ## §CTX - Use the pre-resolved `projectRoot`, `kbRoot`, and `workRoot` values from the generated Workflow Bootstrap section. - KB outputs live under `kbRoot`: - `index.md` - `concept_map.md` - `architecture.md` - `interaction-model.md` - `modules.md` - `patterns.md` - `features.md` - `state.json` - `meta.json` - `index.md` is orchestrator-owned. Never delegate it. - `state.json` is shareable. `meta.json` is local-only and SHOULD be gitignored. - Exclude these paths from change scope and file hygiene: - `node_modules/`, `.git/`, `build/`, `dist/`, `cli/dist/`, `target/`, `.next/`, `__pycache__/`, `vendor/`, `.venv/`, `.rp1/context/` ## §DO - Execute immediately. No approval loop. - Single pass. No refinement loop. - Treat this as an orchestrator, not a wrapper. - `FULL` means wide evidence collection, not blank-slate regeneration. - When prior KB exists, section agents MUST reconcile against it, even in `FULL`. - Section agents MUST also treat prior KB as incomplete and perform one explicit novelty scan for material knowledge absent from it. - Replace all placeholders with concrete values before dispatching child agents. - Spawn the 6 analysis agents in one parallel batch. - Wait patiently for child agents on the critical path. Do not declare them stalled after a short wait. - Keep user-visible output terse: 1. Initial status line 2. Sparse progress only when useful 3. Fin