character-management

Provide the character's name and role (protagonist, antagonist, supporting, or minor), then build the profile through conversation covering appearance, personality, backstory, motivations, voice, and arc. The result is saved as a markdown file with YAML frontmatter in the characters/ directory.

Relationships are stored in each character's frontmatter using typed entries like parent, rival, or mentor. Every relationship is bidirectional, so adding one to a character also adds the inverse type to the other character's file.

No, the Story CLI is optional. If it is unavailable, the skill falls back to the story-maintenance script or performs registry updates and backlink checks manually, though CLI access enables automated reindexing and validation.

Yes, family trees are maintained in the characters/_index.md file under a Family Trees section. Children are indented under parents, and marriages or partnerships are noted inline using the family relationship types.

A story project must already exist, verified by the presence of story.md in the project root, typically created via the story-init skill. Character files are stored in the characters/ directory with a central _index.md registry.