plan-growth-loop
Plan Growth Loop
Generate prioritized growth loops from the Skene CLI. The CLI does the planning, not you.
Agent behavior rules
- Autonomous. Run the CLI, present results, suggest next step. No mid-flow questions unless there's a genuine blocker.
- CLI is the source of truth. If
uvx skene planfails, report the error. Do NOT generate your own growth loops. - User cannot type into agent terminals. Pipe safe defaults for routine prompts. Kill stuck terminals and re-run.
Steps
-
Discover CLI options Run
uvx skene plan --helpto see available flags. Use only flags that appear in the output. -
Verify analysis exists
ls .skene/analysis/ 2>/dev/null || ls skene-context/ 2>/dev/nullIf missing: "Run/skene-analyzefirst." Stop. -
Generate growth plan Run
uvx skene planwith appropriate flags from --help output. If it fails, report error. Do NOT make up growth loops. -
Present CLI output Read results from
.skene/plans/orskene-context/growth-loops/and present loops by priority. -
Help user choose Ask which loop to implement — this is the one genuine decision point.
-
Store selection Use the appropriate CLI flag from --help to store the selection (e.g.
--select). If the command prompts for input, pipe the answer. If no select flag exists, write to.skene/active-loop.jsondirectly. -
Next step "Run
/skene-buildto generate the implementation plan."
Error handling
- CLI failure: Report error, suggest fix. Do NOT fabricate growth loops.
- Permission errors: Give user the command for their terminal.
Output
Loops found, selection stored, next step (/skene-build).
More from skenetechnologies/skene
deploy-telemetry
Set up analytics and tracking infrastructure for growth loops. Use when the user says "deploy telemetry", "set up analytics", "tracking", "events", "push to supabase", or "skene push".
2validate-loop
Check if growth loop requirements are actually implemented in the codebase. Use when the user says "validate", "check status", "skene status", "is it done", or "verify implementation".
2analyze-codebase
Run comprehensive PLG analysis on a codebase to detect tech stack, existing growth features, and revenue opportunities. Use when the user says "analyze", "scan", "audit codebase", or "find growth opportunities".
2build-implementation
Generate context-aware implementation prompts for a selected growth loop. Use when the user says "build", "implement", "generate code", "create prompt", or "how do I build this".
2initialize-config
Set up Skene configuration for a project. Use when starting a new PLG analysis, when .skene.config is missing, or when the user says "skene init", "set up skene", or "configure skene".
2