creative-writing-craft
Craft compelling fiction and creative nonfiction with attention to structure, voice, prose style, and revision. Supports short stories, novel chapters, essays, and hybrid forms. Triggers on creative writing, fiction writing, story craft, prose style, or literary technique requests.
Best use case
creative-writing-craft is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Craft compelling fiction and creative nonfiction with attention to structure, voice, prose style, and revision. Supports short stories, novel chapters, essays, and hybrid forms. Triggers on creative writing, fiction writing, story craft, prose style, or literary technique requests.
Teams using creative-writing-craft should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/creative-writing-craft/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How creative-writing-craft Compares
| Feature / Agent | creative-writing-craft | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Craft compelling fiction and creative nonfiction with attention to structure, voice, prose style, and revision. Supports short stories, novel chapters, essays, and hybrid forms. Triggers on creative writing, fiction writing, story craft, prose style, or literary technique requests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Creative Writing Craft
Transform ideas into compelling prose.
## Story Architecture
### Three-Act Structure
```
ACT I (25%) │ ACT II (50%) │ ACT III (25%)
Setup │ Confrontation │ Resolution
────────────────┼────────────────────────────┼─────────────────
Hook │ Rising Action │ Climax
Inciting Event │ Midpoint Shift │ Falling Action
First Plot Point│ Second Plot Point │ Resolution
```
### Scene Structure
```
Goal → Conflict → Disaster → Reaction → Dilemma → Decision
```
Each scene should have:
- **POV character** with a clear goal
- **Obstacle** preventing the goal
- **Stakes** if they fail
- **Outcome** (usually not what they wanted)
### Story Beats
| Beat | Percentage | Function |
|------|------------|----------|
| Opening Image | 0-1% | Establish world/tone |
| Theme Stated | ~5% | Hint at meaning |
| Setup | 1-10% | Ordinary world |
| Catalyst | ~10% | Inciting incident |
| Debate | 10-20% | Hesitation |
| Break into Two | ~25% | Commits to journey |
| B Story | ~30% | Subplot, often thematic |
| Fun and Games | 30-50% | Promise of premise |
| Midpoint | ~50% | False victory/defeat, stakes rise |
| Bad Guys Close In | 50-75% | Increasing pressure |
| All Is Lost | ~75% | Lowest point |
| Dark Night of Soul | 75-80% | Despair |
| Break into Three | ~80% | New plan/revelation |
| Finale | 80-99% | Climax, resolution |
| Final Image | 99-100% | Echo opening, show change |
---
## Character Development
### Character Dimensions
| Layer | Question | Example |
|-------|----------|---------|
| Surface | What do they show? | Confident, funny |
| Behavior | What do they do? | Helps strangers, avoids calls |
| Motive | What do they want? | Success, approval |
| Need | What do they actually need? | Self-acceptance |
| Ghost | What wound drives them? | Abandoned as child |
### Character Arc Pattern
```
Lie they believe → Want (conscious goal) → Need (unconscious)
↓ ↓ ↓
Truth they learn ← Confrontation ← Cost of lie
```
### Voice Development
To develop distinct character voice, vary:
- Sentence length and complexity
- Vocabulary level and specificity
- Speech patterns (fragments, run-ons)
- Topics they notice/mention
- What they omit or avoid
- Metaphor domains (what do they compare things to?)
---
## Point of View
### First Person
```
I walked into the room and immediately regretted it.
```
Pros: Intimacy, voice, unreliable narrator potential
Cons: Limited perspective, "I" fatigue
### Third Person Limited
```
She walked into the room and immediately regretted it.
```
Pros: Flexibility, intimacy without "I"
Cons: Can drift into head-hopping
### Third Person Omniscient
```
Sarah walked into the room, unaware that three people
were already watching her from the shadows.
```
Pros: God's-eye view, irony
Cons: Distance, harder to master
### Second Person
```
You walk into the room. You immediately regret it.
```
Pros: Immediacy, unusual
Cons: Can feel gimmicky, reader resistance
### POV Rules
1. **Stay in one head per scene** (for limited)
2. **Only show what POV character perceives**
3. **Filter through their psychology**
4. **Match POV to story needs**
---
## Prose Style
### Sentence Craft
**Vary length**:
```
Short sentences punch. They create urgency. Impact.
But longer sentences, with their flowing clauses and
subordinate phrases, can lull the reader into a rhythm,
carrying them forward on a wave of prose that builds
and builds until—
```
**Strong verbs over adverbs**:
```
❌ She walked quickly across the room.
✅ She darted across the room.
✅ She bolted across the room.
```
**Concrete over abstract**:
```
❌ He felt sad.
✅ His chest ached. He couldn't swallow.
```
### Show vs Tell
**Telling** (has its place):
```
She was angry.
```
**Showing**:
```
Her jaw tightened. She set down her fork—carefully,
deliberately—and folded her hands in her lap.
```
When to tell:
- Transitions
- Unimportant information
- Pacing through slow periods
- Emotional summary after intense scene
### Dialogue
**Subtext**: Characters rarely say what they mean.
```
"Nice weather," she said. (Text)
[I don't want to talk about it] (Subtext)
```
**Attribution**:
```
✅ "I'm leaving," she said.
✅ "I'm leaving." She grabbed her coat.
⚠️ "I'm leaving," she exclaimed angrily.
```
"Said" is invisible. Use it.
**Beats over tags**:
```
"I'm leaving." She grabbed her coat. "Don't wait up."
```
---
## Description
### Sensory Writing
| Sense | Often Used | Underused |
|-------|------------|-----------|
| Sight | Very common | - |
| Sound | Common | - |
| Touch | Uncommon | Temperature, texture |
| Smell | Rare | Memory trigger |
| Taste | Rare | Atmosphere |
**Layer senses**:
```
The bar smelled like spilled beer and regret. Neon
buzzed overhead, painting everyone the same shade of
desperate pink. Someone fed the jukebox, and Patsy
Cline started breaking hearts again.
```
### Meaningful Detail
Choose details that do double duty:
```
❌ The room had a desk, a chair, and a filing cabinet.
[Inventory]
✅ Dust furred the family photos on his desk—all
turned to face the wall.
[Character revelation + atmosphere]
```
---
## Revision Framework
### Levels of Revision
| Level | Focus | Questions |
|-------|-------|-----------|
| Structural | Story architecture | Does the plot work? Are scenes in right order? |
| Scene | Individual scenes | Does each scene have conflict? Purpose? |
| Paragraph | Flow and pacing | Transitions smooth? Rhythm varied? |
| Sentence | Prose quality | Verbs strong? Sentences varied? |
| Word | Precision | Right word? Unnecessary words? |
### Revision Passes
**Pass 1: Story**
- Does the beginning hook?
- Is the ending earned?
- Does the middle sag?
- Are stakes clear?
**Pass 2: Character**
- Distinct voices?
- Consistent motivation?
- Arc completed?
- Relationships clear?
**Pass 3: Scene**
- Each scene has purpose?
- Conflict present?
- Sensory grounding?
- POV consistent?
**Pass 4: Line**
- Cut filler words (just, really, very)
- Strengthen verbs
- Vary sentence structure
- Check dialogue tags
**Pass 5: Polish**
- Read aloud
- Check spelling/grammar
- Format consistency
- Final typo sweep
---
## Common Problems
### Pacing Issues
| Symptom | Cause | Fix |
|---------|-------|-----|
| Drags | Too much description | Cut, add conflict |
| Rushed | Not enough scene | Slow down, add beats |
| Confusing | Time jumps | Add transitions |
| Boring | No stakes | Raise consequences |
### Dialogue Issues
| Problem | Example | Fix |
|---------|---------|-----|
| On-the-nose | "I'm angry at you!" | Subtext |
| Talking heads | Dialogue without action | Add beats |
| Info dump | Explaining plot | Conflict over info |
| Same voice | All characters same | Differentiate |
### Description Issues
| Problem | Fix |
|---------|-----|
| Purple prose | Simplify, cut adjectives |
| No setting | Ground in physical space |
| Floating heads | Add action, gesture |
| Info dump | Distribute, dramatize |
---
## Forms
### Short Story
- 1,000-7,500 words typical
- Single effect/impression
- Limited scope
- Often one POV
### Flash Fiction
- Under 1,000 words
- Implication over exposition
- Often twist or resonance
- Every word counts
### Novel Chapter
- 2,000-5,000 words typical
- Mini-arc or cliffhanger
- Advances plot AND character
- Varies with genre
### Personal Essay
- First person reflection
- Particular to universal
- Scene + reflection
- "So what?" answered
---
## References
- `references/story-structures.md` - Alternative structures
- `references/genre-conventions.md` - Genre expectations
- `references/revision-checklist.md` - Detailed checklistRelated Skills
technical-analytical-writing
Write clear technical analysis, system architecture documents, decision records, and research synthesis. Covers argument structure, evidence-based reasoning, and technical communication patterns. Triggers on technical writing, architecture documentation, ADR creation, or analytical essay requests.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.
landscape-discovery-audit
Phase 1 of the pentaphase structural-overhaul protocol. Inventories assets, maps current flow, identifies friction, and defines value metrics for any substrate. Use when the user invokes phase 1 of an overhaul, requests a baseline audit, asks to "discover the landscape" of a system, or wants to understand current state before redesigning. Produces phase-1-landscape-report.md.
governance-evolution-protocol
Phase 5 of the pentaphase structural-overhaul protocol. Codifies operational protocols, onboards the ecosystem of participants, programs behavior monitoring, and establishes an iteration cadence so the substrate evolves rather than calcifies. Use when the user invokes phase 5 of an overhaul, asks to "establish governance" or "lock in the protocols", or has completed ingestion and is ready to declare the substrate operational. Consumes phase-4-ingestion-report.md; produces phase-5-governance-charter.md, which closes the protocol.
dimension-surfacing
Surfaces the parallel domain dimensions implicit in a dense or minimal prompt. Use when a user prompt is small on the surface but plainly implies multiple independent domains needing different expertise; when explicitly invoked by the coliseum-orchestrator skill as Phase 1; or when the user asks "what dimensions does this prompt encode" or "what axes does this break into." Produces a named dimension set where each dimension is independently executable and not a paraphrase of another.
coliseum-dispatch
Dispatches a composed set of assignment envelopes to domain-expert subagents in parallel, in a single message with multiple Agent tool calls. Enforces the no-pingpong gate via the pingpong-detector agent before any dispatch fires. Use when invoked by the coliseum-orchestrator as Phase 3; when envelopes are already composed and the next step is parallel execution; or when the user asks to "fan out" or "dispatch in parallel." Produces a dispatch log capturing what was sent, when, and where returns land.
assignment-composition
Wraps each surfaced dimension as a self-contained 9-section autonomous-work-assignment envelope — scope, context, success criteria, allowed tools, return format, handoff — all the recipient subagent needs to execute without coming back. Use when invoked by coliseum-orchestrator as Phase 2; when dimensions are named and the next step is to make each independently dispatchable; or when the user asks "compose this as an assignment." The no-pingpong gate validates each envelope before dispatch.
workspace-autopsy-governance
Conducts a full automated autopsy of the current workspace directory to map files, identifies structural issues, proposes a restructuring plan (the signal), and establishes unified governance using templates. Use this skill when a user asks to map, restructure, reorganize, or apply new governance to an existing messy repository.
workshop-presentation-design
Design engaging workshops, conference talks, and educational presentations. Covers learning objectives, activity design, slide craft, and facilitation techniques. Triggers on workshop design, presentation prep, talk structure, or training session requests.