
Readable primary-flow–first code structuring with minimal boundaries, atomic composition, and contract-driven unit tests
Compose, restructure, and review engineering docs and multi-file documentation packages. Use when cleaning up or assessing design docs, implementation plans, migration plans, runbooks, PR narratives, handoffs, task-doc bundles, or documentation sets for reader flow, source fidelity, ownership/source-of-truth, stale material, backlog/log/evidence separation, and implementation readiness.
Keep durable coding-agent repo context across sessions, handoff, long-running implementation, multi-agent follow-through, and reusable reference notes.
Audit scattered repository docs and notes, then move only the right working context into the `project-context` structure.