Updated readme and added TDD features

updated /.context/README.md file to accurately reflect the current directory structure and include information about the new TDD integration.

Author: BuildSomethingAI

.context/AI_INSTRUCTIONS.md

@@ -39,6 +39,7 @@ Comprehensive implementation guide for the Aegis framework, containing detailed
    - Target state allowed
    - Dependencies met
    - Progress tracked
+   - Test status appropriate
 
 3. **Memory Validation**
    - Front matter valid
@@ -82,6 +83,8 @@ Comprehensive implementation guide for the Aegis framework, containing detailed
 - [ ] Validate the current task state
 - [ ] Perform the requested task operation
 - [ ] Update the task document
+- [ ] Verify test status when completing a task
+- [ ] Prompt for confirmation if test status is not "Passing" or "Not Applicable"
 - [ ] Update project.json with task changes
 - [ ] Update timestamps to current time
 - [ ] Verify all files have been properly updated
@@ -151,6 +154,7 @@ Comprehensive implementation guide for the Aegis framework, containing detailed
    - Dependencies noted
    - Status updated
    - Next steps defined
+   - Test status managed
 
 2. Directory Structure
 ```
@@ -195,6 +199,33 @@ Comprehensive implementation guide for the Aegis framework, containing detailed
      - Include test files only when the task directly involves testing
      - For framework tasks, include only the specific framework files being modified
 
+4. Test-Driven Development Integration
+   - Purpose: Support TDD workflow within the framework
+   - Implementation:
+     - Each task includes a "Test Status" section
+     - Valid statuses: Not Started, Failing, Passing, Not Applicable
+       - "Not Started": Tests haven't been written yet, or testing has not begun
+       - "Failing": Tests exist but are failing (implementation incomplete/incorrect)
+       - "Passing": All tests are passing (implementation complete and correct)
+       - "Not Applicable": Task doesn't require tests (documentation, planning, etc.)
+     - Related test files are tracked with brief descriptions
+   - Task Completion Logic:
+     - When test status is "Passing", task can be completed normally
+     - When test status is "Failing", prompt user for confirmation before completing
+     - When test status is "Not Applicable", task can be completed normally
+     - When test status is "Not Started", prompt user for confirmation before completing
+   - Status Management:
+     - Update test status when test files are created or modified
+     - Set initial status to "Not Started" for tasks involving implementation
+     - Set initial status to "Not Applicable" for tasks not requiring tests (e.g., documentation)
+     - Track test files path and descriptions in the task document
+   - Best Practices:
+     - Always update test status when related tests are created or modified
+     - Include comments or documentation about test requirements
+     - Link to specific test files in the task document
+     - Explain why a task is marked as "Not Applicable" when applicable
+     - For TDD workflow: tests should transition from "Not Started" → "Failing" → "Passing"
+
 ## Memory System
 
 ### Memory Types
@@ -619,4 +650,27 @@ If you detect inconsistencies between state files and the actual system:
 1. Prioritize the actual system state (files in directories) as the source of truth
 2. Update state files to match the actual system state
 3. Document the reconciliation in your response to the user
-4. Suggest preventive measures to avoid future inconsistencies
+4. Suggest preventive measures to avoid future inconsistencies
+
+### TaskTemplate
+      "FrontMatter": [
+        "title, type=task",
+        "status=[planned|active|completed|hold]",
+        "created=YYYY-MM-DDTHH:MM:SS",
+        "updated=YYYY-MM-DDTHH:MM:SS",
+        "id=TASK-XXX",
+        "priority=[high|medium|low]",
+        "memory_types=[procedural|semantic|episodic]",
+        "dependencies, tags"
+      ]
+    },
+    "RequiredTaskSections": [
+      "Description",
+      "Objectives",
+      "Steps",
+      "Progress",
+      "Dependencies",
+      "Test Status",
+      "Notes",
+      "Next Steps"
+    ],

.context/README.md

@@ -4,21 +4,30 @@ This directory contains the core Aegis framework implementation. Each subdirecto
 
 ## Directory Structure
 
+### ai/
+Contains AI assistant operations and patterns:
+- `operations/`: Operation patterns and command implementation YAML files
+
 ### memory/
 Stores framework and project memory in a structured, file-based system:
 - `core/`: Framework knowledge and operation patterns
 - `project/`: Project-specific memory and state
+  - `context/`: Project context data
+  - `self_improvement.json`: Self-improvement metrics and recommendations
 - `session/`: Temporary session state and context
+- Documentation files:
+  - `SELF_IMPROVEMENT.md`: Documentation for the self-improvement system
+  - `STRUCTURE.md`, `REFERENCES.md`, `STATE_TRACKING.md`, etc.
 
 ### templates/
 Contains document templates for maintaining consistency:
 - `tasks/`: Task definition templates
 - `sessions/`: Session record templates
 - `decisions/`: Decision record templates
 
-### operations/
-Stores operation patterns and command implementations:
-- `core/`: Core command implementations and patterns
+### plan/
+Stores planning documents and resources:
+- `planning_document.md`: Current project plan
 
 ### tasks/
 Manages tasks through their lifecycle:
@@ -27,6 +36,23 @@ Manages tasks through their lifecycle:
 - `hold/`: Tasks waiting on dependencies
 - `completed/`: Finished tasks
 
+### sessions/
+Stores session records and progress:
+- Files named by date: `YYYY-MM-DD.md`
+
+### decisions/
+Stores important decision records:
+- Files named by ID: `DECISION-XXX.md`
+
+## Key Files
+- `AI_INSTRUCTIONS.md`: Comprehensive framework instructions for the AI assistant
+
+## TDD Integration
+The framework now supports Test-Driven Development with:
+- Test Status tracking in task documents
+- Conditional task completion based on test status
+- Support for test statuses: Not Started, Failing, Passing, Not Applicable
+
 ## Usage
 1. Copy this `.context` directory to your project root
 2. Initialize with `/aegis start`

.context/ai/operations/task.yaml

@@ -233,7 +233,11 @@ command_template:
           implementation: |
             1. For create: Copy template and create new task file
             2. For start: Move task from planned to active
-            3. For complete: Move task from active to completed
+            3. For complete: 
+               - Check Test Status section value
+               - If status is "Passing" or "Not Applicable", proceed normally
+               - If status is "Failing" or "Not Started", prompt user for confirmation
+               - Only after confirmation or if status is acceptable, move task from active to completed
             4. For hold: Move task from active to hold
       
       - task_update:

.context/ai/operations/task_transition.yaml

@@ -23,7 +23,25 @@ flow:
         - target_state: {type: state_valid}
         - transition: {type: allowed_transition}
 
-    2_update_task:
+    2_check_test_status:
+      action: check_test_status
+      condition: ${operation} == "complete"
+      checks:
+        - test_status_section: {type: section_exists, section: "Test Status", error: "Test Status section not found"}
+        - test_status: {type: extract_value, pattern: "Status: ([\\w\\s]+)", section: "Test Status", error: "Test status not found"}
+      responses:
+        - condition: ${test_status} == "Passing" || ${test_status} == "Not Applicable"
+          action: proceed
+        - condition: ${test_status} == "Failing" || ${test_status} == "Not Started"
+          action: user_prompt
+          message: "Warning: Task has test status '${test_status}'. Do you want to complete it anyway? (yes/no)"
+          responses:
+            - yes: proceed
+            - no: abort
+      validate:
+        - status_valid: {error: "Invalid test status value"}
+    
+    3_update_task:
       action: update_frontmatter
       updates:
         - field: status
@@ -35,7 +53,7 @@ flow:
       validate:
         - timestamps: {error: "Invalid timestamps"}
 
-    3_move_file:
+    4_move_file:
       action: move_file
       source: ${current_path}
       target: ${target_path}
@@ -44,7 +62,7 @@ flow:
         - target_valid: {error: "Target directory must be valid"}
         - permissions_ok: {error: "Must have write permissions"}
 
-    4_verify:
+    5_verify:
       action: verify_transition
       checks:
         - file_moved: {type: file_check}
@@ -86,6 +104,25 @@ safeguards:
   - cleanup: "Remove any duplicate files"
   - state_check: "Verify state matches directory"
 
+# Test Status validation
+test_status:
+  valid_values:
+    - "Not Started"
+    - "Failing"
+    - "Passing"
+    - "Not Applicable"
+  completion_checks:
+    auto_complete:
+      - "Passing"
+      - "Not Applicable"
+    confirm_required:
+      - "Failing"
+      - "Not Started"
+  error_messages:
+    invalid_status: "Invalid test status: must be one of Not Started, Failing, Passing, or Not Applicable"
+    missing_section: "Missing Test Status section: all tasks must include this section"
+    confirmation_required: "Task has tests in '${status}' state. Confirmation required to complete."
+
 transitions:
   start:
     from: planned