Mandatory Pre-Writing Checklist

Core Features

Solves AI Focus Degradation in Long Novels - This is the core innovation of Novel Writer Skills v1.0.

Root Cause of the Problem

User Feedback: When creating works with novel-writer, the first 30 chapters are of high quality, but after chapter 30, the AI starts to:

Forget previous settings
Have inconsistent character personalities
Repeat or contradict plot points
Ignore the principles of the Writing Constitution

Fundamental Reason: Long conversations cause the AI to forget early context, even if specification.md is written in extreme detail.

Solution

Mandatory re-reading of all key files before each writing session → AI reloads complete context → Maintains consistency

9-Item Mandatory Checklist

Each time the

/write

command is executed, this checklist must be completed first:

markdown

📋 Mandatory Pre-Writing Checklist (Must Complete):

✓ 1. memory/constitution.md - Writing Constitution
✓ 2. memory/style-reference.md - Style Reference (if applicable)
✓ 3. stories/_/specification.md - Story Specification
✓ 4. stories/_/creative-plan.md - Creative Plan
✓ 5. stories/\*/tasks.md - Current Tasks
✓ 6. spec/tracking/character-state.json - Character State
✓ 7. spec/tracking/relationships.json - Relationship Network
✓ 8. spec/tracking/plot-tracker.json - Plot Tracker (if applicable)
✓ 9. spec/tracking/validation-rules.json - Validation Rules (if applicable)

📊 Context Loading Status: ✅ Completed

How It Works

Automatic Trigger Timing

User executes the
/write
command
This Skill activates automatically
Enforces the checklist
Outputs confirmation report
Begins writing only after completion

Execution Flow

User: /write Chapter 10

         ↓

[pre-write-checklist activates automatically]

         ↓

Step 1: Read memory/constitution.md
Step 2: Read memory/style-reference.md (if exists)
Step 3: Read stories/*/specification.md
Step 4: Read stories/*/creative-plan.md
Step 5: Read stories/*/tasks.md
Step 6: Read spec/tracking/character-state.json
Step 7: Read spec/tracking/relationships.json
Step 8: Read spec/tracking/plot-tracker.json (if exists)
Step 9: Read spec/tracking/validation-rules.json (if exists)

         ↓

Output Confirmation:
📋 Mandatory Pre-Writing Checklist (Completed):
✓ All 9 files have been read
📊 Context Loading Status: ✅ Completed

Key Information Summary:
- Writing Principles: [Extracted from constitution]
- Current Tasks: [Extracted from tasks.md]
- Main Characters: [Extracted from character-state]
- Plot Progress: [Extracted from plot-tracker]

         ↓

Start writing Chapter 10...

Output Formats

Standard Output (All Files Exist)

markdown

📋 Mandatory Pre-Writing Checklist (Completed):

✓ 1. memory/constitution.md - Writing Constitution
→ Core Principles: [List 2-3 key principles]

✓ 2. memory/style-reference.md - Style Reference
→ Style Key Points: [Extract key style requirements]

✓ 3. stories/xxx/specification.md - Story Specification
→ Story Genre: [Romance/Suspense/History, etc.]
→ P0 Elements: [Mandatory elements to include]

✓ 4. stories/xxx/creative-plan.md - Creative Plan
→ Current Phase: [Volume X/Chapter X]
→ Chapter Goal: [Plot/Emotional Goal]

✓ 5. stories/xxx/tasks.md - Current Tasks
→ Chapter to Write: [Chapter X]
→ Task Status: [pending/in_progress]

✓ 6. spec/tracking/character-state.json - Character State
→ Main Characters: [List character names and current states]

✓ 7. spec/tracking/relationships.json - Relationship Network
→ Core Relationships: [Relationship changes between protagonist and others]

✓ 8. spec/tracking/plot-tracker.json - Plot Tracker
→ Active Plot Threads: [Current ongoing plot lines]

✓ 9. spec/tracking/validation-rules.json - Validation Rules
→ Auto-Fix: [Enabled/Disabled]

📊 Context Loading Status: ✅ Completed (Loaded 9 files, approximately XXXX tokens)

🎯 Ready to write Chapter X...

When Some Files Are Missing

markdown

📋 Mandatory Pre-Writing Checklist (Partially Completed):

✓ 1. memory/constitution.md - Writing Constitution
✓ 2. ⚠️ memory/style-reference.md - Does not exist (optional file, skipped)
✓ 3. stories/xxx/specification.md - Story Specification
✓ 4. stories/xxx/creative-plan.md - Creative Plan
✓ 5. stories/xxx/tasks.md - Current Tasks
✓ 6. spec/tracking/character-state.json - Character State
✓ 7. spec/tracking/relationships.json - Relationship Network
✓ 8. ⚠️ spec/tracking/plot-tracker.json - Does not exist (optional file, skipped)
✓ 9. ⚠️ spec/tracking/validation-rules.json - Does not exist (optional file, skipped)

📊 Context Loading Status: ✅ Completed (Loaded 6 mandatory files + 0 optional files)

💡 Recommendation: Run `/track-init` to initialize the complete tracking system

When Critical Files Are Missing (Blocks Writing)

markdown

📋 Mandatory Pre-Writing Checklist (Failed):

✓ 1. memory/constitution.md - Writing Constitution
✓ 2. memory/style-reference.md - Style Reference
❌ 3. stories/xxx/specification.md - **File does not exist**
❌ 4. stories/xxx/creative-plan.md - **File does not exist**
❌ 5. stories/xxx/tasks.md - **File does not exist**

⛔ Error: Missing mandatory files, cannot continue writing

Must complete the following first:

1. Run `/constitution` to create a Writing Constitution
2. Run `/specify` to define story specifications
3. Run `/plan` to develop a creative plan
4. Run `/tasks` to break down the task list

Then you can execute `/write`

This is the recommended workflow of the seven-step methodology.

Integration with Commands

/write

Command

Must execute checklist first before writing:

yaml

Execution Order:
1. pre-write-checklist (this Skill) → Read all files
2. Output confirmation report
3. Check setting-detector → Whether to activate knowledge base
4. Start actual writing

/analyze

Command

It is recommended to execute the checklist during analysis:

yaml

Ensure complete context before analysis:
1. pre-write-checklist → Reload all files
2. Execute analysis based on the latest status

/track

Command

Trigger checklist after tracking updates:

yaml

Update Workflow:
1. User modifies tracking files
2. Run `/track` to update
3. pre-write-checklist → Re-read and validate

File Importance Classification

Mandatory Files (Blocks Writing if Missing)

1. memory/constitution.md - Writing Principles
3. stories/*/specification.md - Story Specifications
4. stories/*/creative-plan.md - Creative Plan
5. stories/*/tasks.md - Current Tasks
6. spec/tracking/character-state.json - Character State
7. spec/tracking/relationships.json - Relationship Network

Logic: Without these files, the AI does not know:

What principles to follow
What the story is about
Where the current writing stands
Who the characters are and their states

Optional Files (Warns but Allows Continuation if Missing)

2. memory/style-reference.md - Style Reference
8. spec/tracking/plot-tracker.json - Plot Tracker
9. spec/tracking/validation-rules.json - Validation Rules

Logic: These files enhance quality but are not minimum requirements:

style-reference: Not used by some users / book-internalize
plot-tracker: May not be needed for simple stories
validation-rules: Non-mandatory automation

Anti-Focus-Degradation Mechanism

Problem Scenarios

Writing Chapter 1:
- AI remembers all settings
- High quality

Writing Chapter 10:
- Conversation has become very long
- AI starts to forget Chapter 1 settings

Writing Chapter 30:
- Completely forgets early settings
- Character personalities deviate
- Plot contradicts itself

Solution Mechanism

Before each writing session:
- Mandatory re-reading of all core files
- Reload complete context
- Treat Chapter 30 like Chapter 1

Results:
- Quality of Chapter 30 ≈ Quality of Chapter 1
- Consistency maintained
- No more focus degradation

Effect Comparison

Comparison Dimension	Without Checklist	With Checklist
Chapters 1-10	✓ High quality	✓ High quality
Chapters 11-30	⚠️ Starts to be unstable	✓ Remains stable
Chapters 31-50	❌ Obvious focus degradation	✓ Still stable
Chapters 51+	❌ Severe focus degradation	✓ Long-term stability

Configuration Options

Adjust Strictness

Default: Strict Mode (Recommended)

"Use strict checklist mode"
→ Blocks writing if mandatory files are missing

Lenient Mode (Not Recommended)

"Use lenient checklist mode"
→ Allows skipping some files (not recommended, may cause focus degradation)

Customize Checklist Items

If you have additional important files:

"Please add the following to the checklist:
- spec/knowledge/worldbuilding/magic-system.md
- spec/knowledge/characters/protagonist-profile.md"

Performance Optimization

Token Consumption

Additional token cost per writing session:

Reading 9 files:
- constitution.md: ~200 tokens
- specification.md: ~500 tokens
- creative-plan.md: ~300 tokens
- tasks.md: ~150 tokens
- character-state.json: ~200 tokens
- relationships.json: ~150 tokens
- Others: ~200 tokens

Total: Approximately 1700 tokens per writing session

Benefits:
- Avoids rewrites caused by focus degradation (saves tens of thousands of tokens)
- Maintains consistent quality (user satisfaction)
- Sustainability of long-form projects

ROI is extremely high: 1700 tokens for long-term stable quality.

Caching Strategy

Within the same writing session:
1st writing: Read all files (1700 tokens)
2nd writing (within 1 hour): Check if files have been modified
- Not modified: Use cache (0 tokens)
- Modified: Re-read (partial tokens)

Frequently Asked Questions

Q: Will reading so many files every time slow down writing?

A: No.

File reading is fast (milliseconds)
Token consumption is reasonable (~1700 tokens)
The trade-off is long-term quality assurance

Comparison:

Without checklist: Chapter 30 quality is poor → User requests 10 rewrites → Wastes tens of thousands of tokens
With checklist: +1700 tokens per chapter → 50 chapters only +85000 tokens → But quality remains stable

Q: Can I skip the checklist?

A: Technically yes, but strongly not recommended.

"Skip checklist and write directly"
→ AI will warn: "Not recommended, may cause focus degradation"
→ But will respect your choice

At your own risk: Don't say you weren't warned if focus degrades after 30 chapters 😊

Q: What if I really don't have some files?

A: Two scenarios:

Missing mandatory files (constitution, specification, etc.): → Blocks writing, prompts to run corresponding commands to create them first

Missing optional files (style-reference, plot-tracker): → Warns but allows continuation, recommends creating them later

Q: What is the relationship between the checklist and setting-detector?

A: They work complementarily:

pre-write-checklist:
- Loads project-specific files (your story data)

setting-detector:
- Loads general knowledge bases (genre conventions, writing techniques)

Combined = Complete context:
Your story settings + genre expertise

Q: Do I need to read all files every time for a 100-chapter long novel?

A: Yes, and it's even more necessary.

Challenges of long novels:
- More complex settings
- More characters
- More plot threads
- AI is more likely to forget

Role of the checklist:
- Ensures Chapter 100 has the same quality as Chapter 1
- Prevents sudden character personality changes
- Prevents plot contradictions

This is the cornerstone of quality assurance for long novels.

Best Practices

1. Keep Files Updated

The checklist only ensures the AI reads files, but file content must be accurate:

✓ Character state changes → Update character-state.json
✓ Relationship changes → Update relationships.json
✓ New plot threads → Update plot-tracker.json

2. Run

/track

Regularly

Recommended frequency: Run `/track` every 5-10 chapters
Purpose:
- Update tracking files
- Validate consistency
- Detect potential issues

3. Manually Trigger After Important Changes

If you manually modify key files:
"Please re-execute the checklist to reload all files"

Ensure the AI sees the latest status.

4.配合consistency-checker配合

pre-write-checklist (before writing):
- Loads all context
- Prepares for writing

consistency-checker (during/after writing):
- Monitors consistency
- Detects contradictions

Double protection = Highest quality.

Technical Implementation

File Reading Order

Priority Order (Most Important First):
1. constitution (highest principles)
2. specification (story core)
3. creative-plan (technical plan)
4. tasks (current tasks)
5. character-state (character data)
6. relationships (relationship data)
7. plot-tracker (plot tracking)
8. validation-rules (validation rules)
9. style-reference (style reference)

Error Handling

File does not exist:
→ Mandatory files: Blocks writing, prompts creation
→ Optional files: Warns, allows continuation

File format error:
→ JSON parsing failed: Display error, recommend fixing
→ Markdown format issue: Try to read as much as possible, mark the problem

File too large:
→ Exceeds 10000 lines: Warns (may affect performance)
→ Recommend splitting the file

Summary

pre-write-checklist is the core innovation of Novel Writer Skills v1.0:

✓ Solves AI focus degradation in long novels ✓ Mandatory re-reading of key files ✓ Ensures context completeness ✓ Maintains long-term quality stability ✓ Suitable for professional authors creating long-form works

No focus degradation after 30 chapters = Long-term competitiveness 🎯

This Skill Version: v1.0 Last Updated: 2025-10-18 Core Problem: Solves AI focus degradation after 30 chapters Compatible With: write.md, setting-detector, consistency-checker

pre-write-checklist

NPX Install

Tags

SKILL.md Content (Chinese)

Mandatory Pre-Writing Checklist

Core Features

Root Cause of the Problem

Solution

9-Item Mandatory Checklist

How It Works

Automatic Trigger Timing

Execution Flow

Output Formats

Standard Output (All Files Exist)

When Some Files Are Missing

When Critical Files Are Missing (Blocks Writing)

Integration with Commands

/write Command

/analyze Command

/track Command

File Importance Classification

Mandatory Files (Blocks Writing if Missing)

Optional Files (Warns but Allows Continuation if Missing)

Anti-Focus-Degradation Mechanism

Problem Scenarios

Solution Mechanism

Effect Comparison

Configuration Options

Adjust Strictness

Customize Checklist Items

Performance Optimization

Token Consumption

Caching Strategy

Frequently Asked Questions

Q: Will reading so many files every time slow down writing?

Q: Can I skip the checklist?

Q: What if I really don't have some files?

Q: What is the relationship between the checklist and setting-detector?

Q: Do I need to read all files every time for a 100-chapter long novel?

Best Practices

1. Keep Files Updated

2. Run /track Regularly

3. Manually Trigger After Important Changes

4.配合consistency-checker配合

Technical Implementation

File Reading Order

Error Handling

Summary

`/write`
Command

`/analyze`
Command

`/track`
Command

2. Run
`/track`
Regularly