Audit a project against current plugin conventions and offer to update structure.
Audits fiction writing projects against current conventions and offers to scaffold missing structure and content.
/plugin marketplace add howells/fiction/plugin install fiction@howellsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Reconcile an existing fiction project with the current plugin conventions. This audits your project structure, identifies gaps or outdated patterns, and offers to scaffold missing sections.
Use this when:
Same as /load — look for README.md, chapters/, characters/ directories.
Check for expected directories and files:
Required:
README.md — Project overviewchapters/ — Chapter filesRecommended:
characters/ — Character documentsworld/ — World/setting documentscraft/tone.md — Voice guidancethemes.md — Thematic contentBuild & Cover:
builds/ — EPUB build outputs (date-organized)covers/ — Cover artwork iterationscritiques/ — Critique outputs (date-organized)synopses/ — Synopsis outputs (date-organized)epub.css — EPUB styling (if building)For each existing file, check for expected sections:
README.md should have:
## Anchored — Immutable constraints (new convention)## Key Decisions — Tracked decisions## Status — Project status## Chapters — Chapter listcraft/tone.md should have:
## Language & Style — English variant, style guide, dialogue quotes, serial comma, dash style## Voice — How the story sounds## POV — Perspective, tense, distanceCharacter files should have:
For series projects, also check:
series-architecture.md with ## Anchored sectionOutput a reconciliation report:
## Reconciliation Report: [Project Name]
### Structure Status
- README.md exists
- chapters/ directory (X chapters)
- characters/ directory (X characters)
- craft/tone.md — missing
- themes.md exists
- builds/ — missing (create with `/fiction:build`)
- covers/ — missing (create for cover artwork)
- critiques/ — missing (create with `/fiction:critique`)
- synopses/ — missing (create with `/fiction:synopsis`)
### Content Audit
**README.md**
- Missing `## Anchored` section (new convention)
- Has `## Key Decisions`
- Has `## Status`
**Character: [Name]**
- Has Want/Need
- Missing Voice notes
[...continue for each file...]
### Recommendations
1. **High priority:** Add `## Anchored` section to README.md
2. **Medium priority:** Create craft/tone.md for voice consistency
3. **Low priority:** Add Voice notes to character files
### Would you like me to:
- [ ] Add missing sections to existing files (safe — adds, doesn't replace)
- [ ] Scaffold missing files from templates
- [ ] Both
After auditing, update (or create) progress.md with:
## Last Reconcile
**Date:** [Today's date]
**Plugin version:** [Current version if known]
**Issues found:** [Count]
**Issues resolved:** [Count of auto-fixed items]
Also update:
If user approves:
Important: Never overwrite existing content. Only add missing sections.
/fiction:reconcile # Reconcile project in current directory
/fiction:reconcile --apply # Auto-apply safe changes without prompting
/fiction:reconcile --report # Report only, don't offer changes
If arguments provided: $ARGUMENTS
## Anchored sections for immutable constraints## Language & Style section in craft/tone.md declaring English variant and style guide (Chicago Manual of Style or New Oxford Style Manual)Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.