Rebuild or update the OKF knowledge bundle under docs/kb — the concept-doc map of Synto's internals (each fact a path:line link) used for navigation. Reach for this whenever the kb has drifted from the code, or someone asks to "refresh the kb", "update the knowledge base", or "get the kb in sync" — e.g. after a feature lands, a subsystem is refactored, files move, a new concept needs seeding, or path:line references go stale. This is specifically the docs/kb concept map; it is NOT for editing .claude/playbook, writing READMEs, re-importing the OKF SPEC.md from upstream, or changing code or tests.
Implement ONE approved Synto implementation plan end-to-end by driving the implement-plan workflow. Takes the plan's path (or slug) under docs/superpowers/plans/, runs preflight, hands it to the batched self-rotating engine (per-unit green-gate + bookmark-B integration + deep end-review), and reports what landed. Use when a written plan is ready to build.
Evaluate codebase quality across four dimensions (correctness, maintainability, performance, testability) plus the principal-engineer lens. Produces a scorecard usable as a quality gate.
Produce a dense, copy-pasteable handoff that lets a fresh, memoryless agent resume the current thread of work. Use when wrapping up a session, running low on context, pausing work, or handing the active task to a new agent window.