End-to-End Workflow Summary

The complete workflow is a controlled loop:

1. Start with a small persistent context and monitor token usage.
2. Explore the repository with isolated subagents when broad investigation is required.
3. Interview the humans until a shared design concept exists.
4. Summarize the destination in a product requirements document that includes module and

testing decisions.

1. Decompose the destination into vertical-slice issues with explicit blockers.
2. Validate one implementation iteration under human observation.
3. Run bounded AFK implementation sessions with TDD, tests, types, commits, and stop

conditions.

1. Review each result in a fresh context with coding standards pushed to the reviewer.
2. Perform human code review and manual QA, then turn findings into new issues.
3. Preserve deep module boundaries and refactor weak architecture so that feedback remains

meaningful.

1. Parallelize only independent issues in isolated worktrees and sandboxes.
2. Merge, rerun feedback loops, obtain team review, and continue until the destination is

satisfied.

The workflow succeeds by refusing two extremes. It does not require a human to type every line of implementation, and it does not permit an agent to convert a vague specification directly into unreviewed software. It uses agents for speed while retaining human control over meaning, structure, and quality.