A checklist tool for creating or running quality checks on planning documents and written project content. It can check outlines, characters, world-building, plot alignment, synchronized data, timelines, and writing status.

Use it to review a creative project's outline or specification, validate story content against its plan, check tracking data, inspect timelines, and assess writing readiness.

It turns broad quality concerns into specific questions or scan results. This helps find missing details, contradictions, and mismatches between plans, tracking files, and completed chapters.

checklist — Command for Claude Code by wordflowlab/novel-writer-skills

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/wordflowlab/novel-writer-skills

agentmods

npx agentmods add commands/wordflowlab/novel-writer-skills/checklist

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/wordflowlab/novel-writer-skills/checklist/github.svg)](https://agentmods.dev/commands/wordflowlab/novel-writer-skills/checklist)

Your own site

<a href="https://agentmods.dev/commands/wordflowlab/novel-writer-skills/checklist"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer-skills/checklist/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/wordflowlab/novel-writer-skills/checklist"><img src="https://agentmods.dev/badge/commands/wordflowlab/novel-writer-skills/checklist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,757 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.02757
Opus 5.5	$0.00007	$0.01103
Sonnet 5.5	$0.00003	$0.00551
Haiku 4.5	$0.00002	$0.00276

Measured 2mo ago against content hash c68dbce1a992, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

checklist scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to checklist — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

templates/commands/checklist.md · 335 lines

How it starts

The opening of the file, as written. The whole thing — 335 lines — stays where its author put it; the contents beside it link to each section on GitHub.

质量检查清单（Checklist）

生成或执行质量检查清单，支持两种模式：

🎯 支持的检查类型

第一类：规格质量检查（问题生成式）

验证规划文档本身的质量（类似"需求的单元测试"）：

大纲质量 - 检查 outline.md 的完整性、清晰度、一致性
角色设定 - 检查 spec/knowledge/characters.md
世界观 - 检查 spec/knowledge/world-setting.md 及相关文档
创作计划 - 检查 creative-plan.md / specification.md
伏笔管理 - 检查 spec/tracking/plot-tracker.json 的伏笔定义

第二类：内容验证检查（结果报告式）

扫描已写章节，验证实际内容：

世界观一致性 - 扫描章节内容，检查世界观描述矛盾
情节对齐 - 对比进度与大纲，检查情节发展
数据同步 - 验证所有 tracking JSON 文件的同步性
时间线 - 检查时间事件的逻辑连续性
写作状态 - 检查写作准备度和任务状态

用户输入

$ARGUMENTS

执行流程

1. 识别检查类型

根据用户输入，确定检查类型（规格质量 vs 内容验证）：

关键词映射：

"大纲"、"质量" → 规格质量类：大纲质量
"角色"、"设定" → 规格质量类：角色设定
"世界观" + "质量/完整性/规格" → 规格质量类：世界观
"世界观" + "一致性/检查/扫描" → 内容验证类：世界观一致性
"创作计划"、"规划" → 规格质量类：创作计划
"伏笔" → 规格质量类：伏笔管理
"情节"、"对齐"、"进度" → 内容验证类：情节对齐
"数据"、"同步"、"一致性" → 内容验证类：数据同步
"时间线"、"时间" → 内容验证类：时间线
"写作状态"、"准备" → 内容验证类：写作状态

如果用户输入不明确，询问选择。

2. 执行对应的检查逻辑

规格质量类检查（生成问题式 Checklist）

执行类似 spec-kit 的需求质量验证逻辑：

2.1 大纲质量检查

目标：验证 outline.md 是否具备良好的完整性、清晰度和一致性。

读取文件：

outline.md 或 stories/*/outline.md
spec/tracking/plot-tracker.json（如果存在）

生成检查项维度：

完整性 (Completeness)：

是否为每个主要情节节点定义了触发条件和结果？
是否明确每个卷/章的故事目标？
是否覆盖所有主要角色的成长弧？
是否定义了主要冲突的升级路径？
是否明确故事的高潮和结局？

清晰度 (Clarity)：

情节节点的触发条件是否具体可验证？
章节分配是否有明确的依据（如字数、情节密度）？
角色动机是否用具体事件量化？
场景描述是否避免模糊词汇（"某个地方"、"一段时间"）？

一致性 (Consistency)：

情节线索前后是否矛盾？
角色行为是否符合设定？
时间跨度是否合理？
世界观规则是否与大纲描述一致？

可测量性 (Measurability)：

章节分配是否合理可行（如每章2000-4000字）？
伏笔回收时机是否明确（章节号或章节范围）？
角色成长是否有明确的里程碑？

覆盖范围 (Coverage)：

是否考虑了所有主要场景类型（冲突、日常、转折）？
是否覆盖了所有主要角色的戏份？
是否包含必要的伏笔铺设和回收？

输出格式示例：

# 大纲质量检查清单
**创建时间**: 2025-10-11
**检查对象**: outline.md
**检查维度**: 完整性、清晰度、一致性、可测量性、覆盖范围

## 完整性 (Completeness)

- [ ] CHK001 是否为每个主要情节节点定义了触发条件和结果？ [Spec §大纲3.2]
- [ ] CHK002 是否明确每个卷/章的故事目标？ [Gap]
- [ ] CHK003 是否覆盖所有主要角色的成长弧？ [Spec §大纲5.1]

## 清晰度 (Clarity)

- [ ] CHK004 情节节点的触发条件是否具体可验证？ [Ambiguity, Spec §大纲3.2]
- [ ] CHK005 章节分配是否有明确的依据？ [Clarity]

## 一致性 (Consistency)

- [ ] CHK006 情节线索前后是否矛盾？ [Consistency]
- [ ] CHK007 世界观规则是否与大纲描述一致？ [Consistency, vs §世界观]

## 可测量性 (Measurability)

- [ ] CHK008 章节分配是否合理可行（如每章2000-4000字）？ [Measurability]
- [ ] CHK009 伏笔回收时机是否明确（章节号或范围）？ [Gap]

## 覆盖范围 (Coverage)

- [ ] CHK010 是否考虑了所有主要场景类型？ [Coverage]
- [ ] CHK011 是否包含必要的伏笔铺设和回收？ [Coverage, Gap]

## 使用说明

勾选已验证项：`[x]`
标记问题项：`[!]` 并在下方记录具体问题

Read the full file on GitHub · 335 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 335 lines · 17 tokens per session scan A c68dbce1a992

Subscribe to this mod's changes

checklist is a command published in the GitHub repository wordflowlab/novel-writer-skills (271 stars, last pushed 1y ago), licensed MIT. It adds 17 tokens to every session and 2,757 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to checklist, differing in 0 lines, and is treated as a copy.

Writing and docs

checklist next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
checklistwordflowlab/novel-writer-skills	Command	271	1y ago	MIT	A	17	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code