undergrowth

Name: undergrowth
Availability: InStock
Author: jdhayesbc

okay, here's your response: { ... }

1|Updated Dec 28, 2025

Search Tags:#investigation #codebase #pattern #probe #undergrowth #wild

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and surfaces growth—planned and emergent—within a software project to guide architecture, refactoring, and long-term maintainability decisions.

Core Features & Use Cases

Deliberate feasibility spikes before significant work (probe mode) to validate the approach.
Organic discovery (wild mode) to surface patterns that arise without explicit planning.
Structured documentation workflow that records findings in forestry-state.json and routes next steps through the forestry sequence (/prescribe → /canopy → /undergrowth → /greenwood or /deadwood).

Quick Start

Initiate an undergrowth probe on the target codebase to surface both planted and emergent patterns.

Frequently Asked Questions about undergrowth

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

FAQPage Schema

How do I identify growth patterns in a software codebase before committing to a major refactor?▼

Surface growth patterns in a codebase by running a feasibility spike using probe mode, which deliberately validates your approach and identifies both planned and emergent structures before significant work begins.

What is the difference between planned and emergent codebase patterns?▼

Planned codebase patterns are deliberately validated through probe mode feasibility spikes, while emergent patterns are organic discoveries surfaced using wild mode to identify structures that arose without explicit planning.

How do I document codebase pattern findings to guide long-term architecture decisions?▼

Document codebase pattern findings in a structured forestry-state.json file, which records both deliberate and organic discoveries to coordinate the forestry workflow and guide future architecture and maintainability decisions.

Can I use this pattern investigation workflow without any external dependencies?▼

Yes, you can execute this codebase pattern investigation workflow without external dependencies, as it relies entirely on internal structured protocols and local file documentation rather than third-party libraries.

When should I route my codebase investigation results to greenwood versus deadwood?▼

Route your codebase investigation results to greenwood to proceed with healthy viable patterns, or to deadwood when the surfaced patterns indicate non-viable growth, determining the next step in the forestry workflow sequence.

What is the best way to discover unplanned architectural patterns during a software project investigation?▼

The best way to discover unplanned architectural patterns is to apply wild mode, which surfaces emergent software growth patterns that were not explicitly planned, helping you understand organic project evolution.