paperclip-distill

Topics in the source

• Paperclip Distill
• When this skill is needed
• Destination space
• Inputs
• Paperclip Asset Gate
• Anti-patterns to avoid
• Workflow
• Voice

Distill Paperclip project, issue, comment, and document activity into durable wiki pages. The success criterion is wiki-insightful, not procedural: a reader who has never seen Paperclip should learn what the project is, what was decided, what is at risk, and what the current state is — without scanning a list of ## [YYYY-MM-DD] headers. Cursor-window distillation: the routine fed you a bounded source bundle of recent Paperclip activity for one project or root issue. Backfill: the user asked to seed the wiki with the historical activity of a project or root issue. Source window may be wide. Manual distill-paperclip-now request from the UI. If the operation issue is operationType: "ingest" (raw file) or operationType: "query", this is the wrong skill — use wiki-ingest or wiki-query. In Phase 1, every Paperclip distill, backfill, and cursor-window operation writes into the default wiki space. The operation issue should always carry spaceSlug: "default". If an operation issue passes any other slug, stop and surface the mismatch in a comment — do not write Paperclip-derived pages into a non-default space. This rule is destination-only. The Paperclip source scope (which projects, root is

This is an excerpt. Refer to the complete source and its current requirements.