workflow-code-generation

To safely automate code changes, this workflow evaluates complexity, verifies spec.md, generates tasks.md, and executes tasks sequentially. This ensures traceability and quality through controlled execution and optional code-review loops.

Yes, this workflow handles code modifications across Python, Go, and C++ files like .cc, .cpp, .h, and .py. It acts as the unified entry point for feature additions, optimizations, bug fixes, and refactors in these languages.

The best way to ensure traceability during code generation is to enforce a standard flow that validates specs and generates task lists. This workflow orchestrates sequential task execution and optional code review loops to maintain quality.

Yes, you need a spec.md file to start automated task generation. The workflow verifies the spec to ensure completeness, breaks it down into executable tasks within tasks.md, and then orchestrates their execution one by one.

You should not use this automated workflow for modifications to non-code files like .md documentation. It is specifically designed to evaluate complexity and execute tasks only for code files such as .cc, .cpp, .h, .go, and .py.

The code-review loop works by optionally evaluating executed tasks during sequential orchestration. If necessary, it triggers a review loop to ensure quality control and traceability before proceeding to the next code modification task.