Character Management
Overview
Create and manage rich character profiles for a story project. Each character is a markdown file with YAML frontmatter in the characters/ directory. Characters are cross-referenced with other story elements through kebab-case identifiers.
Prerequisites
A story project must already exist (created via the story-init skill). Verify by checking for story.md in the project root.
Creating a Character
- Read
story.md for genre, themes, and tone context
- Read
characters/_index.md for existing characters
- Ask for the character's name and role (protagonist, antagonist, supporting, minor)
- Build the profile through conversation, exploring:
- Appearance and distinguishing features
- Personality, traits, and quirks
- Backstory and formative events
- Motivations (external wants vs internal needs)
- Voice and speech patterns (ask for example dialogue)
- Character arc (starting state, turning points, ending state)
- Key life events for the timeline
- Write the character file using the template in
references/character-template.md
- Save to
characters/{name-kebab}.md, or use story add character "{Name}" --role "{role}" when the CLI is available
- Update
characters/_index.md registry table
- If relationships reference existing characters, update those character files too
- When CLI access is available, run the maintenance pass in the story root:
story reindex .
story links .
story validate .
Updating a Character
- Read the existing character file
- Read
characters/_index.md for context on other characters
- Make the requested changes
- If relationships changed, update the other character's file (bidirectional)
- Update
characters/_index.md if role or status changed
- When CLI access is available, run
story reindex ., story links ., and story validate .
Managing Relationships
Reference references/relationship-types.md for the full list of relationship types and inverse pairs.
When adding a relationship:
- Add the relationship entry to the character's frontmatter
- Add the inverse relationship to the other character's frontmatter
- Update the Relationship Map section in
characters/_index.md
Family Trees
Family trees are maintained in the characters/_index.md under the "Family Trees" section. Format:
## Family Trees
### {Family Name}
- **{Character Name}** ({status}) - [{name-kebab}.md]
- **{Child Name}** - [{name-kebab}.md]
- **{Child Name}** - [{name-kebab}.md]
Indent children under parents. Note marriages/partnerships inline.
Cross-Referencing
- When a character is referenced in worldbuilding (e.g., a location's
notable-characters), ensure the link exists both ways
- Character-location backlinks live in the character file's
locations frontmatter list
- Faction memberships live in
worldbuilding/factions/{faction-kebab}.md under members
- Artifact ownership can reference a character id in
worldbuilding/artifacts/{artifact-kebab}.md
- When a character appears in a plot arc, ensure they're listed in the arc's
characters frontmatter
- Character tags should be consistent across the project (e.g., if
magic-user is used, always use that exact tag)
CLI Maintenance
Use the Story CLI when it is available. If story is not installed but the story-maintenance skill is present, use node ../story-maintenance/scripts/story.js with the same arguments, resolving the path relative to this skill folder. If no CLI is available, perform the registry and backlink checks manually.
Reference Files
references/character-template.md - Full blank template for character profiles
references/relationship-types.md - Complete relationship type reference with inverse pairs
1---
2name: character-management
3description: This skill should be used when the user asks to "create a character", "update a character", "add a character", "build a family tree", "character relationships", "character timeline", "character arc", "character profile", or needs to manage characters in a story project.
4metadata:
5 source: https://skillmd.com/skills/danjdewhurst/character-management
6---
7
8# Character Management
9
10## Overview
11
12Create and manage rich character profiles for a story project. Each character is a markdown file with YAML frontmatter in the `characters/` directory. Characters are cross-referenced with other story elements through kebab-case identifiers.
13
14## Prerequisites
15
16A story project must already exist (created via the story-init skill). Verify by checking for `story.md` in the project root.
17
18## Creating a Character
19
201. Read `story.md` for genre, themes, and tone context
212. Read `characters/_index.md` for existing characters
223. Ask for the character's name and role (protagonist, antagonist, supporting, minor)
234. Build the profile through conversation, exploring:
24 - Appearance and distinguishing features
25 - Personality, traits, and quirks
26 - Backstory and formative events
27 - Motivations (external wants vs internal needs)
28 - Voice and speech patterns (ask for example dialogue)
29 - Character arc (starting state, turning points, ending state)
30 - Key life events for the timeline
315. Write the character file using the template in `references/character-template.md`
326. Save to `characters/{name-kebab}.md`, or use `story add character "{Name}" --role "{role}"` when the CLI is available
337. Update `characters/_index.md` registry table
348. If relationships reference existing characters, update those character files too
359. When CLI access is available, run the maintenance pass in the story root:
36
37```shell
38story reindex .
39story links .
40story validate .
41```
42
43## Updating a Character
44
451. Read the existing character file
462. Read `characters/_index.md` for context on other characters
473. Make the requested changes
484. If relationships changed, update the other character's file (bidirectional)
495. Update `characters/_index.md` if role or status changed
506. When CLI access is available, run `story reindex .`, `story links .`, and `story validate .`
51
52## Managing Relationships
53
54Reference `references/relationship-types.md` for the full list of relationship types and inverse pairs.
55
56When adding a relationship:
57- Add the relationship entry to the character's frontmatter
58- Add the inverse relationship to the other character's frontmatter
59- Update the Relationship Map section in `characters/_index.md`
60
61## Family Trees
62
63Family trees are maintained in the `characters/_index.md` under the "Family Trees" section. Format:
64
65```markdown
66## Family Trees
67
68### {Family Name}
69- **{Character Name}** ({status}) - [{name-kebab}.md]
70 - **{Child Name}** - [{name-kebab}.md]
71 - **{Child Name}** - [{name-kebab}.md]
72```
73
74Indent children under parents. Note marriages/partnerships inline.
75
76## Cross-Referencing
77
78- When a character is referenced in worldbuilding (e.g., a location's `notable-characters`), ensure the link exists both ways
79- Character-location backlinks live in the character file's `locations` frontmatter list
80- Faction memberships live in `worldbuilding/factions/{faction-kebab}.md` under `members`
81- Artifact ownership can reference a character id in `worldbuilding/artifacts/{artifact-kebab}.md`
82- When a character appears in a plot arc, ensure they're listed in the arc's `characters` frontmatter
83- Character tags should be consistent across the project (e.g., if `magic-user` is used, always use that exact tag)
84
85## CLI Maintenance
86
87Use the Story CLI when it is available. If `story` is not installed but the `story-maintenance` skill is present, use `node ../story-maintenance/scripts/story.js` with the same arguments, resolving the path relative to this skill folder. If no CLI is available, perform the registry and backlink checks manually.
88
89## Reference Files
90
91- **`references/character-template.md`** - Full blank template for character profiles
92- **`references/relationship-types.md`** - Complete relationship type reference with inverse pairs