mycelium

Read and write forestry-state.json to coordinate persistent state across forestry skills.

1|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/JDHayesBC/Awareness --skill mycelium-jdhayesbc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mycelium
Source: https://github.com/JDHayesBC/Awareness/tree/main/.claude/skills/mycelium
Command: npx skills add https://github.com/JDHayesBC/Awareness --skill mycelium-jdhayesbc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Mycelium skill provides a shared, persistent state bus to coordinate multiple forestry skills across sessions, eliminating loss of context and drift when each skill runs independently.

Core Features & Use Cases

  • Shared state file: reads and writes forestry-state.json to synchronize /prescribe, /canopy, /deadwood, and /coppice workflows.
  • Session orchestration: initializes, updates, and reports on season signals, helping maintain continuity across restarts.
  • Cross-skill coordination: supports initialization, status checks, and updates that propagate through the Forestry sequence.

Quick Start

Run the --init command to create forestry-state.json and begin cross-skill coordination.

Frequently Asked Questions about mycelium

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I persist state across sessions for multiple independent workflows?

A shared state bus coordinates persistent state across independent workflows by reading and writing a JSON state file. This cross-session state management initializes status, updates signals, and advances lifecycle counters to prevent context loss and drift.

What is a signal bus for cross-skill state management?

A signal bus for cross-skill state management is a shared JSON file that coordinates multiple independent processes. It enforces a defined schema and lifecycle events so separate processes can read, update, and report status signals reliably across different sessions.

How do I initialize cross-session state coordination using a JSON file?

Initialize cross-session state coordination by running an init command to create the shared JSON state file. This establishes the required schema structure for the signal bus, allowing connected workflows to begin reading, writing, and synchronizing their status.

Does JSON state management work for coordinating independent workflows across restarts?

JSON state management successfully coordinates independent workflows across restarts by storing current status, signals, and lifecycle counters in a persistent file. When a workflow restarts, it reads the JSON file to resume exactly where the previous session left off.

Why does my independent workflow lose context without pattern persistence?

Independent workflows lose context without pattern persistence because each process runs in isolation, causing drift when state is not shared. Without a central JSON state file to synchronize signals, processes cannot maintain continuity or coordinate lifecycle events across restarts.