validate-loop
Validate Loop Implementation
Check implementation status via the Skene CLI.
Agent behavior rules
- Autonomous. Run the CLI, present results, suggest next step. No mid-flow questions.
- CLI is the source of truth. If
uvx skene statusfails, report the error. Do NOT fabricate your own checklist. - User cannot type into agent terminals. Pipe safe defaults for routine prompts. Kill stuck terminals.
Steps
-
Discover CLI options Run
uvx skene status --helpto see available flags. Use only flags that appear in the output. -
Check for growth loops
ls .skene/active-loop.json 2>/dev/null || ls skene-context/growth-loops/ 2>/dev/nullIf missing: "No growth loop found. Run/skene-planfirst." Stop.
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".
2plan-growth-loop
Generate prioritized growth loops with implementation roadmaps based on codebase analysis. Use when the user says "plan", "growth loops", "prioritize", "what should I build", or "roadmap".
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