story

Load project context from .story/ to track tickets and issues across sessions.

689|35|Updated Apr 17, 2026

Search Tags:#tickets #project-context #session-context #recap #handovers #storybloq

Ready to run

npx skills add https://github.com/Storybloq/storybloq --skill story-storybloq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: story
Source: https://github.com/Storybloq/storybloq/tree/main/src/skill
Command: npx skills add https://github.com/Storybloq/storybloq --skill story-storybloq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI coding sessions are often stateless, forcing users to re-explain context every time. This Skill loads a persistent .story/ context to keep tickets, issues, roadmaps, and handovers available across sessions.

Core Features & Use Cases

Load project context from .story/ at session start.
Track tickets, issues, roadmap, and handovers across sessions.
Support session recap and handover creation to preserve decisions.
Query status, recaps, and lessons to inform ongoing work.

Quick Start

Invoke /story to load context and continue from the previous session.

Frequently Asked Questions about story

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I preserve project context across Claude Code sessions?▼

Preserve project context by loading a persistent `.story/` directory that tracks tickets, issues, roadmaps, and handovers. Invoke `/story` at session start to load context and continue from the previous session without re-explaining decisions.

How does session handover work for AI coding tickets and roadmaps?▼

Session handover works by creating a recap of changes and decisions from one session to the next. The Skill enforces loading rules to surface tickets, issues, and roadmap status, ensuring ongoing work continues with full context.

Can I track project tickets and issues inside Claude Code?▼

Yes, you can track project tickets and issues inside Claude Code. The Skill stores them in a persistent `.story/` context, exposing roadmaps and handovers to guide ongoing work and query status across multiple sessions.

What is the best way to recap changes and decisions from a previous coding session?▼

The best way to recap changes is by invoking `/story` at session start. It loads the persistent project context, surfaces decisions from the previous session, and supports handover creation to inform ongoing work.

Do I need a specific framework to load project context into Claude Code?▼

No specific framework is required, but the Skill integrates with storybloq MCP and CLI flows as needed. It relies on a persistent `.story/` context to load tickets, issues, roadmaps, and handovers.

Why does Claude Code lose my project context between sessions?▼

Claude Code loses context because AI coding sessions are stateless. This Skill solves the problem by enforcing loading rules for a persistent `.story/` directory, keeping tickets, issues, and handovers available across sessions.