← ClaudeAtlas

storylisted

Track tickets, issues, and progress for your project. Load project context, manage sessions, guide setup.
Storybloq/storybloq · ★ 788 · AI & Automation · score 82
Install: claude install-skill Storybloq/storybloq
# Storybloq - Project Context & Session Management storybloq tracks tickets, issues, roadmap, and handovers in a `.story/` directory so every AI coding session builds on the last instead of starting from zero. Invocation differs by client: use `/story` in Claude Code, `$story` in Codex, or ask naturally to use the Storybloq skill. **Client profile.** Resolve the profile once per invocation. `STORYBLOQ_CLIENT=codex` selects `{ id: "codex", displayName: "Codex", storyCommand: "$story" }`; unset, `claude`, or an unknown value selects `{ id: "claude", displayName: "Claude Code", storyCommand: "/story" }`. Render the resolved `storyCommand` in user-facing instructions. Capabilities such as structured questions, task navigation, exact-message relay, and subagents are separate exact-name runtime gates, not profile fields. This resolution governs RENDERING ONLY -- which `storyCommand` to display. Step 0's bootstrap fallback below decides the SETUP COMMAND to run when CLI/MCP are missing, using a different, inherent-identity signal (`STORYBLOQ_CLIENT` is set only after that same setup has already run once, so it cannot gate the first run of it); the two resolutions are independent and must not be unified into one. **Client task identity.** A Codex SessionStart hook may inject `[storybloq-client-task]` with `client=codex` and an opaque `id`. Use that validated id. If the marker is absent, probe only the corresponding variable with the read-only command `printenv CODEX_THREAD_ID` or