plugins/lyra-creative-writing/skills/using-creative-writing/SKILL.md
Use when the user wants to draft fiction or creative nonfiction prose, get craft critique on prose they have written, or plan story structure, outline, or premise. Workshop-voiced. Three explicit modes (draft, critique, plan) and the router will refuse to begin work without a declared mode.
npx skillsauth add tachyon-beep/skillpacks using-creative-writingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A workshop-voiced craft pack for prose narrative — fiction (all major genres) and creative nonfiction (memoir, literary journalism, lyric and personal essay, narrative nonfiction). Sibling to lyra-ux-designer under the Lyra (arts, beauty) faction. v0.1 covers prose narrative only; poetry, scripts, plays, comics, songwriting, and interactive fiction are scheduled for v0.4.
Three modes, one router. The router enforces mode discipline because most failures of writing assistance are mode failures: the writer wanted critique and got a rewrite, wanted a plan and got a draft, wanted a draft and got a lecture about pacing.
Four hard rules, in this order:
Mode is declared, not inferred. Either the user invokes a slash command (/draft-scene, /critique-prose, /plan-story) or the router asks: "Three things I can do here — draft, critique, or plan. Which do you want?" before doing anything substantive. No silent mode-selection. The phrasing of a request ("sort it out", "fix this", "help me with this scene") rarely makes the mode explicit, and guessing wrong wastes the session.
Each mode has a hard output boundary.
Mode switches are explicit and surfaced. When a user request mid-conversation requires a different mode, the router asks: "That's a coach-mode question — want me to switch?" It does not silently oblige. A hedge in the answer ("a demonstration revision rather than a replacement") is not the same as a question; the question is the discipline.
Workshop voice throughout. Craft is treated as observable skill, not received doctrine. Multiple traditions are named when they disagree. Heuristics are framed as heuristics, not laws. Formulas (Save the Cat, Hero's Journey, three-act, MRUs) are presented with the workshop critique alongside them; the writer chooses what fits. Both literary and genre fiction are valued without ranking.
Drafter — /draft-scene. The writer provides a brief (beats, voice samples, POV constraint, target length); the scene-drafter agent produces a scene draft. Sheets typically loaded: pov-and-voice, scene-construction, dialogue (if the scene has dialogue), character-interiority (if close third or first), worldbuilding-by-implication (if setting matters). The drafter does not auto-critique its own output.
Coach — /critique-prose. The writer pastes a draft; the command fans out five coach-mode agents in parallel (developmental-reviewer, line-reviewer, pov-and-distance-auditor, dialogue-doctor, continuity-checker), then dispatches revision-coach to synthesise their reports into a prioritised revision-pass plan ("Pass 1: structural, Pass 2: line, Pass 3: dialogue polish") rather than dumping all issues at once. Coach mode never rewrites, regardless of follow-up requests.
Consultant — /plan-story. The writer brings a premise, logline, or partial outline; the outline-architect agent develops or interrogates the outline using the writer's chosen structural lens (or proposes two or three lenses if none is stated). Sheets typically loaded: story-structure-and-arc, openings-and-endings, plus any of worldbuilding-by-implication, research-and-verisimilitude, creative-nonfiction-craft as relevant. Consultant mode never drafts prose.
| Sheet | Topic | Primary consumers |
|---|---|---|
| pov-and-voice | First/second/third options, distance, free indirect discourse, slip patterns | pov-and-distance-auditor, scene-drafter |
| scene-construction | Scene vs summary vs sequel; entry late / exit early; why this scene exists | developmental-reviewer, scene-drafter |
| showing-vs-telling | Filtered narration vs scene rendering; when telling is the correct choice | line-reviewer, scene-drafter |
| character-interiority | Thought, feeling, sensation; gap between what a character notices and what is true | developmental-reviewer, line-reviewer, scene-drafter |
| dialogue | Voice differentiation, subtext, attribution rhythm, on-the-nose detection | dialogue-doctor, scene-drafter |
| prose-rhythm-and-style | Sentence variety, clause balance, paragraph cadence, reading aloud | line-reviewer |
| pacing-and-tension | Microtension vs macrotension, withholding/delaying/concealing, why middles drag | developmental-reviewer, line-reviewer |
| story-structure-and-arc | Multiple structural lenses (three-act, Freytag, hero's journey, kishōtenketsu, Yorke's Y) presented as tools, not templates | developmental-reviewer, outline-architect |
| openings-and-endings | First-page weight, the promise of the novel, ending registers, why endings are made in revision | developmental-reviewer, scene-drafter |
| worldbuilding-by-implication | Iceberg principle for setting, offhand reference as world-density, why most worldbuilding belongs cut | scene-drafter, outline-architect |
| research-and-verisimilitude | Knowing more than you put on the page, period-detail discipline, research-as-procrastination | continuity-checker, outline-architect |
| revision-and-cutting | Pass-based revision (structural before line), kill-your-darlings without sentimentality, the over-polished early-draft trap | revision-coach, line-reviewer |
| creative-nonfiction-craft | CNF/fiction overlap and divergence, truth-claim vs verisimilitude, persona vs author, ethics of writing about real people | line-reviewer, developmental-reviewer, outline-architect |
v0.2 adds nine genre-specific sheets covering the major prose-narrative genres: mystery, thriller, sf, fantasy, horror, romance, literary-fiction, memoir-and-personal-essay, literary-journalism. Each presents conventions through a uniform reader-contract discipline: name the contract → name the cost of breaking → name books worth the cost. The router loads on demand — typically one genre sheet per session, two when the project is genuinely cross-genre (literary thriller, romantasy, memoir-as-essay-collection). For three-genre projects, the router asks which to focus on rather than loading three at once.
Genre sheets reference the v0.1 craft sheets rather than re-explaining universal craft. If a genre question turns out to be a craft question (pacing, POV, dialogue), defer to the craft sheet.
The sheets do not rank genres against each other. Literary fiction is one mode among nine, with its own contract and its own breaking-costs — not the unmarked default the others deviate from. The literary-vs-genre debate is named honestly inside literary-fiction.md rather than left as subtext.
| Sheet | Contract | Cross-genre handled |
|---|---|---|
| mystery | Fair-play puzzle that resolves; cosy↔noir axis | literary-fiction, romance, horror |
| thriller | Stakes-escalation under time pressure | literary-fiction, romance |
| sf | Novum-driven extrapolation with rule-bound consequences | literary-fiction, fantasy, horror |
| fantasy | Mythopoeic coherence; soft↔hard magic axis (Sanderson's laws as one tradition) | literary-fiction, sf, romance, horror |
| horror | Dread that compounds; cosmic↔domestic axis | literary-fiction, mystery, sf, fantasy |
| romance | HEA/HFN; subgenre conventions (regency, romantasy, romantic suspense, dark) | fantasy (romantasy), thriller (rom-suspense), literary-fiction |
| literary-fiction | Ambiguity-tolerant ending, prose-as-virtue, interiority foregrounded; literary-prize/MFA/literary-press ecology | thriller, sf, horror (romance and fantasy briefly) |
| memoir-and-personal-essay | Truth-claim with persona discipline; lyric↔narrative axis | literary-journalism, literary-fiction (autofiction) |
| literary-journalism | Truth-claim with reportorial verification; subject-as-collaborator vs subject-as-material | memoir-and-personal-essay, literary-fiction |
| Agent | Mode | Scope |
|---|---|---|
| developmental-reviewer | Coach | Structure, character arcs, plot logic, scene-level cause/effect, manuscript-wide pacing |
| line-reviewer | Coach | Sentence-level prose, paragraph rhythm, word choice, filter words, weak verbs |
| pov-and-distance-auditor | Coach | POV slips, head-hopping, narrative-distance shifts, knowledge violations |
| dialogue-doctor | Coach | Per-character voice differentiation, subtext, attribution rhythm, on-the-nose detection |
| continuity-checker | Coach | Names, ages, timeline, geography, established facts — pure factual tracking, no craft judgement |
| scene-drafter | Drafter | Drafts a scene from beats + voice samples + POV/distance constraint |
| outline-architect | Consultant | Builds outlines from premise; supports multiple structural lenses; stress-tests for weak cause/effect |
| revision-coach | Consultant | Synthesises five coach-mode reports into a prioritised revision-pass plan |
| worldbuilding-consultant | Consultant | World abstraction: magic-system rule-checks, mythopoeic coherence, technological extrapolation, geography/economy/politics consistency. Distinct from outline-architect (story-level) and the worldbuilding-by-implication sheet (technique). |
| opening-and-ending-doctor | Coach | First 5 pages and last 5 pages only. Output is a promise ledger — signal inventory at the front, promise reckoning at the back. Distinct output shape from developmental-reviewer's manuscript-wide memo. |
| premise-stress-tester | Consultant (adversarial) | Pre-outline. Interrogates a premise: what is the story engine? Conflict load-bearing or decorative? What does this add to genre prior art? Distinct from outline-architect, which develops premises that have already passed muster. |
The router loads one to three craft sheets per session based on the conversation, plus one genre sheet (or two when the project is cross-genre, with a router prompt for three-genre projects). It does not load all twenty-two; the context cost is wasteful and the user's question rarely spans the whole pack. Load on demand. If a question arises that the loaded sheets do not cover, name what is missing and load the relevant sheet, rather than answering generically.
muna-panel-reviewWhen the writer wants simulated reader reactions to a draft — beta-reader panels, target-audience reactions, sensitivity reads — defer to the muna-panel-review pack: invoke /panel-review rather than reinventing reader simulation here. That pack is the canonical path for panel work, and reaching for it instead of duplicating it is the right move.
| Rationalisation | Reality | |---|---| | "User said 'just fix it' so they want a rewrite." | They want results. Results means a clear path, not silent mode collapse. Surface the mode and ask. | | "Save the Cat is what they asked for." | Heuristic, not law. Present it as one structural lens; name its critics; ask what the writer wants the lens to reveal about their project. | | "Faster to just answer than ask which mode." | Speed at the cost of voice is not speed. A one-line clarification saves an entire wasted draft. | | "I'll just rewrite a paragraph to demonstrate." | A rewrite-to-demonstrate is still drafter mode. Name the switch or do not make it. | | "They probably mean diagnostic, not drafting." | They probably mean something; you do not know what. Ask. | | "The phrasing 'sort it out' is informal — they want a quick fix." | Informality of phrasing tells you nothing about mode. Three different writers using those exact words want three different things. | | "Three-act is the universal structure." | Three-act is one lens. Kishōtenketsu, Freytag, Yorke's Y all reveal different things. Naming the lens you are using is craft; pretending one is universal is not. | | "Showing is always better than telling." | Telling is correct sometimes — compression, voice-rich narration, summary, transitions. The dictum's failure modes are real. |
If you find yourself thinking any of these, stop:
Each of these is a mode-discipline failure or a formula-as-law failure in disguise. The discipline is to surface the mode question, present formulas as lenses, and trust the writer to choose.
development
Use when **managing the delivery of work** rather than building it — running a project or a program, not writing its code. Use when a team is busy but outcomes are not landing, when "when will it be done" has no defensible answer, when status is green every week until it is suddenly red, when dependencies surprise you, when a RAID log is a graveyard, or when several projects must be coordinated toward one outcome (a program). Lean/agile-leaning, honest about where program scale needs predictive structure. Pairs with `/axiom-planning` (turning one workstream into an implementation plan) and `/axiom-sdlc-engineering` (process maturity, requirements traceability, formal governance). Do not load for writing code, picking an architecture, or designing a single feature.
tools
--- name: using-product-management description: Use when a Claude is taking **standing ownership** of a software product and driving it end-to-end across many sessions — discovery, strategy, specs, delivery orchestration, and value validation — deciding *what to build, why, for whom,* and *whether it worked*, with continuity, decision provenance, and an authority boundary that escalates anything irreversible or outward-facing to the human owner. Owns the product disciplines: opportunity assessme
tools
Use when designing, implementing, or auditing an MCP (Model Context Protocol) server — tool API design, idempotency under agent retry, structured error envelopes agents can recover from, schema versioning across model drift, transport reliability (stdio / HTTP), output-shape and pagination discipline, and choosing between tools / resources / prompts / sampling. Also use when an MCP server's tools confuse agents, return unstructured errors, deadlock under concurrent calls, double-execute under retry, or lose state across reconnects. Do not use for general REST/GraphQL API design (use `/web-backend`), for client-side prompt engineering or tool-loop design (use `/llm-specialist`), for general in-process plugin architecture (use `/system-architect`), or for cryptographic-provenance audit trails (use `/audit-pipelines`).
development
Use when running **SQLite or DuckDB inside an application process** as the durable store — not as a development convenience but as the production database. Use when scaling an SQLite layer that worked at low concurrency and is now hitting SQLITE_BUSY, WAL bloat, lock contention, schema-migration ceremony, or correctness gaps under multi-process writers. Use when introducing DuckDB as an OLAP complement to an OLTP SQLite store, or when picking between the two for a new component. Pairs with `/web-backend` (the API surface above the DB) and `/audit-pipelines` (when the DB is also the audit trail). Do not load for server databases (Postgres, MySQL), key-value stores, or ORM choice in isolation.