Provide support for agent generating technical design prior to making code changes (markdown format).
Agent should request approval of the design before changing code.
I have had success asking for informal proofs when generating technical designs.
Agent command sequence:
Build current-state propositions. Start by reading the technical design.
Build change propositions.
Check the proof. Confirm in code.
Write tests for the design.
Implement.
This task was just implemented. Run all tests. Fix tests.
Example of technical design doc:
# Task 03 - Proof: Use multi-check
Please read [apply-all-technical-design.md].
Proof process:
- Write propositions which establish the current state.
- Write propositions which clearly describe a set of system changes. These should provably satisfy the conclusion.
- Cite sources as [filename:element-name]
## Primary conclusion
Multi-check handling from createApplySuggestionsCommands can replace the implementation in ApplyAllSuggestionsMenuItem by the process described.
## Current-state Propositions
### Proposition: ApplyAllSuggestionsMenuItem uses direct redlining operations without the comprehensive state management of createApplySuggestionsCommands
**Proof:**
Claim 1: ApplyAllSuggestionsMenuItem implements its own redlining logic directly
Evidence: ...
## Change Propositions
### Proposition: ApplyAllSuggestionsMenuItem can be refactored to use useApplySuggestions
**Proof:**
Claim 1: ...
## Conclusion Demonstration
The propositions establish that: ...