// Create a new Story with structured fields including acceptance criteria, non-goals, risks, and follow-ups. Use when a new piece of work needs to be planned before implementation.
| name | story-write |
| description | Create a new Story with structured fields including acceptance criteria, non-goals, risks, and follow-ups. Use when a new piece of work needs to be planned before implementation. |
| argument-hint | story-title |
| disable-model-invocation | true |
Create a new StoryForge Story file with all required fields.
First, read .kanban/stories/ to find the next available Story ID
Ask the user for:
.kanban/features/ for existing files
and .kanban/board.md for the features table).kanban/features/ using FEAT-TEMPLATE.md as the base, and add it to the
Features table in board.mdCreate the Story file at .kanban/stories/STORY-NNN.md:
# STORY-NNN: (Title)
- **Feature**: FEAT-NNN - (Feature Name)
- **Initiative**: INIT-NNN - (Initiative Name)
- **Status**: Backlog
- **Created**: (Today's date)
## Context
(Why this work is needed)
## Acceptance Criteria
- [ ] (Criterion 1)
- [ ] (Criterion 2)
- [ ] (Criterion 3)
## Non-Goals
- (What is explicitly NOT in scope)
## Implementation Notes
(Technical approach or constraints - fill in during planning)
## Validation Notes
(How to verify the work is correct - fill in during planning)
## Risks
- (Known risks or uncertainties)
## Follow-ups
- (Work discovered that should be done later)
.kanban/board.md to include the new Story in the Backlog column.kanban/backlog.md if a new Feature or Initiative was createdDisplay the StoryForge Kanban dashboard showing board status, features, active stories, sprint progress, and recent activity. Use to get a quick overview of project delivery state.
Update StoryForge delivery artifacts after work is completed. Updates story status, board, changelog, and captures follow-ups. Use after completing implementation work.
Plan or review a sprint by selecting Stories from Ready state into the sprint backlog. Use for sprint planning or mid-sprint reviews.
Link a StoryForge story to a GitHub Issue or Pull Request. Updates the story's GitHub field and optionally adds a comment on the GitHub issue. Use when starting work that relates to a GitHub issue.
Initialize a project with StoryForge Kanban delivery structure. Creates .kanban/ directory with board, backlog, sprint, decisions, changelog, and stories directory. Use when setting up a new project for StoryForge delivery tracking.
Process an Anthropic Claude Code release or documentation change and determine its impact on StoryForge. Use when a new Claude Code version is released or docs change.