Writing & Documentation Skills

Root operating protocol for all interactions. Defines behavioural rules, FCP (Forced Classification Protocol), FCoP (Forced Count Protocol), multi-pass reading, position holding, graduated process trace, ICP (Intent Convergence Protocol), conversation health monitoring, directive management, drift mitigation, and deliberative agent orchestration. Invoke at session start. Literal step-by-step execution required, not summary adherence.

Generates a structured continuation block for carrying work state into a new conversation. Use when the user says "context transfer", "handoff", "generate transfer", "continuation block", or asks for something they can paste into a new chat to continue specific work. Not a summary. A continuation point that tells the new instance what state to be in.

Use this skill for creative writing collaboration when the user explicitly activates creative mode (for example: "creative mode", "workshopping", "drafting", or direct equivalent). Use for brainstorming, prose drafting, structural analysis, and critique of fiction or creative nonfiction while preserving anti-sycophancy and evidence-first assessment. Do not trigger from context pattern matching alone.

Use for ALL file creation, modification, and editing tasks. Defines operation tiers, smart file targeting, large file strategy, multi-file dependency ordering, and verification. Invoke before any file operation. Re-invoke every 5 messages during file-heavy work.

Use when the user requests critical review, verification, or analysis. Mode A handles iterative document editing (regression checking, content loss detection, register alignment, cross-reference propagation across file dependencies). Mode B handles analytical/factual review (evidence evaluation, position stability, multi-theory comparison, depth beyond surface). Read this skill when the user asks for review, verification, critical analysis, or editorial checking. Integrates with nocap.

Defines a four-phase investigation protocol for any problem, claim, error, anomaly, or system failure the user presents. Prevents premature conclusion-jumping and guess-and-check thrashing. Use when the user presents a problem to diagnose, an anomaly to explain, a claim to evaluate, or a situation where the cause is unclear. Integrates with nocap.