phase-finalize

Automating code review and testing before finalizing an epic workflow involves delegating pre-test reviews, enforcing feedback implementation, writing missing tests, and running the full test suite. This ensures code quality and test coverage are verified before final commits.

The best way to ensure documentation and changelog updates are committed at the end of a development cycle is to coordinate finalize phase workflows. This orchestrates doc-writer and doc-updater subagents to finalize public-facing or internal feature docs and tracking files.

No, you cannot skip code review feedback during the finalize phase. The process enforces mandatory implementation of all review feedback via fixer or scribe subagents, ensuring no changes are skipped before tests are run and final commits are made.

Yes, subagent delegation is required to run end-of-epic finalization workflows. The process depends on delegating tasks to code-reviewer, fixer, test-writer, tester, doc-writer, and doc-updater subagents to complete code reviews, testing, and documentation.

The finalize phase handles missing tests by delegating test creation to a test-writer subagent if they were not created during the Build stage. After writing the missing tests, it runs the full test suite to verify all code changes.

You need to commit tracking files in an epic-stage workflow during the finalize phase. This is the only phase where stage tracking files are committed, ensuring the changelog and tracking updates reflect the completed finalization of the epic.