메뉴
Manage multi-level novel revisions while preventing cascade problems. Use when editing novels, when changes at one level break things at others, when you need systematic change management for long-form fiction, or when revisions keep creating new problems.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | novel-revision |
| description | Manage multi-level novel revisions while preventing cascade problems. Use when editing novels, when changes at one level break things at others, when you need systematic change management for long-form fiction, or when revisions keep creating new problems. |
| license | MIT |
| metadata | {"author":"jwynia","version":"1.0","type":"diagnostic","mode":"diagnostic+assistive","domain":"fiction"} |
You help writers manage revisions across multiple levels of abstraction while preventing unintended consequences from cascading through the narrative. Your role is to implement systematic change management that maintains story coherence.
Any change at one level potentially affects all other levels. Changes propagate both upward (prose discoveries revealing structural problems) and downward (structural changes requiring prose rewrites).
Every novel operates simultaneously across these levels:
Before implementing any revision:
For each proposed change, document:
Define warning signs that indicate problems:
Triggers: Character feels flat, motivations unclear, arc incomplete
Protocol:
Monitoring: Does behavior remain believable? Do others respond appropriately?
Triggers: Pacing off, events disconnected, climax lacks impact
Protocol:
Monitoring: Does tension build? Do plot points feel connected and inevitable?
Triggers: Theme heavy-handed, unclear, or inconsistent
Protocol:
Monitoring: Do themes emerge naturally? Does resolution feel thematically satisfying?
| Warning Sign | What It Indicates |
|---|---|
| Character acts against personality without development | Consistency break |
| Events don't follow logically | Plot logic gap |
| Scenes feel rushed or drag unexpectedly | Pacing anomaly |
| Story events undermine themes | Thematic drift |
# Revision: [Brief Description]
## Change Type
- [ ] Conceptual - [ ] Structural - [ ] Prose
## Rationale
[Why this change is needed]
## Predicted Consequences
- Immediate (1-2 chapters):
- Medium-term (3-5 chapters):
- Story-wide:
## Monitoring Criteria
- Warning sign 1:
- Warning sign 2:
- Success indicator 1:
- Success indicator 2:
## Implementation Status
- [ ] Initial change complete
- [ ] Cascade tasks identified
- [ ] Cascade tasks completed
- [ ] Validation complete
## Outcome Assessment
[Complete after implementation]
When working with multiple agents on revision:
When revision feels stuck:
context/output-config.md in the projectrevision/ or explorations/revision/Pattern: {novel-name}-revision-{date}.md
context/output-config.md{novel-name}-revision-{date}.mdTrigger phrases: "coordinate all revisions", "map full cascade", "plan the rollback"
| Task | Agent Type | When to Spawn |
|---|---|---|
| Consistency check | Explore | When verifying changes across manuscript |
| Character tracking | general-purpose | When monitoring character consistency |
Pattern: Making revisions without first analyzing what else might be affected—jumping straight to implementation. Why it fails: Changes cascade. A character motivation change affects every scene where that character makes choices. Unassessed changes create problems you discover pages later, often after you've built on broken foundation. Fix: Before every significant change, explicitly document: what must change as a result? What might break? Set monitoring criteria before implementation, not after.
Pattern: Noticing that something feels off after a change but pushing forward anyway, trusting it will resolve itself. Why it fails: Early warnings are cheap signals about expensive problems. Characters acting against established personality, plot logic gaps, pacing anomalies—these compound. The deeper you go, the more expensive the fix. Fix: Treat early warnings as actionable information. Stop, evaluate, decide to either fix now or explicitly accept the risk. Don't let "I'll fix it later" accumulate.
Pattern: Making changes without tracking the secondary edits they require—accumulating a backlog of unaddressed implications. Why it fails: Untracked cascade tasks become invisible technical debt. You think you made one change; you actually made one change and created ten unfixed inconsistencies. Fix: Maintain explicit cascade task lists. When a change requires follow-up edits, write them down immediately. Track completion. Don't move on until cascade is resolved.
Pattern: Continuing with a problematic change because you've already invested significant effort, even when warning signs multiply. Why it fails: The effort is gone either way. Continuing down a broken path just adds more lost effort. Multiple warning signs within two chapters usually indicate fundamental problems. Fix: Define rollback triggers before implementation. When triggers fire, roll back. Document what you learned. The insight is valuable even if the change wasn't.
Pattern: Measuring progress by pages revised rather than by improvement achieved—conflating work with results. Why it fails: You can revise extensively without making the story better. In fact, you can revise extensively and make it worse. Activity that doesn't serve story goals is waste. Fix: Define what "better" means for each revision pass. Measure against that goal, not against pages touched. Sometimes the best revision is no revision.
| Skill | What it provides |
|---|---|
| story-sense | Diagnosis of what needs revision |
| character-arc | Character consistency requirements |
| scene-sequencing | Pacing and structure requirements |
| Skill | What this provides |
|---|---|
| prose-style | Manuscript-level changes with cascade awareness |
| revision | Scene-level work with multi-level coordination |
| (completed novel) | Final product with maintained coherence |
| Skill | Relationship |
|---|---|
| story-sense | Story-sense diagnoses problems; novel-revision manages the fix without creating new problems |
| revision | Revision handles sentence and scene level; novel-revision coordinates across the whole manuscript |
Search the web using Brave Search API for fast, privacy-respecting results with localization, freshness filtering, and extra snippets. Use when you need web search results with country/language targeting or time-based filtering. Requires BRAVE_API_KEY. Keywords: brave, web search, localized search, privacy search, freshness filtering.
Build and publish npm packages using Bun as the primary toolchain with npm-compatible output. Use when the user wants to create a new npm library, set up a TypeScript package for publishing, configure build/test/lint tooling for a package, fix CJS/ESM interop issues, or publish to npm. Covers scaffolding, strict TypeScript, Biome + ESLint linting, Vitest testing, Bunup bundling, and publishing workflows. Keywords: npm, package, library, publish, bun, bunup, esm, cjs, exports, typescript, biome, vitest, changesets.
Build and publish npx-executable CLI tools using Bun as the primary toolchain with npm-compatible output. Use when the user wants to create a new CLI tool, set up a command-line package for npx execution, configure argument parsing and terminal output, or publish a CLI to npm. Covers scaffolding, citty arg parsing, sub-commands, terminal UX, strict TypeScript, Biome + ESLint linting, Vitest testing, Bunup bundling, and publishing workflows. Keywords: npx, cli, command-line, binary, bin, tool, bun, citty, commander, terminal, publish, typescript, biome, vitest.
Integrate installed skill usage guidance into project CLAUDE.md/AGENTS.md based on project context. Use when skills are installed but agents don't know when to use them, when setting up a new project with skills, or when updating guidance after adding skills.
Synthesize new works from extracted functional DNA documents. Use when adapting a source work to a new context, when combining multiple source extractions, or when generating variations that preserve function while changing form.
Diagnose book marketing copy problems and generate platform-optimized blurbs, descriptions, taglines, and query pitches. Use when marketing copy feels weak, when descriptions aren't converting, or when starting marketing from scratch.