Writing workflow
When to use
Use for multi-step fiction work, especially when continuing across sessions or choosing which writing specialty to apply.
Inputs and assumptions
Identify the project, current task, output format, language, audience, desired voice, and requested scope. Saved manuscript evidence takes precedence over an unsupported recollection from chat.
Portable workflow
- Read the project workflow and inspect the saved project state.
- Separate format, genre, style, and unit of work. Read format guidance and style choices only as needed.
- Choose relevant specialist skills. When the author asks to learn or the project uses beginner guidance, load beginner coaching and start with one small step. Do not apply it to every new project. Planning uses brainstorming and outlining. Drafting uses prose, the medium skill, and continuity. Revision uses critique and voice checks. Visual adaptation uses adaptation and manga guidance.
- Clarify only missing decisions that affect this deliverable. A new book starts with an agreed direction, not automatic whole-book generation. For a beginner, a rough scene idea is enough to begin practicing; a full outline is not a prerequisite.
- Complete one bounded step. Save authorized outputs, verify them, and record the next step. Stop at an author decision rather than guessing approval.
Safety and side effects
Creating and drafting can write local files. Reviewing is read-only. Preserve existing prose and keep proposed ideas separate from canon. Do not install, publish, upload, or generate images merely to run a writing workflow.
Scripts, references, and dependencies
No scripts or external services required. Specialist instructions live in sibling skill directories. The shared references define file responsibilities and medium-specific checks.
Verification
Confirm the requested scope was delivered, saved paths exist when saving was requested, the checkpoint matches the files, and unresolved choices remain visible. Do not report a reserved target as a finished chapter.
Pi adapter
Use /writer for the guided menu, /writer start for beginner help, /writer coach to learn with an existing project, /writer new book "Title" for standard setup, and /writer continue to resume. The command uses the active model and saves projects under the invoking workspace's writing/ directory. It does not need the separate workflows extension.
1---2name: writer-workflow3description: Coordinate fiction planning, drafting, continuation, revision, and adaptation using saved project files. Use for starting or resuming books, chapters, scenes, volumes, or manga projects.4license: MIT5---67# Writing workflow89## When to use1011Use for multi-step fiction work, especially when continuing across sessions or choosing which writing specialty to apply.1213## Inputs and assumptions1415Identify the project, current task, output format, language, audience, desired voice, and requested scope. Saved manuscript evidence takes precedence over an unsupported recollection from chat.1617## Portable workflow18191. Read [the project workflow](../../references/project-workflow.md) and inspect the saved project state.202. Separate format, genre, style, and unit of work. Read [format guidance](../../references/formats.md) and [style choices](../../references/styles.md) only as needed.213. Choose relevant specialist skills. When the author asks to learn or the project uses beginner guidance, load [beginner coaching](../writer-beginner/SKILL.md) and start with one small step. Do not apply it to every new project. Planning uses brainstorming and outlining. Drafting uses prose, the medium skill, and continuity. Revision uses critique and voice checks. Visual adaptation uses adaptation and manga guidance.224. Clarify only missing decisions that affect this deliverable. A new book starts with an agreed direction, not automatic whole-book generation. For a beginner, a rough scene idea is enough to begin practicing; a full outline is not a prerequisite.235. Complete one bounded step. Save authorized outputs, verify them, and record the next step. Stop at an author decision rather than guessing approval.2425## Safety and side effects2627Creating and drafting can write local files. Reviewing is read-only. Preserve existing prose and keep proposed ideas separate from canon. Do not install, publish, upload, or generate images merely to run a writing workflow.2829## Scripts, references, and dependencies3031No scripts or external services required. Specialist instructions live in sibling skill directories. The shared references define file responsibilities and medium-specific checks.3233## Verification3435Confirm the requested scope was delivered, saved paths exist when saving was requested, the checkpoint matches the files, and unresolved choices remain visible. Do not report a reserved target as a finished chapter.3637## Pi adapter3839Use `/writer` for the guided menu, `/writer start` for beginner help, `/writer coach` to learn with an existing project, `/writer new book "Title"` for standard setup, and `/writer continue` to resume. The command uses the active model and saves projects under the invoking workspace's `writing/` directory. It does not need the separate workflows extension.