workflow-guide_skill
- Shell
91
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill wordflowlab/novel-writer-skills --skill workflow-guide- SKILL.md10.1 KB
Overview
This skill guides authors through a seven-step novel-writing workflow designed to organize idea-to-first-draft work. It activates automatically when you say you want to write a novel and stays active to keep you on track. The workflow turns creative intent into concrete specifications, plans, tasks, writing sessions, and quality checks. It integrates contextual writing skills as needed.
How this skill works
The guide walks you through seven commands: /constitution, /specify, /clarify, /plan, /tasks, /write, and /analyze. Each command produces structured outputs—principles, story specs, clarified decisions, chapter plans, prioritized tasks, AI-assisted drafting, and periodic quality analysis. The skill monitors progress, suggests which other skills to activate (e.g., dialogue or worldbuilding), and reminds you if you skip essential steps.
When to use it
- Starting a new novel project and needing a reproducible workflow
- Converting an existing outline into a machine-readable specification
- Breaking a large manuscript into prioritized, actionable work
- Maintaining consistency across long-form or serialized fiction
- Running periodic quality checks after every few chapters
Best practices
- Begin with /constitution to lock core principles that guide all decisions
- Use /specify to create a one-sentence logline, target reader, core conflict, and success metrics
- Run /clarify early to resolve up to five fuzzy points before planning
- Design chapter-level plans with /plan, then convert them to prioritized tasks via /tasks
- Write in focused sessions with /write and run /analyze every 3–5 chapters
Example use cases
- Short story: use a condensed flow /specify → /clarify → /write → /analyze for a 1–2 day sprint
- Mid-length novel: follow the full seven-step flow for a 2–6 month schedule
- Long serialized work: iterate plan → tasks → write → analyze to preserve consistency across volumes
- Import an existing outline into /specify to enable automated tracking and downstream tools
- Quick NaNoWriMo sprint: fast-track constitution/specify/plan then heavy /write sessions with frequent /analyze checks
FAQ
No. Import your outline into /specify to convert it into the workflow format, then use /clarify and /plan where needed. Minimal workable flow: /constitution → /specify → /write.
Can I skip steps and just start writing?
You can, but skipping /specify and /plan increases the risk of inconsistency and heavyweight revisions. The skill will gently remind you and offer to run the missing setup commands.
How often should I run analysis?
Run /analyze after the first three chapters for early validation, then every 3–5 chapters and once more after the full draft to catch structural or consistency issues.
