The CLI
Storybloq CLI.
The agentic development framework CLI.
The storybloq CLI provides structured access to your .story/ project state. Claude Code and Codex both get context loading, autonomous mode, MCP tools, and client hooks from the same engine and client-specific skill command.
/story
What /story does.
Run /story in Claude Code and it does five things before you type a word.
- i.Loads project status -tickets, 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 ticket to work on
File convention
The .story/ directory.
config.jsonProject config (name, type, language)roadmap.jsonPhase ordering and metadatatickets/One JSON file per work item (T-001.json, T-002.json)issues/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.
20+ read tools and 10+ write tools that Claude Code and Codex call directly. Status, tickets, issues, handovers, phases, notes, lessons, snapshots, recaps, recommendations, and more.
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.