create-code

Code implementation from a plan file follows TDD workflows by executing tasks sequentially, integrating linters, and running tests to verify quality against acceptance criteria. This ensures development adheres to technical specifications and validates functionality before completion.

Plan-driven code implementation automates writing code based on a pre-defined plan file, ensuring structured development. You need it when executing validated tasks sequentially to maintain adherence to technical specifications and quality assurance standards.

Yes, linters and tests integrate directly into the code implementation process to verify quality and functionality. They execute alongside sequential task processing to ensure code style compliance and validate acceptance criteria before completion.

When no specific plan file is provided, the code generation process handles plan discovery and prompts user confirmation. This ensures the implementation targets the correct validated plan before executing any sequential code changes.

Plan-based implementation integrates seamlessly into development workflows by following plan creation and preceding code review. It executes code changes sequentially based on tasks outlined in a specified plan file, fitting into the larger development cycle.

Code implementation requires a validated plan file to ensure development follows a structured process. This plan-driven approach guarantees sequential task execution adheres to acceptance criteria and technical specifications, preventing unstructured code generation.