Writer's Loop

Writer's Loop

Core Rule

Extract preferences only from explicit user decisions:

• Approved or rejected plans
• Accepted, rejected, or undone edits
• Manual rewrites that change style, voice, or structure (not fact corrections)
• Explicit standing preferences declared by the user

Never extract preferences from unreviewed drafts, one-off comments, fact corrections, or current-task constraints. Learn from decisions, not raw drafts.

When to Use

Use for writing where quality depends on structure, audience fit, correctness, style, or iteration — typically 300+ words or any writing where feedback and refinement are expected:

• Coding plans, implementation plans, and technical proposals
• Business reports, research summaries, executive updates, and memos
• Product specs, design docs, documentation, and tutorials
• Fiction chapters, essays, scripts, speeches, and narrative outlines
• Poetry (limited support — use custom rubric; see references/artifact-types.md)
• Academic papers and whitepapers (limited support — adapt to venue requirements)
• Brand-governed or legally constrained writing (legal, clinical, regulatory, corporate)
• Style learning or style distillation from the user's own writing, permitted reference samples, files, pasted text, chapters, reports, docs, or codebase prose
• Translation where meaning, source-language writing style, voice, rhythm, formatting, terminology, or cultural effect matters

Do not use for tiny one-off text edits unless the user asks for a reusable process or preference learning.

Core Loop

Follow the loop in order. Do not emit a later-stage section before its gate has passed:

1. Frame: Identify artifact type, audience, purpose, constraints, success criteria, and desired tone.
2. Question Gate: Ask only blocking questions. If context is enough, state assumptions and continue.