moonlight-lupin/agent-skills / productivity/task-brief
task-brief
VerifiedUse when the user says "brief this task", "scope this properly", "what do you need from me", "improve my prompt", "help me get better output", "turn this into a reusable prompt", "a prompt I can hand to a colleague", or hands over a SUBSTANTIAL task — multi-step, multi-document, or a deliverable someone else will read — as a thin one-line request. Compile a task brief BEFORE starting substantial work — pin down the goal with checkable "done when" tests, context, constraints (standing rules included automatically), and tooling — confirm with the user, then execute against it. Reusable-prompt mode saves the brief as a structured prompt for recurring work instead of running it. Asks at most 2-3 clarifying questions, only where the answer would change the output; otherwise states assumptions in the brief and proceeds. Not for quick one-step asks — answer those directly.
README.md
View on GitHub# task-brief
Prompt-quality skill for AI agents: before substantial work starts, the agent compiles a short
**task brief** — **Goal** (what "done" looks like) · **Context** · **Constraints** (the
organisation's standing rules injected automatically) · **Assumptions** (flagged fills) ·
**Tooling** (which installed skill does the work) — confirms it with the user, executes against
it, then closes the loop against its **Done when** tests (2–5 checkable lines, vague words swapped
for formats, thresholds and dates). **Reusable-prompt mode** saves the brief as a structured
prompt (`[task-name]-prompt.md`) for recurring work instead of running it. At most 2–3 clarifying questions, and only where
the answer would change the output; skips itself on trivial asks.
The user never has to write a better prompt — the agent does the structuring, and a one-word
"go" (or a one-word correction) catches misreadings at the cheapest possible point.
## Structure
```
task-brief/
└── SKILL.md # The whole skill: when to run, the brief shape, compile rules,
# worked example, principles, pitfalls, verification checklist
```
Reasoning-only — no scripts, references or assets.
## Requirements
- None. No Python, no network access, no credentials — pure prompt workflow.
## License
MIT
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |