rewrite

Rewrite episodes to align with updated design documents using a 3-phase workflow.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/JaesikYun-jax/ai-breeder-game --skill rewrite-jaesikyun-jax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rewrite
Source: https://github.com/JaesikYun-jax/ai-breeder-game/tree/main/.claude/skills/rewrite
Command: npx skills add https://github.com/JaesikYun-jax/ai-breeder-game --skill rewrite-jaesikyun-jax

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Rewrite transforms existing episodes to align with updated design documents.

Core Features & Use Cases

  • Automated 3-Phase rewrite workflow: analysis, rewrite, and verification to ensure episode consistency with design docs.
  • Project-wide scope: supports EP range selection, batch processing, and cross-episode validation.
  • Rigorous reporting: generates rewrite-plan.md and rewrite-log.md to track progress and changes.

Quick Start

Run the /rewrite command to begin processing the next unfinished episode.

Frequently Asked Questions about rewrite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate rewriting existing story episodes to match updated design documents?

To automate episode rewriting, the Skill applies a structured 3-phase workflow—analyze, rewrite, and verify—transforming existing episodes to align with updated design documents while enforcing cross-episode validation.

Can I batch process a range of episodes for rewriting at once?

Yes, episode rewriting supports project-wide scope with EP range selection, allowing you to batch process multiple episodes using parallel analysis and sequential rewriting across multi-phase workflows.

How does cross-episode validation work during the episode rewrite process?

Cross-episode validation occurs during the verification phase of the rewrite workflow, checking transformed episodes against updated design documents and guard rails to ensure narrative consistency across the entire project scope.

Do I need a configuration file to start batch rewriting story episodes?

Yes, episode rewriting integrates with novel-config.md and established guard rails to enforce design document alignment, requiring these configuration files before processing begins.

What reports are generated when I transform episodes to align with new design docs?

Episode rewriting generates rewrite-plan.md to track intended changes and rewrite-log.md to document progress and results, providing rigorous reporting throughout the transformation workflow.

What's the best way to handle episode consistency when design documents change mid-project?

To maintain episode consistency after design changes, use an automated rewrite workflow that sequentially processes affected episode ranges, validates cross-episode alignment, and logs all transformations to structured markdown reports.