i9wa4 Logbook
Owns non-code artifact lifecycle and delivery: where working artifacts live, when to create or reuse them, how to discover them on resume, and how to prepare approved human-facing Secret-Gist delivery.
A logbook entry is a local Markdown file (mkmd) or a Secret Gist — never
claude.ai's Artifact/canvas feature (hence this skill's name, not
artifacts). Route /artifacts questions to artifact-design; see
references below for mkmd vs. Gist.
Follow the active runtime/session language policy or explicit request. This skill does not define its own output language defaults.
1. Workflow
- If the requester supplied an artifact path, use that path as canonical.
- If no path was supplied, use Local Markdown Artifacts to discover work-start or resume candidates before creating a file.
- Reuse one matching active artifact for the same repo, branch, task, and purpose; create a separate file only for a genuinely separate purpose.
- If durable state is needed and no path exists, create a markdown artifact
with the cwd-independent
mkmdcontract in the local markdown reference. - For human-facing Secret-Gist delivery, read Secret-Gist Delivery and require current approval before any external mutation.
- Keep local artifacts as task state. Treat Gists as approved delivery copies, not task memory, source of truth, or cross-machine persistence.
2. References
- Local Markdown Artifacts
- Secret-Gist Delivery