---
name: briefing
description: Generates a plain-language briefing summarizing what happened, what went well, what didn't, and what's next. Written for a non-developer audience.
disable-model-invocation: true
---

# Generate Briefing

Write a plain-language briefing to `docs/status/BRIEFING.md`. This is for someone who may not be deeply technical. Write in simple, clear language.

## Format

```markdown
# What Happened Today — [DATE]

## In Plain English
[2-3 sentences explaining what was accomplished in everyday language.
No technical jargon. Describe what the USER can now do, not what code was written.]

## What Went Well
- [Things that worked smoothly]
- [Decisions that turned out to be good]

## What Didn't Go Well
- [Problems encountered]
- [Things that took longer than expected]
- [Anything still broken or delayed]

## Decisions Made
- [Any important decisions, explained simply]
- [Why they were made]

## What's Next
- [Specific next steps in plain language]
- [Any input needed from the user]

## Questions for the User
- [Anything that needs input or decision]

## Numbers
- Features/components built: X
- Bugs found and fixed: X
- Critical issues: X
- Pipeline runs this session: X
```

## Rules

- NO technical jargon — explain everything as if talking to a smart non-developer
- Be honest about what didn't go well — directness is valued
- Always include what input is needed from the user
- Reference the agent report for technical details if needed