grounding-wiki

Lead-engineer-plus-team architecture review of any codebase via parallel subagents: one consolidated, evidence-backed report, proven by a read-only output gate (sections + resolving citations + target untouched).

Bootstrap a new or existing project for the praxis development lifecycle — plant the always-on PDLC grounding (CLAUDE.md), wire the .handoff/ transport, opt into the peer utilities (Backlog.md, Spec Kit) — orchestrate multi-task board sweeps through that lifecycle: pdlc:sweep authors a dependency-laned, operator-signed-off runbook, then runs every task through spec, PR, merge, and re-ground; pdlc:design-rounds covers the inverse case, where the deliverable is not knowable until an operator has chosen among options, running comparable design rounds to a decision record and a spec written against it — and close the loop with pdlc:refactor-triage, which triages the swept result for debt and drift and cards accepted findings back onto the board as sweepable tasks.

Corpus-grounded reorientation loop: N parallel evaluator subagents judge research branches under a stated lens against the project's wiki and board, the operator steers between rounds, evaluators cross-ground each other, and one synthesis lands as concrete board moves — proven by an output gate (per-branch analyses + merged synthesis sections).

Gather cited facts into an isolated, interlinked Markdown thinking-vault branch (embed -> query -> render). Drop-anywhere.

Implement a SPEC and return findings for a lesson to fold back in. Split out of educate.

Turn a folder into a Socratic learning project: teach, author a build SPEC, and gate each lesson done on auditable artifacts.

Turn any codebase into a beautiful, interactive single-page HTML course that teaches how the code works to non-technical people.

Marketplace

Backlog.md as the kanban view over GitHub Spec Kit specs: link a task to a spec dir, sync status one-way from spec artifacts, and gate 'status can't exceed proven artifacts'.