phase-harness

End-to-end project phase execution orchestrates sequential phases from clarify to report, generating progressive artifacts under .harness/ and docs/progress while enforcing non-committal harness state until release. It manages phase prompts and supports optional subagent integration for structured workflows.

Structured phase progress tracking is a disciplined workflow that turns scattered tasks into sequential artifact-generating phases. It applies to learning projects and codebases requiring evidence collection, running from clarify through plan and implement to report, documenting each step progressively.

To initialize artifact pipelines, run a phase harness session which creates the .harness/ directory structure and begins the phase flow. This sets up the orchestrated framework to manage phase prompts and collect evidence across the project lifecycle.

Subagent integration is supported for evidence collection within phase-based workflows. The orchestration framework manages phase prompts and artifact pipelines while optionally delegating tasks to subagents, ensuring artifacts are generated progressively under .harness/ and docs/progress directories.

Phase work orchestration enforces non-committal harness state until release, ensuring generated artifacts under .harness/ and docs/progress remain isolated. This prevents partial or incomplete phase artifacts from affecting the main project state until explicitly released.

Managing artifact pipelines from clarify to report requires an orchestrated framework that sequences phases and generates progressive artifacts. This approach manages phase prompts, supports subagent integration, and maintains artifact isolation under .harness/ and docs/progress until release.