Stats
Actions
Tags
From bee
Manages workflow state in bee-state.local.md via a shell script. Provides commands to init, set, get, and clear fields like feature, phase, and progress.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bee:bee-stateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The state script manages `.claude/bee-state.local.md` — the source of truth for workflow progress across sessions.
The state script manages .claude/bee-state.local.md — the source of truth for workflow progress across sessions.
CRITICAL: Never use Write or Edit tools on bee-state.local.md — that triggers permission prompts. Always use this script via Bash. It is pre-approved in allowed-tools.
${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh
Initialize (after triage):
"${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh" init --feature "User auth" --size FEATURE --risk MODERATE
Update fields (incremental — only pass what changed):
"${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh" set --current-phase "single-phase" --phase-spec "docs/specs/user-auth.md — confirmed"
Read state (on startup):
"${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh" get
Read single field:
"${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh" get --field feature
Clear (when done):
"${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh" clear
--feature, --size, --risk, --discovery, --design-brief, --boundaries, --current-phase, --phase-spec, --architecture, --tdd-plan, --current-slice, --phase-progress, --slice-progress
For phase-progress and slice-progress, use | as line separator:
"${CLAUDE_PLUGIN_ROOT}/scripts/update-bee-state.sh" set --phase-progress "Phase 1: done — Cart|Phase 2: executing|Phase 3: not started"
npx claudepluginhub incubyte/ai-plugins --plugin beeCheckpoints and resumes workflow state across sessions. Saves phase, task progress, and artifacts for later continuation.
Maintains a living STATE.md document tracking current project context, active tasks, blockers, and next steps. Auto-loads at session start or on explicit commands like 'update state' or 'where was I'.
Drives a config-driven state machine for dev workflows: reads state.md, executes stages inline or via subagents, transitions via update-status.sh. Requires an existing state.md bootstrap.