Entry Points
Choose a human Finder depth, bounded decision flow, accepted delivery work, or CLI operation
Harness entrypoints start from the state of the work. Use a human-invoked Finder wrapper when one request needs durable product placement, shippable behavior, or technical delivery closure. Use another Core entrypoint when the problem is already bounded, an Atomic skill for one small move, or a Command for CLI maintenance.
Get Started remains the first-run path for installation and first command guidance. This overview answers what Harness can do once you are choosing the work mode.
Core
Core entrypoints are the major workflow starts. They turn a project intent, accepted scope, runtime symptom, branch, finding set, or docs change into a bounded Harness run.
Business Finder
Capture uncertain business intent and optionally project Product Areas or Initiatives.
Functional Finder
Capture functional behavior and optionally project Business structure plus Epics.
Brainstorming, Requirements, And Backlog Definition
Close bounded decisions, compile an agent-ready spec, then project delivery backlog.
Design
Turn design evidence into approved artifacts, backlog context, and delivery-ready shape.
Implementation
Move an agent-ready spec through backlog projection, planned worker waves, validation, review, and docs closeout.
Debugging
Start from a concrete symptom, gather runtime evidence, patch the proven cause, and rerun the failing gate.
Review
Inspect a branch or diff with review lenses before merge.
Massive Bug Hunt And Fix
Discover candidate findings, inspect them, choose what matters, and resolve selected work within bounds.
Docs Update
Update durable wiki knowledge after implementation changes behavior, setup, contracts, or workflow.
AFK delivery is an implementation child route for unattended delivery: AFK Implementation.
Atomic
Atomic entrypoints are intentionally small operating moves. They can start useful Harness work without a full lifecycle wrapper.
parallel-research: split independent readonly investigation across bounded questions, paths, or hypotheses, then converge on evidence.handoff: preserve the useful continuation state when context should move across agents, sessions, or time.
Commands
Command capabilities start from the hi CLI. The overview names the capability; the CLI docs own mechanics.
hi update: refresh generated Harness scaffold files and inspect scaffold drift.hi report: create a report with the evidence needed for triage and follow-up.
Where To Go Next
Choose Finder only for optional human-invoked intake. Business may project Product Areas and Initiatives; Functional may project that Business structure plus Epics. Choose Brainstorming, Requirements, And Backlog Definition for the sole Requirements Grill, Create Spec, and delivery-depth Write Backlog route. Choose Design for a visual artifact decision, and Implementation after delivery authority is agent-ready. Choose Atomic when the next move is one skill-sized action, and Commands when the task starts from scaffold state or a reportable issue.