Closed-Loop Workflow
Harness repositories are designed around an explicit loop:
- Define intent through
PRODUCT_SPECS.md and the relevant product specs.
- Capture architecture and tradeoffs in design docs.
- Create an ExecPlan before non-trivial implementation.
- Implement incrementally and run validations.
- Run a separate validation subagent with a distinct prompt that points the reviewer to
REVIEW.md.
- Resolve findings and rerun validation until no material issues remain.
- Archive evidence under a day-based folder in
features/generated/.
- Update
CHANGELOG.md and version numbers only when the user explicitly requests or approves that release bookkeeping.
- Review changes against explicit expectations.
Validation Subagent Priority Order
The validation subagent should evaluate the latest feature in this order:
- correctness, regressions, and repository-guideline compliance;
- test execution and validation output;
- code repetition plus improvements in style or code organization.
Context For The Validation Prompt
The validation prompt should:
- point to the active ExecPlan when one exists;
- otherwise provide a contextual summary of the latest feature;
- instruct the subagent to follow the repository guidance in
AGENTS.md and REVIEW.md.
Changelog And Version Rule
- Keep notable release history in the root
CHANGELOG.md.
- Ask the user before editing changelogs or version numbers.
- If the user declines, continue the requested work without touching changelog or version references.