Menü
How to create deliverable artifacts (meeting prep briefs, draft emails, analyses) in artifacts/ with required structure and source manifests.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Required procedure for answering questions about the client - grounding, citation format, conflict handling, and how to say "not in the workspace".
How to record completed work in logs/agent-log.md so humans can inspect what the agent read, wrote, and concluded.
How to extract durable memories from sources and write them as reviewable candidate memory files with provenance, confidence, and sensitivity.
How to orient inside a client workspace - the directory layout, the manifest, provenance records, and which sources outrank which.
| name | drafting-artifacts |
| description | How to create deliverable artifacts (meeting prep briefs, draft emails, analyses) in artifacts/ with required structure and source manifests. |
Artifacts are deliverables the agent produces for humans: meeting prep briefs, draft client emails, analyses, summaries. They live in artifacts/ and must be self-contained and auditable.
artifacts/<YYYY-MM-DD>-<slug>.md (date = today). Example: artifacts/2026-06-10-annual-review-prep.md.
Every artifact must contain, in order:
---
type: <brief | draft-email | analysis | summary>
created: <ISO timestamp>
task: <one-line restatement of the request>
sources:
- <relative-path>
- <relative-path>
---
# <Title>
<body>
## Open questions
<Bulleted list of unresolved items a human should address, or "None.">
sources list must name every file the artifact relies on.[source: <path>:<line>], same as the answering-with-citations skill.Sections: Client snapshot, What changed since last meeting, Commitments we made, Commitments they made, Agenda recommendations, Open questions. Lead with what the advisor must not forget.
Match the client's preferred tone and channel if known from the workspace. Keep it under 250 words. Include a [DRAFT - requires advisor review] marker at the top of the email body. Never invent commitments or numbers.
State the question, the data used, the method, the finding, and the limitations. Show figures with their source citations.
[MISSING: <what>], and list them under Open questions.