File to the subject
File every output (a task, a document, a message, an issue, a note) to the subject it is about, with attribution. Use whenever you produce something the team should see later.
Output that lives only in your chat is lost when the chat ends. File it to the subject, so the next person and the next agent find it.
Procedure
- Choose the right kind of output.
- Work someone must do: a task.
- A longer text the team reads and edits: a document.
- A short update to the people on the subject: a message.
- A settled choice: a decision. See record-a-decision.
- A bug or change in code: an issue on the linked repository.
- Attach it to the subject's door. Never create an output with no subject when a subject exists.
- Write it so it stands alone. A reader who did not see your chat must understand it. Name the source: the call, the document, the message.
- Keep the attribution. You act for a person. Do not write as if the person wrote it by hand. The store shows your client name beside the output.
- Return the door. Tell the person what you filed and where, with the new thing's door.
Rules
- One output, one place. Do not post the same text as a message and a document.
- Follow propose-dont-apply for output other people see at once, such as a message to a channel.
- Use an
idempotency_keywhen you retry a write.
On Starlings
| Output | Tool |
|---|---|
| Task | task |
| Document | docs_write |
| Message | send_message |
| Issue | create_issue |
| Goal | set_goal |
| File a quick note | task, create_issue, send_message or docs_write, with the note's id as quick_note |
Install: SKILL.md · Source: standard/skills/file-to-the-subject/SKILL.md · Apache-2.0