AI coding assistants often lack statelessness, leading to repeated work and lost context between sessions. Storybloq addresses this by introducing a standardized `.story/` directory structure within projects to store tickets, issues, roadmap phases, session handovers, and lessons learned. This setup, combined with a CLI, an MCP server, and a dedicated Claude Code skill, ensures that every coding session builds upon the last, providing Claude with full project awareness, enabling compounding work, and preventing the need to re-establish context from scratch.
Key Features
010 GitHub stars
02Autonomous mode (`/story auto`) to drive tickets through their lifecycle from planning to review and commit.
03CLI (`storybloq`) for inspecting and mutating project state from the terminal.
04MCP server with 43 tools for direct, low-latency interaction with Claude Code.
05Claude Code skill (`/story`) to load project state and manage session continuity.
06Standardized `.story/` directory for persistent project context, tracked by Git.
Use Cases
01Maintaining continuous context across multiple AI coding sessions to avoid redundant setup.
02Standardizing project management artifacts (tickets, issues, handovers) for AI-native development.
03Automating ticket workflows and code reviews with AI agents using structured project data.
