status-update

name	status-update
description	Update task document and roadmap with session results. Use when user says "status update", "update status", "update roadmap", "update task", or after code review is complete. Documents what was completed, decisions made, and updates roadmap progress.

Status Update

Updates task document and roadmap with implementation results from the session.

Workflow

Step 1: Identify Documents

Determine which files to update:

Task Document: User specifies path, or infer from session context

• Pattern: ai_docs/tasks/XXX_feature_name.md

Roadmap: Always update

• Path: ai_docs/prep/roadmap.md

If task document path unclear, ask:

"Which task document should I update? (e.g., ai_docs/tasks/026_prompt_detail_page.md)"

Step 2: Gather Session Information

Collect from the session:

• Completed items: Tasks marked done, files created/modified
• Not completed items: Deferred work, known gaps
• Design decisions: Q&A outcomes with rationale (the "why")
• Change requests: Any approved modifications to settled work
• Files created/modified: Full list with line counts

Step 3: Update Task Document

Add or update these sections:

## What Was Completed
- [x] Item 1 ✓ YYYY-MM-DD
- [x] Item 2 ✓ YYYY-MM-DD

## What Was NOT Completed
- [ ] Item 3 — Deferred to [Phase/Task]
- [ ] Item 4 — Reason for deferral

## Design Decisions (Q&A Resolved)
| Decision | Choice | Why |
|----------|--------|-----|
| [Topic] | Option [X] | [Rationale] |

## Change Requests to Settled Work
- **CR#1**: [Description] — Approved YYYY-MM-DD
  - Affected: [File/Component]
  - Reason: [Correctness/Scalability/Safety]

## Files Modified
| File | Changes |
|------|---------|
| `path/to/file.ts` | Created (XX lines) |
| `path/to/other.tsx` | +XX/-XX lines |

Step 4: Update Roadmap

Locate the relevant Phase and Subsection in ai_docs/prep/roadmap.md.

Update status markers:

• [ ] → [x] for completed items
• Add ✅ COMPLETED (YYYY-MM-DD) to subsection header
• Add Task Document reference

Add summary block:

### Subsection Name ✅ COMPLETED (YYYY-MM-DD)
[Goal: Original goal statement]
**Task Document**: `ai_docs/tasks/XXX_feature_name.md`

**What Was Completed:**
- [x] Item 1
- [x] Item 2

**What Was NOT Completed:**
- [ ] Item 3 — Deferred to [Phase X]

**Design Decisions (Approved YYYY-MM-DD):**
| Decision | Why |
|----------|-----|
| [Choice made] | [Rationale] |

**Change Requests to Settled Work:** None required
OR
**Change Requests to Settled Work:**
- CR#1: [Brief description]

Step 5: Verify Updates

Read both files after updates to confirm:

• Checkboxes correctly marked
• Dates are accurate
• Decision rationale is clear (why, not just what)
• Cross-references are correct

Step 6: Present Summary

## Status Update Complete

**Task Document:** `ai_docs/tasks/XXX.md`
- Added: [X] completed items, [Y] design decisions, [Z] files
- Deferred: [N] items to future work

**Roadmap:** `ai_docs/prep/roadmap.md`
- Updated: [Phase X] → [Subsection Y]
- Status: ✅ COMPLETED

**Ready for:** commit-push

Example Usage

User: "status update for task 026"

Response:

1. Identify: ai_docs/tasks/026_prompt_detail_page.md + roadmap
2. Gather: 8 completed items, 2 deferred, 5 design decisions
3. Update task doc with completion status and decisions
4. Update roadmap Phase 6B → Prompt Detail Page section
5. Verify cross-references
6. Present summary

Key Principles

• Document the "why": Decisions need rationale, not just outcome
• Accurate dates: Use actual completion dates
• Cross-reference: Link task docs from roadmap
• Complete picture: Include both completed AND deferred items