greenwood

Name: greenwood
Availability: InStock
Author: jdhayesbc

Validate season and prescription before planting deliberate growth in a topology.

1|Updated Dec 28, 2025

Search Tags:#topology #mycelium #prescription #planting #undergrowth #deliberate-growth #forestry-state

Ready to run

npx skills add https://github.com/JDHayesBC/Awareness --skill greenwood

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: greenwood
Source: https://github.com/JDHayesBC/Awareness/tree/main/.claude/skills/greenwood
Command: npx skills add https://github.com/JDHayesBC/Awareness --skill greenwood

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Greenwood helps teams add new components or abstractions to a software topology in a deliberate, context-aware way by coordinating sequencing with prescriptions and viability checks.

Core Features & Use Cases

Verifies season and viability signals before adopting new growth to ensure alignment with topology goals
Enforces a staged workflow: /prescribe → /canopy → /deadwood → /coppice → /undergrowth → /greenwood
Applies guardrails around season and explicit prescriptions to prevent unsanctioned growth
Integrates with session management to maintain coherent identity across topology changes

Quick Start

After /prescribe names the goal and /undergrowth probe confirms viability, run the planting step to add deliberate growth.

Frequently Asked Questions about greenwood

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

FAQPage Schema

How do I validate software topology viability before adding new abstractions?▼

Deliberate growth validation requires confirming the season via forestry-state.json and probing viability through /undergrowth before planting new components into a software topology.

What is the correct workflow sequence for deliberate topology growth?▼

The deliberate growth workflow enforces a staged sequence: /prescribe → /canopy → /deadwood → /coppice → /undergrowth → /greenwood to ensure context-aware topology changes.

Can I add new growth to my topology without a prior prescription?▼

No, planting requires an explicit prescription to name the goal and a viability probe to confirm alignment, preventing unsanctioned growth within the topology.

How do I verify the season state before initiating a planting workflow?▼

You must read the forestry-state.json file to verify the current season and ensure it aligns with topology goals before executing any planting operations.

Why does topology growth require session management integration?▼

Session management integration maintains coherent identity across topology changes, ensuring that deliberate growth actions remain traceable and contextually valid throughout the workflow.

What happens if viability signals are missing before planting new growth?▼

Missing viability signals will halt the planting workflow, as the system enforces guardrails requiring explicit prescriptions and confirmed viability to prevent unsanctioned growth.