---
name: updating-status
description: Updates project status files with progress, blockers, decisions, and next steps. Use when user says "update status", "status update", or provides progress information for a specific project outside of meeting context.
---

# Updating Project Status

## Workflow

```
Progress:
- [ ] Step 1: Identify project and updates
- [ ] Step 2: Read current status
- [ ] Step 3: Apply updates with history
- [ ] Step 4: Save
```

## Step 1: Identify Project and Updates

Parse user input for:
- Project name
- Completed tasks (Progress)
- Blockers (if any)
- Key decisions made (if any)
- Upcoming milestones (if any)
- Next steps

If project name not provided, ask user.

## Step 2: Read Current Status

1. Read `LLM-context/status-template.md` for format reference
2. Read `projects/{project}/status.md`

## Step 3: Apply Updates

Transform current status to history format:

```markdown
### [Previous Date]
- Progress: [Summary of previous progress]
- Key Decision: [If any]
- Next Steps: [What was planned]
```

Write new current status:

```markdown
## Current Status
**Last Updated:** [Today's date]

### Progress / Completed Tasks
- [From user input]

### Blockers
- [From user input, or "None"]

### Key Decisions Made
- [From user input, or remove section if none]

### Upcoming Milestones
- [From user input or keep previous]

### Next Steps
- [From user input]
```

## Step 4: Save

1. Show diff of changes
2. Wait for user confirmation
3. Save to `projects/{project}/status.md`

## Input Examples

User might say:
- "update status for alpha: completed API design, blocked on legal review, next is frontend setup"
- "alpha status: done with phase 1, moving to phase 2"
- "update project-beta status" (then provide details)

## Notes

- Keep history entries concise
- Preserve history in reverse chronological order
- If no blockers mentioned, set to "None"