The CLI
Storybloq CLI.
Project memory and workflow in your terminal.
Connect Claude Code or Codex to your project memory. Load context, record stories, and save handovers from the tools you already use.
/story
What /story does.
Run /story in Claude Code and it does five things before you type a word.
- i.Loads project status: stories, issues, phases, blockers
- ii.Shows what changed since last snapshot
- iii.Reads the last 3 session handovers for continuity
- iv.Loads development rules and lessons learned
- v.Suggests the next story to work on
File convention
The .story/ directory.
Stories are saved as ticket records in tickets/. CLI commands keep the name ticket.
config.jsonProject config (name, type, language)roadmap.jsonPhase ordering and metadatatickets/Your stories, stored as ticket recordsissues/One JSON file per bug or gap (ISS-001.json)notes/Brainstorming and ideas (N-001.json)handovers/Session continuity documents (markdown)snapshots/State snapshots for session diffs (gitignored)MCP
30+ tools.
Tools that Claude Code and Codex call to read and update status, stories, issues, handovers, lessons, and review records.
Pattern
Working across multiple repos.
The CLI walks up the directory tree to find .story/, so a single shared .story/ at a wrapper directory can serve many sub-repos. Each sub-repo keeps its own git history; the wrapper keeps the shared memory.