hosioobo

Turn a complex development or research goal into a living work map, decompose it into stages and tasks, identify dependencies and parallel tracks, assign and adapt sub-sessions, follow work to completion, and prevent over-engineering. Use when Codex is asked to act as a meta director, create or maintain a development map or work plan, coordinate multiple workstreams or sessions, continue an existing multi-stage project, or keep execution aligned with the original goal. Do not use for a simple one-step task unless explicitly requested.

Create or manage a Hatch lifecycle workspace when a project needs a private workbench, a public-safe product repo, and evidence for publication: initialize a new workspace or promote selected work into a public-ready product snapshot with a brief, audit, version log, evidence, and readiness check. Use for an explicit `$hatch` lifecycle request, or implicitly only inside a workspace with a `hatch.toml` marker and one of those lifecycle intents. Do not use for ordinary coding, builds, tests, Git operations, deployments/releases, generic skill creation or installation, or Codex animated-pet work. Bootstrap Hatch itself only after an explicit self-hosting request.