gf-implement

Direct implementation without planning reads task context from next-task.json, writes required tests, implements code changes, runs verification suites, and generates a digest documenting modifications for validation.

Writing tests and implementing code for greenfield tasks executes directly from next-task.json data, applying code changes alongside optional tests, running the project test suite, and writing a validation digest to .aw/digests/.

Direct-greenfield task execution bypasses planning to accelerate delivery by reading task context, implementing code, executing verification suites, and documenting changes, which is needed when tasks are flagged for direct execution.

Direct task implementation works without a planning phase by reading next-task.json and related files to execute code changes, write tests when needed, and perform verification directly within the greenfield workflow.

Verifying code changes and documenting them after implementation runs the project test suite for validation and writes a digest to .aw/digests/implement-task-N-digest.md detailing what changed and how to validate it.

You should avoid bypassing planning for task implementation when tasks are not flagged for direct execution, as this approach is designed specifically for direct-greenfield tasks where context is already defined in next-task.json.