Status Update

---
name: status-update
description: When the user says "@status update" or "status update", execute this
  command.
---

---
name: status-update
description: Podsumowanie stanu projektu: wersja, faza, zmiany, następne kroki. Triggers: status projektu, stan, podsumowanie
---

# status-update (Manual Command)

## Trigger

When the user says **"@status update"** or **"status update"**, execute this command.

---

## What to Do

Provide a concise 3-5 bullet point summary of the project's current state and next steps.

### Step 1: Read These Files (in parallel)
- `logs/DEVLOG.md` → "Current Context (Source of Truth)" section
- `logs/DEVLOG.md` → "Current Objectives" section
- `logs/CHANGELOG.md` → "Unreleased" section
- `logs/adr/README.md` → Recent ADRs (if any)

### Step 2: Extract Key Information
- **Current version** (from DEVLOG Current Context)
- **Active branch** (from DEVLOG Current Context)
- **Active phase** (from DEVLOG Current Context)
- **Recent changes** (from CHANGELOG Unreleased - last 3-5 entries)
- **Current objectives** (from DEVLOG Current Objectives - unchecked items)
- **Known risks/blockers** (from DEVLOG Current Context)

### Step 3: Format the Output

Use this exact format:

```markdown
📍 **Status Update - [Project Name]**

**Current State:**
- **Version:** [version]
- **Phase:** [phase] - [brief description]
- **Branch:** [branch name]

**Recent Progress:**
- ✅ [Recent accomplishment 1]
- ✅ [Recent accomplishment 2]
- ✅ [Recent accomplishment 3]

**Next Up:**
- [Next objective 1]
- [Next objective 2]
- [Next objective 3]

**Risks/Blockers:**
- [Risk/blocker 1, or "None currently"]
```

---

## Example Output

```markdown
📍 **Status Update - Log File Genius**

**Current State:**
- **Version:** v0.1.0-dev (pre-release)
- **Phase:** Foundation - Repository structure complete, ready for launch
- **Branch:** main

**Recent Progress:**
- ✅ Created README.md with quick start and migration guide
- ✅ Added CONTRIBUTING.md for community engagement
- ✅ Moved Augment rules into starter pack for better distribution

**Next Up:**
- Set up GitHub repository features (About, Topics, Template button)
- Create issue templates for bug reports and feature requests
- Consider GitHub Pages for documentation hosting

**Risks/Blockers:**
- None currently
```

---

## Tips

- Keep it concise (3-5 bullets per section)
- Focus on actionable information
- Highlight what's changed recently
- Be specific about next steps
- Update if planning files are out of sync