# Brief

> Write or revise a concise project brief or one-pager. Use when the user asks for stakeholder alignment, a proposal, a one-page brief, or an edit to an existing brief artifact.

- Skill: `aylee/brief` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add aylee/brief`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aylee/brief/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: aylee (https://skillmd.com/u/aylee)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/aylee/brief

---


# Brief

Produce a decision-ready brief, not a transcript of the work that led to it.

1. Resolve the owner binder. Read its `BINDER.md`, linked active workstream, relevant area context, and `library/reference/me.md` when voice matters.
2. Inspect `library/templates/brief.md`. Reuse its structure only where each section earns its place.
3. Establish audience, decision or outcome, evidence, constraints, scope, risks, and next step. Ask only for material facts that cannot be discovered.
4. For an existing file, preserve settled facts and edit in place. For a new file, write it inside the owner binder with a descriptive filename.
5. Keep execution state in the linked `WORKSTREAM.md`; do not duplicate status logs in the brief.
6. After writing, summarize what changed, unresolved questions, and the artifact path. Do not create a receipt for the document edit.

If the work changes current execution state, update the linked workstream
separately and create a receipt only for that workstream revision transition.

Do not invent links, metrics, quotations, or stakeholder positions. Do not commit or publish unless the user separately asks.