state-management
State persistence and management
What this skill does
# State Management Skill
This skill handles loading, saving, and validating workflow state.
## State File Path
`.claude/claude-bot.local.md`
## Reading State
To read the current state:
1. Check if file exists
2. Parse YAML frontmatter
3. Validate structure
4. Return state object
```yaml
# State returned as object with these fields
workflow_state:
version: "1.0"
status: "active|paused|completed|blocked"
current_phase: "plan|explore|design|implement|validate|test|document|complete"
started_at: "ISO timestamp"
updated_at: "ISO timestamp"
goal:
original_request: "string"
refined_requirements: []
accepted: true
phases:
plan: { status, tasks, blockers }
explore: { status, tasks, blockers }
design: { status, tasks, blockers }
implement: { status, tasks, blockers }
validate: { status, tasks, blockers }
test: { status, tasks, blockers }
document: { status, tasks, blockers }
decisions_made: []
agent_history: []
next_actions: []
```
## Writing State
To save state:
1. Update state object
2. Convert to YAML
3. Write to .local.md with frontmatter
```markdown
---
workflow_state:
version: "1.0"
status: "active"
current_phase: "plan"
started_at: "2025-01-13T10:00:00Z"
updated_at: "2025-01-13T10:05:00Z"
goal:
original_request: "Add JWT auth"
refined_requirements: []
accepted: true
# ... rest of state
---
# Claude-Bot State
This file contains the persistent state for the Claude-Bot autonomous workflow.
Do not edit manually - use /bot-status, /bot-resume, or /bot-stop commands.
```
## Validation
A valid state must have:
- `workflow_state` with `status` and `current_phase`
- `goal` with `original_request`
- `phases` with entries for each phase
## State Transitions
Valid status transitions:
- `active` → `paused` (user stops)
- `active` → `blocked` (blocker detected)
- `paused` → `active` (resume)
- `blocked` → `active` (resolution provided)
- `active` → `completed` (all phases done)
Valid phase transitions:
- Must complete current phase before moving to next
- Can resume from any non-completed phase
## Utility Functions
### Check for Active Workflow
```bash
# Returns true/false
if [ -f ".claude/claude-bot.local.md" ]; then
STATUS=$(grep "status:" .claude/claude-bot.local.md | head -1)
if [[ "$STATUS" =~ (active|paused|blocked) ]]; then
echo "true"
fi
fi
echo "false"
```
### Get Current Phase
```bash
# Returns phase name
awk '/^current_phase:/ {print $2}' .claude/claude-bot.local.md
```
### Update Single Field
```bash
# Update status
sed -i '' 's/^status: .*/status: paused/' .claude/claude-bot.local.md
```
## Backup
Consider creating backups before major changes:
```
.claude/claude-bot.local.md.backup
```
## Cleanup
When workflow completes, consider archiving rather than deleting:
```
.claude/claude-bot.completed.2025-01-13.md
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.