Menu
Mine user conversation into raw writing fragments in one markdown file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Generate Codex hooks.json and AGENTS.md from Claude Code hooks. Maps supported hooks directly, including Edit|Write apply_patch aliases, and keeps Stop batch checks only as fallback. Use when setting up Codex compatibility or dual-agent support.
Question changed code as liability and remove unjustified surface area. Use before commit, push, PR, merge, or when a change feels overbuilt or low-value.
Reviews diffs for over-engineering only. Use when reviewing, desloping, or asking what to delete, inline, shrink, or replace with stdlib/native code.
Resilience Review checks resilience. Use when edge cases, errors, fallback, async/data, state, or polish matter.
Reviews a diff since a fixed point across Standards, Spec, and risk gates. Use when reviewing a branch, PR, WIP, or "review since X".
parallel executor. Use /swarm.
| name | writing-fragments |
| description | Mine user conversation into raw writing fragments in one markdown file. |
Interview relentlessly. Capture raw fragments. Do not impose outline/phases.
If path missing, ask once. Remember it. Re-read before every write to preserve user edits.
Capture from first user prompt too.
First write: single H1 working title, then fragments. No metadata/TOC/date.
Readable by author; may not be self-contained for cold reader. Could be sharp sentence, claim, vignette, code snippet, analogy, half-thought, quote, complaint, punchline.
Format:
# Working title
Fragment one.
---
Fragment two.
Use \n---\n separators. No body headings/tags/order beyond capture order.
Append silently. Mention briefly. User can cut/rewrite/merge anytime.