Validate season and prescription before planting deliberate growth in a topology.
npx skills add https://github.com/JDHayesBC/Awareness --skill greenwood
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
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.
After /prescribe names the goal and /undergrowth probe confirms viability, run the planting step to add deliberate growth.
High-intent search queries and answers about installing and using this skill.
Deliberate growth validation requires confirming the season via forestry-state.json and probing viability through /undergrowth before planting new components into a software topology.
The deliberate growth workflow enforces a staged sequence: /prescribe → /canopy → /deadwood → /coppice → /undergrowth → /greenwood to ensure context-aware topology changes.
No, planting requires an explicit prescription to name the goal and a viability probe to confirm alignment, preventing unsanctioned growth within the topology.
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.
Session management integration maintains coherent identity across topology changes, ensuring that deliberate growth actions remain traceable and contextually valid throughout the workflow.
Missing viability signals will halt the planting workflow, as the system enforces guardrails requiring explicit prescriptions and confirmed viability to prevent unsanctioned growth.
JDHayesBCokay, here's your response: { ... }
syhyaAutomate versioning, topology validation, and git tagging for FlashInfer contest submissions.
rolopez23Review staged code diffs and apply conservative refactors with human sign-off.
picmakproEstablish and maintain structured planning documentation for non-development labs.
