executing-plans

You can execute a written implementation plan with TDD by loading the plan file, validating tasks, running tests, logging decisions to a knowledge brain, and automatically updating canonical documentation.

Automating feature rollouts with tests is achieved by enforcing a validation gate that typechecks, lints, and runs tests before declaring task completion, while automatically noting unresolved issues for follow-up.

Brain-backed logging works by hydrating context from a knowledge brain before executing tasks, then automatically logging significant decisions made during the task execution back into the brain.

Yes, you need a written plan file to start automating task execution, because the workflow requires loading and critically reviewing the plan before executing bite-sized tasks with tests and documentation updates.

You can use this workflow for refinement cycles and feature spinoffs, as the execution applies across any scenario where written plans exist and require disciplined execution with test validation and brain logging.

Unresolved issues discovered during the validation gate are optionally noted for follow-up, ensuring the workflow completes the current task cycle while tracking lingering problems for future resolution.