Load Ticket Context

You are loading the full context for ticket: TICKET-$ARGUMENTS

Required Actions

1. •

   Find the ticket file:

   code

   sprints/sprint-*/TICKET-$ARGUMENTS*.md
   

2. •

   Read the complete ticket including:

   • •Metadata (Sprint, Priority, Complexity, Dependencies, Blocks)
   • •Description
   • •Acceptance Criteria
   • •Technical Details (data structures, code examples)
   • •Files to Create/Modify
   • •Testing Requirements
   • •Definition of Done
3. •

   Check dependency status:

   • •For each ticket in "Depends On", verify it is 🟢 Complete
   • •If any dependency is not complete, WARN
4. •

   Read related context:

   • •Sprint README for overall context
   • •Any referenced files (@path references)
   • •Related tickets if mentioned
5. •

   Identify implementation path:

   • •List files to create/modify
   • •List test files needed
   • •Note any architectural considerations

Output Format

# TICKET-$ARGUMENTS: <Title>

## Status Check
- Current Status: 🔴/🟡/🟢
- Dependencies: ✓ All satisfied / ⚠️ Blocked by TICKET-XX-YYY
- Blocks: <tickets that depend on this>

## Summary
<Full description>

## Acceptance Criteria
- [ ] <criterion 1>
- [ ] <criterion 2>
...

## Implementation Plan

### Files to Create
| File | Purpose |
|------|---------|
| ... | ... |

### Files to Modify
| File | Changes |
|------|---------|
| ... | ... |

### Test Files
| File | Tests |
|------|-------|
| ... | ... |

## Key Technical Details
<Important code structures, patterns, or requirements>

## Ready to Implement?
<Yes if dependencies met, No with explanation if blocked>

Important Reminders

After reading this ticket, follow the work loop:

1. •Plan the implementation (use Plan agent if complex)
2. •Write failing tests FIRST
3. •Implement to pass tests
4. •Run cargo test && cargo clippy
5. •Commit with proper message
6. •Update ticket status in sprint README