design-big

Files (1)

• SKILL.md

SKILL.md (first lines)

# Design Big Skill

## Purpose
Create top-level architecture documents for a book project before any chapter writing starts.

This phase never writes manuscript chapters. It turns the user's actual request into a reviewable plan. The user must approve that plan through `runtime/approvals/book-plan-approval.json` before `design-small`, `create`, `polish`, `rewrite`, or `export` may proceed.

## Flow
1. Parse the actual user request from `runtime/book-request.md`.
2. Run domain research only when source artifacts will be recorded; otherwise do not claim research.
3. Orchestrate design agents:
   - concept-builder
   - character-architect
   - plot-hook-engineer
   - book-structure-optimizer
   - domain-researcher
   - research-citation-auditor
4. Run consistency merge pass.
5. Publish reader-facing plan files, machine-readable state files, and `novel-config.md`.
6. Stop for user review. Do not start chapter-range planning or manuscript writing.

## Hard Rules
- Do not use placeholder language such as `plan_required`, `to_be_confirmed`, `TBD`, `TODO`, or "fill in later".
- Every character entry must include concrete role, name, desire, fear, and arc.
- Every plot arc must include concrete opening promise, inciting incident, midpoint turn, climax, and resolution.
- Every chapter plan entry must include reader-facing title, purpose, events, character focus, continuity promises, and target words.
- Layout targets must align with target pages, target words, target chapters, trim size, font, and words-per-page estimate.
- Technical ids such as `EP001` may exist in state file ids, but reader-facing titles must not be technical labels.

## Outputs
- `design/*_bootstrap.md`
- `design/*_character.md`
- `design/*_plot-hook.md`
- `design/04_book_plan.md`
- `design/05_chapter_plan.md`
- `design/06_layout_plan.md`
- `novel-config.md`
- `revision/_state/book-plan.json`
- `revision/_state/chapter-plan.json`
- `revision/_state/layout-plan.json`
- `revision/_state/longform-plan.json`
- `revision/_state/character-state.json`
- `revision/_state/plot-ledger.json`
- `revision/_state/chapter-summaries.json`
- `revision/_state/continuity-ledger.json`
- `revision/_state/style-profile.json`
- `revision/_state/writing-type-profile.json`
- `revision/_state/genre-structure-template.json`
- `revision/_state/editorial-quality-scorecard.json`
- `revision/_state/llm-adapter-contract.json`
- `revision/_state/create-plan.json`
- `revision/_state/design-hashes.json`
- `revision/_workspace/02_domain-researcher_design-big.md`
- `revision/_workspace/02_domain-researcher_design-big.json`
- `revision/_workspace/07_research-citation-auditor_design-big.md`
- `revision/_workspace/07_research-citation-auditor_design-big.json`

## Design Freeze Contract
- `create-plan.json` must assign every chapter a target word count, min/max range, status, retry policy, and required gates.
- `design-hashes.json` must hash the approved design and state files after `novel-config.md` is written.
- If any hashed design source changes after approval, create/polish/export must stop and rewrite must first produce `revision/_workspace/rewrite-impact-report.json`.

From Anubis44197/kit_hub, Apache-2.0.

More from Anubis44197/kit_hub