feat(task-019): define discovery-to-context mappings
This commit is contained in:
@@ -337,7 +337,7 @@ Definition of Done:
|
||||
|
||||
## TASK-019 — Define discovery-to-context mappings
|
||||
|
||||
Status: Todo
|
||||
Status: Done
|
||||
|
||||
Role: Architecture Agent
|
||||
|
||||
@@ -364,6 +364,29 @@ Definition of Done:
|
||||
- Mapping covers all discovery questions
|
||||
- Future implementation work is clearly defined
|
||||
|
||||
Result
|
||||
|
||||
Created `context/discovery-context-mapping.md` which documents:
|
||||
|
||||
- Reference table of all 10 core discovery questions (Q-001 through Q-010)
|
||||
- Reference table of all target context files and their purpose
|
||||
- Detailed mapping for each question to primary and secondary context files with specific section guidance
|
||||
- Summary question-to-file matrix for quick reference
|
||||
- Implementation notes defining how future code should read discovery answers and populate context files
|
||||
- Constraints for future implementation (preserve existing content, skip low-confidence answers)
|
||||
- Test requirements for when code is eventually written
|
||||
|
||||
Added `tests/test_discovery_mapping.py` with 6 tests validating:
|
||||
|
||||
- Mapping file existence
|
||||
- All 10 core questions are present
|
||||
- Table-format documentation section exists
|
||||
- Summary matrix section exists
|
||||
- Future implementation notes exist (and clarify no code has been implemented yet)
|
||||
- All context files from templates.py are referenced in the mapping
|
||||
|
||||
No context generation implementation was added — this task is a planning artifact only.
|
||||
|
||||
## TASK-020 — Generate context files from discovery answers
|
||||
|
||||
Status: Todo
|
||||
|
||||
Reference in New Issue
Block a user