plant-growth

---
name: plant-growth
description: Plant Growth is for projects that need cultivation more than force: SEO programs, communities, product adoption, content ecosystems, or early-stage platforms. It assumes the system can grow, but only if fed in the right places and at the right pace. The spell favors compounding loops over campaign spikes.
license: CC0-1.0
---

# Plant Growth
Help a promising system thicken gradually instead of stretching thin.
## What This Skill Does
Plant Growth is for projects that need cultivation more than force: SEO programs, communities, product adoption, content ecosystems, or early-stage platforms. It assumes the system can grow, but only if fed in the right places and at the right pace. The spell favors compounding loops over campaign spikes.
In this grimoire, Plant Growth is treated as a metaphorical spell with a shipping-now delivery profile.
Canonical reference input: Plant Growth (spell).
## When To Use

- You are trying to scale adoption, reach, contribution, or traffic in an organic way.
- The work benefits from sequencing, consistency, and compounding rather than one giant push.
- You need to identify what nourishment produces durable growth.

## Prerequisites

- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.

## Procedure

1. Restate the target, the success condition, and any no-touch boundaries before taking action.
2. Map the existing roots, signals, and growth constraints in the project or ecosystem.
3. Choose a small number of nurturing interventions with compounding upside.
4. Return a cultivation plan with leading indicators, cadence, and what to prune.
5. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

## Deliverables

- A staged growth plan with compounding bets.
- A list of leading indicators worth tracking early.
- A pruning list for work that drains attention without feeding growth.

## Pitfalls / Guardrails

- Keep the metaphor anchored to a real mechanism instead of drifting into lore.
- Do not confuse vanity metrics with healthy growth.
- Avoid growth tactics that erode trust, quality, or community resilience.

## Verification

- Check that the result includes every deliverable promised above.
- Check that confirmed facts, assumptions, and inferences are visibly separated.
- Check that the metaphor still maps cleanly to a real operational mechanism.

## Example Invocation
```text
/plant-growth design a patient, compounding growth plan for this project instead of a brute-force launch tactic
```