Process step: engineering-log execution spec

=== WAITING FOR ANSWERS (EXECUTION-SPEC) ===

5. After answers (or if inputs are sufficient), follow the prompt in references/exec-spec-prompt.md strictly.
6. Hard requirement for the filled spec: in the template section ## 9. Testing there must be either a list of acceptance test cases or a link to an artifact that contains them.
7. Hard requirement for the filled spec: explicitly state that the executor must work by TDD using those acceptance test cases.
8. Hard requirement for the filled spec: include a test definition of done that states “all acceptance test cases are implemented and pass”.
9. Conventions rule: do not duplicate test coding rules in the spec.
10. Conventions rule: provide links to the relevant conventions instead.
11. Default requirement: if the task impacts any public API (HTTP, RPC, events, DB contracts, or other externally consumed interfaces), explicitly require backward compatibility in TASK_DIR/04-execution-spec.md unless the inputs explicitly approve a breaking change.
12. Hard requirement for the filled spec: instruct the executor to stop and ask the user for clarification/approval if, during implementation, it turns out the spec cannot be followed literally.
13. Hard requirement for the filled spec: instruct the executor to append to the implementation chat transcript as they go (after each completed step) and not fabricate it if saving is not possible.
14. If a required link or acceptance cases cannot be provided factually from inputs, ask for it as a clarifying question and stop with === WAITING FOR ANSWERS (EXECUTION-SPEC) ===.
15. Write the final document to TASK_DIR/04-execution-spec.md in English and output the exact same text to chat.
16. Ask whether the current chat transcript may be saved.
17. If yes, append to the transcript as you go, after each completed step, instead of saving only at the end.
18. Save the transcript to TASK_DIR/chats/03-execution-spec-chat-1.md.
19. If you cannot save the transcript automatically, do not fabricate it.
20. Ask the user for help or use $exporting-chat-artifacts.