3분 분량언어: 영어
Game jam, team of one: one brief, four handoffs
A solo game jam entrant writes one brief. Octuo hands the bug, the icon and the music to the right tools at once, follows each run and returns one report.
← 전체 글로 돌아가기
‘briefs’ 태그가 달린 글
- #how-to77
- #delegation35
- #reviewing-work29
- #briefs24
- #coding-agents23
- #personal-assistant14
- #long-running-tasks13
- #privacy-and-security10
- #scheduled-routines10
- #writing10
- #canvas7
- #codex6
- #memory6
- #claude-code5
- #data-and-reports5
- #accounts4
- #productivity4
- #product-notes3
- #usage-limits2
- #ai-agents1
- #announcements1
- #comparison1
- #octuo1
4분 분량언어: 영어
How do I tell an AI agent what “done” means?
Write “done” as a check the agent can prove: one measurable end state, a stated check, constraints and a limit. How /goal works in Claude Code and Codex.
3분 분량언어: 영어
A brief for a recurring data pull: what to write down so the tenth run matches the first
Six lines to write into the brief for a recurring data pull (source, period, fields, what to do when the source changes, output name and a sanity range) so later runs stay comparable with the first.
4분 분량언어: 영어
A one-page kickoff for a helper: six things to settle before the first task
How to write a one-page project kickoff covering purpose, what done looks like, fixed and open constraints, who decides, check-ins and where things live, before the first task is handed over.
4분 분량언어: 영어
A one-page voice sheet so your drafts sound like you
How to build a one-page voice sheet from your own writing (samples, sentence habits, word lists, openers and hard limits) so drafts from any helper need fewer edits, and how to test and maintain it.
4분 분량언어: 영어
Before the meeting: ask for a one-page pre-read, not a long summary
How to ask for a one-page meeting pre-read built around what you will be asked to say or decide, in six parts you can read in about three minutes.
3분 분량언어: 영어
Before you paste an email thread into a brief: five things to leave out
A two-minute trim before you paste an email thread into a brief: five things to leave out, how to replace rather than delete, and a one-line note that tells the helper the gaps are deliberate.
3분 분량언어: 영어
Choosing what to keep human: a four-question filter
A four-question filter for deciding which tasks to hand over whole, which to keep and which to split, so the hard-to-undo, personal and judgment-heavy parts stay with you.
3분 분량언어: 영어
From a rambling voice note to a clear brief: five edits
Five quick edits that turn a rambling voice note into a brief a helper can act on: put the outcome first, separate facts from wishes, cut repeats, add the obvious and end with a done line.
4분 분량언어: 영어
Long chats go stale: write a restart note and begin again
How to spot a conversation that has gone stale and restart it with a six-line note covering the goal, decisions, rejected options, current state, open questions and next step.
3분 분량언어: 영어
Rough, usable or final? Say which finish you want before the work starts
Four levels of finish (rough, working, usable and final), how to name the one you want in the first line of a brief, and how to match your review to each level.
3분 분량언어: 영어
Sort your requirements into must, should and nice before you ask for options
A five-step method for sorting requirements into must, should and nice, turning musts into testable lines and asking for options in a simple pass-or-fail table.
3분 분량언어: 영어
Turn the job that went well into a template: five things to replace
How to turn a brief that worked into a reusable template in about ten minutes: labelled blanks, wording kept as it was, a note on what changed last time, fixed versus varying parts, and an owner and date.
3분 분량언어: 영어
When one helper's output feeds another's input: three checks at every handover
Three checks for every point where one step's output feeds the next (shape, completeness and assumptions), plus a four-line handover note and a simple rule for who checks what.
3분 분량언어: 영어
Ask for a checkpoint halfway: what a good partial result looks like
Why to build a checkpoint into a long job, what a useful partial result should contain and where to place the pause so a change of direction is still cheap.
3분 분량언어: 영어
Show the shape of your data, not the data: how to make a safe sample for a brief
How to build a small invented or masked sample with the same shape as your real data, so you can brief a helper without handing over anyone's personal details.
3분 분량언어: 영어
Four requests in one message? Number them so none gets dropped
Five habits for sending several requests in one message so none gets lost: one request per number, order by need, mark dependencies, ask for replies by number, and quote numbers in follow-ups.
3분 분량언어: 영어
Show one good example, and say exactly what to copy from it
How to hand over one good example with clear notes on what to copy, what to change and why it works, so a helper matches your style without reusing old details.
3분 분량언어: 영어
When a handed-off job comes back wrong, look in these five places
A ten-minute postmortem for a handed-off job that came back wrong: check the brief, the inputs, the fit, the check and the scope in order, and change one thing at a time.
3분 분량언어: 영어
One page of definitions your helpers can’t guess: a project glossary
How to write a one-page project glossary: which words belong in it, a four-line format for each entry, where each word is used, words to avoid, and how to hand it over with every task.
2분 분량언어: 영어
How to hand off a chore that only lives in a browser tab
How to write down a repetitive browser chore so anyone can take it over: where it starts, the steps as verbs, what done looks like, what must not happen, and what comes back to you.
3분 분량언어: 영어
How to hand off a research question: five parts of a good brief
A five-part brief for handing off research: the question and the decision it feeds, scope, source rules, the shape of the answer, and what would change your mind, with a full example.
1분 분량언어: 영어
Four sentences that turn an idea into an interactive view
Four sentences that describe a small interactive view clearly enough to lay it out: who uses it and when, what it keeps, what you do with it, and what stays in view.
2분 분량언어: 영어
How to write a bug report that a coding tool can start from
A five-part bug-report brief that a coding tool, a new teammate or you next week can start from: what you saw, minimal repro steps, where to look and not touch, how you'll know it's fixed, and what to send back.