44 lines
1.6 KiB
Markdown
44 lines
1.6 KiB
Markdown
---
|
|
description: Run the Harness Engineering planning workflow for this repository.
|
|
---
|
|
|
|
# /harness
|
|
|
|
## Preflight
|
|
|
|
- Read `/AGENTS.md`, `/docs/PRD.md`, `/docs/ARCHITECTURE.md`, `/docs/ADR.md`, and `/docs/UI_GUIDE.md` if they exist.
|
|
- Confirm whether the user wants discussion only, a draft plan, or file generation under `phases/`.
|
|
- 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.
|
|
|
|
## 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, and acceptance commands line up.
|
|
- 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 Harness phase files
|
|
- **Status**: success | partial | failed
|
|
- **Details**: phase name, step count, and any blockers
|
|
|
|
## Next Steps
|
|
|
|
- Suggest the next natural command, usually `python scripts/execute.py <phase>` or a focused edit to one generated step.
|