Slash commands

Quick-fire commands you can type instead of describing the workflow in prose. Each one invokes the matching skill.

When to use a slash command vs. just talking

Slash commands are great for repeat workflows — you know what you want, you want one line of typing. For first-time flows or anything you might back-and-forth on, just describe it in chat. The skills fire the same way either route.

/stos-task <what to remember>

Quick-capture a task. One short title, optional description, saved against the active pen name.

Fires: quick-task-capture skill

/stos-task remember to email the cover designer about the rebrand

/stos-write <description of what to draft>

Start a chapter-drafting flow. Reads the pen-name persona + story bible, drafts in voice, saves on approval.

Fires: chapter-drafting skill

/stos-write draft chapter 4 of Curses and Currents under Indie Annie

/stos-time <start | stop | status>

Start, stop, or check a writing timer against the active pen name + title.

Fires: time-tracking skill

/stos-time start

/stos-bible <title name or id>

Generate a full story bible for a title — looped per-entity, no batching. Saves every character, location, event, lore entry, and association individually.

Fires: story-bible skill

/stos-bible Curses and Currents

/stos-finance <income | expense> <amount> <note>

One-line finance entry. Resolves the vendor + pen name if mentioned, then saves the transaction with the right scope.

Fires: finance skill

/stos-finance expense 400 editor Sarah Marsh on Curses and Currents

/stos-revise <chapter (id, number, or title)> -- <feedback>

Revise an existing chapter using dev-edit-style feedback. Preserves persona voice + continuity. Saves on approval.

Fires: chapter-drafting skill (revise mode)

/stos-revise chapter 7 -- tighten the pacing, cut the second exposition block