StoryForge

Display 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.

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.

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.

Run a comprehensive security audit on the current project. Scans for secrets, vulnerabilities, dangerous configs, and risky patterns. Use at the end of each sprint or before releases.

Run the StoryForge upstream documentation monitor to check for Anthropic doc changes. Use daily or when you suspect Claude Code has been updated.