Run repo-local story, handover, and review workflows with Storybloq
Use Storybloq when Claude Code or Codex needs durable repo-local stories, plans, handovers, lessons, and review evidence instead of rediscovering project state each session.
npx skills add agentskillexchange/skills --skill run-repo-local-story-handover-and-review-workflows-with-storybloq
npm install -g @storybloq/storybloq@latest, run storybloq setup --client all to install the Claude Code/Codex skill and MCP server, then initialize a project with storybloq init --name . In Claude Code invoke /story; in Codex invoke $story to load or update the repo-local project state.Use Storybloq when an operator wants coding agents to maintain project state as reviewable files beside the code. The workflow initializes a .story/ directory, records stories, issues, roadmap phases, decisions, lessons, plan snapshots, review evidence, and handovers, then lets Claude Code or Codex reload that state through the bundled skill, CLI, hooks, and MCP server.
What this skill actually does
Invoke this instead of using the product normally when the job is not just viewing a project board, but giving a coding agent a durable operating record: choose the next story, continue after an interrupted session, run autonomous plan/review/checkpoint workflows, or hand work across sessions without relying on chat history.
The scope boundary is repo-local agent workflow state for software delivery. It is not a generic project-management SaaS card, a broad MCP listing, or a plain memory store; the repeatable operator workflow is installing Storybloq in a repository and having supported coding agents read and update exact .story/ artifacts during planning, implementation, review, and handover.