---
description: Run the Report Harness planning workflow for this repository.
---

# /harness

## Preflight

- Read `/AGENTS.md`, `/docs/PRD.md`, `/docs/ARCHITECTURE.md`, `/docs/ADR.md`, `/docs/UI_GUIDE.md`, `/docs/RESEARCH_LOG.md`, `/docs/REPORT_DRAFT.md`, and `/docs/FEEDBACK.md` if they exist.
- Confirm whether the user wants discussion only, a draft report plan, or file generation under `phases/`.
- Check that the report topic, purpose, keywords, direction, audience, and output format are available.
- Note whether the user explicitly asked for subagents; only then consider `phase_planner` or built-in explorers/workers.

## Plan

- State what will be created or updated before editing files.
- If a plan already exists under `phases/`, say whether you are extending it or replacing part of it.
- Keep each proposed step small, self-contained, and independently executable.
- Separate source discovery, deep research, source review, outline, draft, and feedback steps.

## Commands

- Invoke `$harness-workflow` and follow it.
- When file generation is requested, create or update:
  - `phases/index.json`
  - `phases/{phase}/index.json`
  - `phases/{phase}/stepN.md`
- Use `python scripts/execute.py <phase>` as the runtime target when you need to reference execution.

## Verification

- Re-read the generated phase files for consistency.
- Check that step numbering, phase names, report artifacts, and acceptance commands line up.
- Confirm that research steps require web search and `docs/RESEARCH_LOG.md` updates.
- If the repo has a validator, prefer `python scripts/validate_workspace.py` as the default acceptance command unless the user specified a narrower command.

## Summary

## Result
- **Action**: planned or generated Report Harness phase files
- **Status**: success | partial | failed
- **Details**: phase name, step count, report artifacts, and any blockers

## Next Steps

- Suggest the next natural command, usually `python scripts/execute.py <phase>` or a focused edit to one generated step.