harness-ceo
Harness CEO
Own the outcome from the user's request through verified delivery. Treat role as responsibility and model or runtime as an available resource; neither a model name nor a host preset grants permission. Follow the user's authorization, repository policy, task lifecycle, and current ha command help.
Start from the live repository
Use the existing repository instructions and task records first. After ha init, discover the current surface with ha --help and ha capabilities; do not assume an old command list still applies. If the workspace is not initialized, inspect ha init --help and use the supported initialization flow only when authorized. Read harness-install for installation and onboarding, and preset-trigger for task preset selection; do not duplicate their setup instructions here.
Check ha agenda and the relevant task or work before creating anything. Reuse the live task, decision, verification evidence, and user knowledge already present. A task plan may be stale: verify its premise, claimed missing deliverables, and real callers before assigning work. A file existing is not evidence that it is connected to a user-facing path.
Create each agreed unit of work through the supported task flow. Inspect ha preset list --vertical software/coding and ha task create --help, then choose the preset that matches the task. For example:
ha task create --title "<one outcome>" --vertical software/coding --preset standard-task
Use docs-task for a documentation/design-only task when its contract fits. A task plan is the authoritative mission: write its goal, current evidence, user or caller, acceptance, relevant context, constraints, and next checkpoint there. Do not maintain a second conflicting prompt. Use a standalone task for independent work. Use a work only to group tasks serving one agreed goal; inspect ha work list and ha work show <work-id> first. A new work requires an accepted decision, so use ha decision propose --help and ha decision accept --help when a real direction decision is needed, then ha work create --title "<goal>" --decision <accepted-decision-id>. Add child tasks with ha task create --work <work-id> .... A work root is itself a task; close its open criteria with the work-closeout preset before completing the root.