Commands Reference - Storyline Docs

Complete reference for all Storyline slash commands.

/sl-setup

Initialize, manage, and check Storyline projects.

Usage

/sl-setup              # Interactive setup and onboarding
/sl-setup init         # Initialize .storyline/ directory
/sl-setup status       # Show project state and next steps
/sl-setup guide        # Display full tutorial
/sl-setup check        # Verify installation

Examples

Initialize a new project:

/sl-setup init

Check current progress:

/sl-setup status

Verify installation health:

/sl-setup check

---

/sl-epic-creator

Parse a PRD or technical spec into epics.

Usage

/sl-epic-creator [prd-file]

Arguments

Argument	Description
prd-file	Path to PRD markdown file (optional)

Behavior

With file: Parses the provided PRD into epics, prompts for optional identifier.

Without file: Launches guided mode to create PRD interactively.

Output

Creates files in .storyline/:

• PRD-{identifier}.md — The PRD (if created or copied)
• epics/epic-{identifier}-{nn}-{name}.md — One or more epics

Examples

Parse existing PRD:

/sl-epic-creator docs/product-requirements.md

Create PRD interactively:

/sl-epic-creator

---

/sl-story-creator

Generate user stories from an epic or create standalone stories.

Usage

/sl-story-creator [epic-file]

Arguments

Argument	Description
epic-file	Path to epic markdown file (optional)

Behavior

With file: Generates stories from the specified epic.

Without file: Launches guided mode for standalone story creation.

Output

Epic-based:

.storyline/stories/epic-{id}/
├── story-01.md
├── story-02.md
└── INDEX.md

Standalone:

.storyline/stories/.standalone/
└── story-{slug}.md

Features

• Validates story format
• Ensures INVEST criteria compliance
• Links to parent epic (or marks standalone)
• Supports optional tracking identifiers

Examples

From epic:

/sl-story-creator .storyline/epics/epic-auth-01-authentication.md

Standalone (guided):

/sl-story-creator

---

/sl-spec-story

Create technical specification from a user story.

Usage

/sl-spec-story <story-file>

Arguments

Argument	Description
story-file	Path to story markdown file (required)

Spec Strategies

For epic-based stories, you’ll choose a strategy:

Strategy	Mapping	Use Case
Simple	1 story → 1 spec	Default, most common
Complex	1 story → N specs	Large stories needing multiple specs
Combined	N stories → 1 spec	Related stories implemented together

Standalone stories always use simple strategy.

Output

.storyline/specs/epic-{id}/
└── spec-{nn}.md

# or for standalone:
.storyline/specs/.standalone/
└── spec-{slug}.md

Includes

• Architecture decisions
• File changes required
• Dependencies and imports
• Testing requirements
• Acceptance criteria

Examples

From epic-based story:

/sl-spec-story .storyline/stories/epic-auth-01/story-01.md

From standalone story:

/sl-spec-story .storyline/stories/.standalone/story-fix-login.md

---

/sl-develop

Execute a technical spec and implement the code.

Usage

/sl-develop <spec-file>

Arguments

Argument	Description
spec-file	Path to spec markdown file (required)

Process

1. Converts spec to PLAN.md format
2. Invokes create-plans for execution
3. Breaks work into atomic tasks (2-3 per plan)
4. Executes with quality controls
5. Runs tests and fixes errors
6. Creates git commits using /sl-commit
7. Generates SUMMARY.md

Output

• Working code in your project
• .storyline/.planning/{spec-id}/PLAN.md
• .storyline/.planning/{spec-id}/SUMMARY.md
• Git commits (not pushed)

Examples

/sl-develop .storyline/specs/epic-auth-01/spec-01.md

---

/sl-commit

Create a git commit with conventional commit message format.

Usage

/sl-commit [message]

Arguments

Argument	Description
message	Custom commit message (optional)

Behavior

Without message: Analyzes git diff and generates semantic message.

With message: Uses provided message with conventional format.

Features

• Analyzes changes to determine type (feat/fix/chore)
• 50-character summary limit
• Detailed bulleted descriptions
• Maintains project commit style
• Never auto-pushes

Commit Types

Type	Description
feat:	New feature
fix:	Bug fix
chore:	Maintenance, refactoring
docs:	Documentation changes
test:	Test additions/changes

Examples

Auto-generate message:

/sl-commit

Custom message:

/sl-commit "Add password reset flow"

---

Command Quick Reference

Command	Purpose	Required Args
/sl-setup	Project management	None
/sl-setup init	Initialize project	None
/sl-setup status	Show progress	None
/sl-setup check	Verify installation	None
/sl-epic-creator	Create epics	Optional PRD path
/sl-story-creator	Create stories	Optional epic path
/sl-spec-story	Create specs	Story path
/sl-develop	Implement code	Spec path
/sl-commit	Create commits	Optional message

Next Steps

• Workflow — Understand the full pipeline
• Quick Start — Walk through your first feature
• FAQ — Common questions and troubleshooting