writers-loop — Claude Code plugin: what it does, how to install
writers-loop runs writing as a reviewable loop: frame the task, plan, draft, critique, then revise only what you approve. Style memory stays off unless you opt in.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install writers-loop@awesome-codex-pluginsWhat writers-loop does
The plugin splits writing into stages that stay separate. Frame the artifact, audience and constraints, then a plan, a draft, and a critique. The agent asks a question only when the answer would change the outcome. Nothing gets rewritten behind your back: proposed edits arrive with a reason, a scope and a risk, and the text moves after you accept, reject or adjust them.
It ships as a skill folder, skills/writers-loop, with guidance for technical plans, reports, proposals, docs, essays, speeches and fiction. Style distillation works from samples you supply or approve, and translation keeps the voice plus exact technical tokens. For editors that cannot run skills, templates cover Obsidian, Logseq, Notion and Feishu/Lark Docs.
Preference memory is opt-in. Until you say yes, whatever the agent notices about your manner stays inside the session. What it records comes from reviewed decisions, approved plans and accepted edits; its own drafts stay out of that set. Normal use needs no npm package.
What it helps with
- turn a fuzzy brief into a technical plan before any prose
- get a critique of the draft before edits land
- carry your own style onto a new piece from samples
- translate a document without losing terms or tone
- keep writing work inside Obsidian or Notion templates
Example prompts for the agent
- Use
$writers-loopfor a migration plan: audience is the backend team, goal is a decision doc. Short plan first, then a draft, and do not save preferences. - Run
$writers-loopoverREADME.md, propose changes with reasons and scope, and touch only what I accept. - Distill the style of
sample.mdwith$writers-loopand rewrite the intro to match it.
How to install writers-loop
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install writers-loop@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about writers-loop
How do I install writers-loop in Claude Code?
Through the marketplace, two commands in order: /plugin marketplace add hashgraph-online/awesome-codex-plugins, then /plugin install writers-loop@awesome-codex-plugins.
What does writers-loop do?
It keeps planning, drafting and revision apart, and asks for a decision before text changes. It can also pull style traits from your samples and translate while holding on to technical terms.
Does writers-loop remember my preferences?
Only once you switch memory on yourself. Otherwise what it picked up about your style lasts for the session, and learning draws on decisions you actually reviewed.
Source text
writers-loop · MIT
# Writer's Loop
English | [简体中文](README_zh.md) | [日本語](README_ja.md) | [Español](README_es.md)
**AI writing that learns from your style, approvals, and edits.**
**让 AI 写作根据你的风格、认可与修改持续改进。**
[](https://github.com/xxsang/writers-loop/actions/workflows/validate.yml)
[](https://hol.org/registry/plugins/writer-s-loop-contributors%2Fwriters-loop)
[](LICENSE)
[](package.json)
[](PRIVACY.md)
<p align="center">
<img src="assets/writers-loop-overview.svg" alt="Writer's Loop overview" width="720">
</p>
Writer's Loop is a portable writing skill for AI agents. It turns writing into
a reviewable loop — frame, plan, draft, critique, revise — and learns only from
style samples you provide or approve and decisions you actually review.
Use it when one-shot prompting is too fuzzy: coding plans, reports, proposals,
product specs, documentation, essays, speeches, fiction, style distillation, and
translation.
---
## One-Line Agent Setup
If you use Claude Code, Codex, Cursor, Gemini CLI, OpenCode, or another local
agent, give it this setup prompt:
```text
Help me install Writer's Loop from https://github.com/xxsang/writers-loop, then use $writers-loop for my writing task without saving preferences unless I explicitly opt in.
```
For manual installation, see [docs/installation.md](docs/installation.md).
If your agent supports repository plugins, start with the public GitHub URL:
`https://github.com/xxsang/writers-loop`.
---
## The Problem With One-Shot AI Writing
Most writing prompts collapse planning, drafting, editing, and preference
learning into one pass. The agent guesses what you want, rewrites without
asking, and forgets your decisions the moment the conversation ends.
| Problem | Writer's Loop response |
| --- | --- |
| One-shot drafts guess too much | Frame the task and plan before drafting |
| Rewrites can erase intent | Propose changes before revising |
| AI memory can become unreliable | Learn only from reviewed decisions |
| Style copying can leak private facts | Separate style traits from source content |
Writer's Loop keeps the stages separate:
| Stage | What happens |
| --- | --- |
| **Frame** | Understand the artifact, audience, goal, and constraints |
| **Ask** | Ask only questions that would materially change the result |
| **Plan** | Propose a structured plan and wait for approval |
| **Draft** | Write once the plan is locked |
| **Critique** | Evaluate the draft before touching it |
| **Propose** | Name targeted changes with reason, scope, and risk |
| **Decide** | You accept, reject, or adjust — the agent does not guess |
| **Revise** | Rewrite only what was approved |
| **Learn** | Record only reviewed decisions as reusable preferences |
Core rule:
```text
Learn from user decisions, not from raw AI drafts.
```
```mermaid
flowchart LR
A["Style samples you provide or approve"] --> D["Reviewed signals"]
B["Approved plans"] --> D
C["Accepted edits"] --> D
X["Raw AI drafts"] -. "not learned from" .-> Z["Discarded"]
D --> E["Reusable preferences"]
E --> F["Better future drafts"]
```
---
## Try It In 30 Seconds
```text
Use $writers-loop for this:
[describe the writing task]
Audience: [who will read it]
Goal: [what it should achieve]
Ask only if blocked. Otherwise make a short plan, draft, and brief critique.
Do not save preferences unless I ask.
```
For more ready-to-copy prompts, see [docs/prompt-templates.md](docs/prompt-templates.md).
---
## What You Get
A structured loop that keeps planning, drafting, and editing separate — so the
output is steerable and reviewed preferences can persist across sessions after
explicit opt-in.
Includes artifact-specific guidance for technical plans, reports, proposals,
docs, essays, speeches, and fiction; style distillation from your own samples;
translation that preserves voice and exact technical tokens; and optional
project-local memory that writes only where you approve it.
---
## Install And Agent Support
Writer's Loop is GitHub-only and public. If your agent supports repository
plugins, install from:
```text
https://github.com/xxsang/writers-loop
```
For local skill-folder installs, clone the repository, then install with the
path or plugin flow that matches your agent.
```bash
git clone https://github.com/xxsang/writers-loop.git
```
| Agent | Fast path |
| --- | --- |
| **Claude Code** | Copy `skills/writers-loop` into `~/.claude/skills/`, or use `.claude-plugin/plugin.json` |
| **OpenAI Codex CLI** | Use the plugin flow with the GitHub URL if available, or copy `skills/writers-loop` into `~/.codex/skills/` |
| **OpenAI Codex App** | Use the plugin flow with the GitHub URL if available, or copy `skills/writers-loop` into `~/.codex/skills/` and refresh skill discovery |
| **Cursor** | Use `.cursor-plugin/plugin.json`, or copy the skill folder |
| **Gemini CLI** | Run `gemini extensions install https://github.com/xxsang/writers-loop` |
| **GitHub Copilot CLI** | Point Copilot-enabled workflows at `AGENTS.md` |
| **OpenCode** | Follow `.opencode/INSTALL.md` |
| **ChatGPT / hosted agents** | Paste or attach `skills/writers-loop/SKILL.md` into project instructions |
For full per-agent steps, see [docs/installation.md](docs/installation.md).
No npm install required for normal use. `package.json` is `private: true`; Node
scripts are for validation, evals, and optional local storage tooling only.
---
## Writing Tool Templates
Writer's Loop also ships templates for writing surfaces that do not run skills
natively. These are linked from the full [writing tool integration guide](docs/writing-tools.md).
| Tool | Easy path |
| --- | --- |
| **Obsidian** | Copy `integrations/obsidian/templates/` into your vault's template folder |
| **Logseq** | Copy `integrations/logseq/templates/writers-loop.md` into a template page |
| **Notion** | Paste `integrations/notion/writers-loop-page-template.md` into a page |
| **Feishu / Lark Docs** | Paste or create `integrations/feishu/writers-loop-doc-template.md` |
| **ChatGPT / Claude Projects** | Paste the project instructions and attach the listed Writer's Loop references |
Obsidian quick setup:
```bash
VAULT="$HOME/Documents/Obsidian/MyVault"
mkdir -p "$VAULT/Templates/Writers Loop"
cp integrations/obsidian/templates/*.md "$VAULT/Templates/Writers Loop/"
```
Then enable Obsidian's **Templates** core plugin and set the template folder to
`Templates/Writers Loop`.
---
## Local Memory Is Opt-In
Writer's Loop works without memory. Preference learning is session-only by default.
If you opt in, tools write only inside the selected project:
```text
.writers-loop/
├── journal.jsonl
├── prefs.md
└── styles/
└── my-style.md
```
- `.writers-loop/` is never created unless you ask.
- Never commit it to public repositories.
- Only reviewed style packs are saved in `.writers-loop/styles/` — not raw source samples.
See [docs/local-preference-storage.md](docs/local-preference-storage.md) for
`style:save` and other commands, and [PRIVACY.md](PRIVACY.md) for the full policy.
---
## When Not To Use It
For tiny one-off copy edits, a simple prompt is usually enough. Writer's Loop
is for writing that benefits from structure, review, or reusable decisions.
Using an LLM for writing may also reduce the pleasure of writing — it can
compress the uncertainty, wandering, discovery, and ownership that make writing
satisfying. Use Writer's Loop as a scaffold, sparring partner, editor, or
translator. Keep the parts of writing you value doing yourself.
---
## Docs
| Need | Read |
| --- | --- |
| Quick example | [docs/demo-transcript.md](docs/demo-transcript.md) |
| Full method | [docs/writers-loop-complete-guide.md](docs/writers-loop-complete-guide.md) |
| Copyable prompts | [docs/prompt-templates.md](docs/prompt-templates.md) |
| Writing tool integrations | [docs/writing-tools.md](docs/writing-tools.md) |
| Using A Learned Style | [docs/prompt-templates.md#using-a-learned-style](docs/prompt-templates.md#using-a-learned-style) |
| Installation | [docs/installation.md](docs/installation.md) |
| Local preference storage | [docs/local-preference-storage.md](docs/local-preference-storage.md) |
| Privacy policy | [PRIVACY.md](PRIVACY.md) |
| Release checklist | [RELEASE.md](RELEASE.md) |
---
## Repository Layout
<details>
<summary>Show file tree</summary>
```text
skills/writers-loop/SKILL.md Core skill instructions
skills/writers-loop/references/ Progressive-disclosure references
skills/writers-loop/scripts/journal.mjs Optional local preference journal
skills/writers-loop/scripts/style-pack.mjs Optional local style-pack storage
docs/ User-facing guides and prompt templates
.codex-plugin/plugin.json Codex plugin metadata
.claude-plugin/plugin.json Claude plugin metadata
.cursor-plugin/plugin.json Cursor plugin metadata
gemini-extension.json Gemini extension metadata
.opencode/ OpenCode install metadata
tools/ Maintainer validation and eval scripts
```
</details>
---
## Validate
```bash
npm test
```
No install step required. Uses only Node.js built-in modules.
---
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md). Keep the skill portable, concise, and
useful across agents.
## License
MIT License. See [LICENSE](LICENSE).
Copyright (c) 2026 Writer's Loop contributors.
© Writer's Loop contributors · MIT · hashgraph-online/awesome-codex-plugins