harness-plan

To keep Plans.md and spec.md in sync, this planning harness produces a Spec delta and validates multi-perspective alignment before tasks are added. It enforces traceability and root spec integrity during task governance.

Defining a clear Definition of Done for Plans.md tasks is automated by applying risk-aware gating and generating explicit DoD for each task. This ensures dependencies and progress markers are established upfront.

Yes, you can apply memory reuse and lint baseline checks before adding tasks to Plans.md. The harness enforces these guardrails alongside code change validation and root spec alignment during task creation.

To start generating Plans.md and a Spec delta, invoke the create command to process input requirements. This automates planning and produces actionable tasks with clear DoD for research workflows.

Multi-perspective validation directly improves task governance in research harness workflows by applying risk-aware gating before tasks are added. It ensures proposals align with the root spec and pass memory checks.

You should not use automated planning for research harness workflows if your proposals require lightweight, manual adjustments rather than formal Spec delta generation, risk-aware gating, and strict DoD enforcement.