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.From its SKILL.md
npx -y skills add aylee/agent-os --skill briefAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 244 tokens by cl100k_base, as published. Nobody here has run it
Brief
Produce a decision-ready brief, not a transcript of the work that led to it.
- Resolve the owner binder. Read its
BINDER.md, linked active workstream, relevant area context, andlibrary/reference/me.mdwhen voice matters. - Inspect
library/templates/brief.md. Reuse its structure only where each section earns its place. - Establish audience, decision or outcome, evidence, constraints, scope, risks, and next step. Ask only for material facts that cannot be discovered.
- 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.
- Keep execution state in the linked
WORKSTREAM.md; do not duplicate status logs in the brief. - 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.
What ships with it: 2 files
532 B alongside SKILL.md
agents/
- agent-os.yaml301 B
- openai.yaml231 B