repo-harness-goal

# repo-harness-goal Use this command when the user wants to start a bounded native `/goal` session in Codex or Claude from repo-harness planning artifacts. The command prepares the goal prompt and acceptance contract; the host-native `/goal` feature owns continuation. ## Protocol 1. Confirm the working repo with `git rev-parse --show-toplevel`; read repo-local `AGENTS.md` or `CLAUDE.md`, `.ai/harness/policy.json`, and the relevant `tasks/current.md` projection when present. 2. Require detailed source context before starting `/goal`: a PRD under `plans/prds/*.prd.md`, a Sprint backlog under `plans/sprints/*.sprint.md`, or a pasted/attached document with equivalent problem, users, scope, non-goals, acceptance scenarios, backlog order, and verification criteria. 3. If the user did not attach or name a detailed PRD/Sprint document, stop and prompt them to attach one. The prompt must ask for the PRD/Sprint artifact, target repo/path, desired goal outcome, hard non-goals, and verification surface. 4. Read the PRD/Sprint enough to extract a single goal statement, bounded scope, non-goals, authoritative files, ordered tasks, acceptance checks, rollback or stop condition, and any explicit owner or dependency constraints. 5. Produce a host-ready `/goal` prompt that tells Codex or Claude to use the attached PRD/Sprint as source of truth, preserve repo-harness workflow gates, run one bounded goal, report checkpoints, and stop on verified completion or blocker evidence. 6. When a Sprin...