Draft Initialization

Initialize a new draft cycle under drafts/###-kebab-case-name/ using the standard artifact stages.

When To Use

• •Create a new draft folder and scaffold artifacts
• •Turn an idea into a plan, then into tasks
• •Break down a rewrite or story change into atomic tasks

Draft Folder Shape

drafts/###-kebab-case-name/
├── idea.md
├── clarify.md
├── plan.md
├── tasks.md
├── analyze.md
└── feedback.md

Use drafts/_template/ as the reference layout.

Stage 1: idea.md (Intent Spec)

Required sections:

• •Intent Summary (3–5 sentences: WHAT and WHY)
• •Motivation (why now)
• •Scope (episodes/scenes/elements affected)
• •Desired Outcome (what success looks like)

Rules:

• •No prose writing
• •No solutions yet; just intent

Stage 2: Clarify Gate

Ask up to 5 questions, prioritized by impact:

1. •Scope boundaries
2. •Intended outcome / reader effect
3. •Non-negotiables (constraints)
4. •Continuity constraints (time/place/who knows what)
5. •Format constraints (episode/chapter structure)

If no questions are needed, say why (1–3 bullets).

Stage 3: plan.md (Blueprint)

Plan should include:

• •Element changes (elements/**)
• •Content changes (content/**)
• •File operations (create/rename/delete)
• •Sequence of work (dependency-aware)
• •Risks / ambiguity flagged as [NEEDS CLARIFICATION: ...]

Before planning, check:

• •elements/checklist.md
• •elements/pov.md, elements/tone.md
• •voice/style.md, voice/format.md

Stage 4: tasks.md (Atomic Tasks)

Every task MUST use this exact format:

- [ ] **T###: [Task Name]** — [Brief description]
  - **Files/Directories Affected:** [list]
  - **Action:** [what to do]
  - **Acceptance Criteria:**
    - [ ] [criterion 1]
    - [ ] [criterion 2]
  - **Dependencies:** [task IDs] | None

Include at least one QA task at the end (continuity + checklist compliance across touched files).

Output

When used in a prompt-run, output ONLY the updated artifact file section:

### drafts/<current-draft-folder>/<file>.md