getting-started_skill

This skill guides new users through the seven-step novel creation method, offering prompts, explanations, and orderly progression from idea to draft.
  • 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 getting-started

  • SKILL.md4.8 KB

Overview

This skill activates when you start a new novel project and guides you through a seven-step methodology from idea to analysis. It offers gentle prompts, concise explanations, and direct commands to move you step-by-step. The goal is to remove startup friction and keep your creative work aligned and actionable.

How this skill works

When you indicate you want to write a novel or start a project, the skill presents a welcome flow that maps the seven steps (constitution → specify → clarify → plan → tasks → write → analyze). Each step includes targeted prompts, required inputs, and a command to proceed. You can follow the recommended order or jump steps when appropriate; the skill remembers context and enforces the guiding principles you set.

When to use it

  • When you decide to begin a new novel and need a structured onboarding
  • If you feel overwhelmed and want a clear, repeatable workflow
  • When you need to define creative boundaries and technical specs before writing
  • To convert a vague idea into an actionable plan and task list
  • When you want periodic quality checks and consistency analysis during drafting

Best practices

  • Start with /constitution to define core values, standards, and red lines
  • Use /specify to lock down genre, audience, length, and must-have elements
  • Let /clarify run five focused questions to remove major ambiguities early
  • Turn the plan into discrete tasks and track status (pending/in_progress/completed)
  • Run /analyze regularly after writing sessions to catch structural or consistency issues

Example use cases

  • A first-time novelist who needs a guided roadmap and guardrails
  • An experienced writer wanting to standardize project setup across multiple books
  • A short-story author who wants a quick specification and task breakdown
  • A team coordinating on a serialized novel, using tasks to split chapters
  • A writer iterating on drafts who uses analyze to find cohesion problems

FAQ

Recommended but not mandatory. The sequence reduces rework; experienced authors can skip /clarify or simplify /plan for short projects.

How long does the whole setup take?

Depends on complexity: simple projects can complete steps 1–5 in a few hours; complex novels may take one to two days for initial setup, with writing spanning months.

Can I change specifications or the plan later?

Yes. Update your specification or plan at any time; tasks and subsequent writing should be re-synced and re-analyzed to stay consistent.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational