richfrem/agent-plugins-skills / plugins/agent-exploration-cycle/.apm/skills/running-exploration-cycle
running-exploration-cycle
VerifiedRuns the business exploration cycle end to end: starts or resumes a session (intake interview, session brief), enforces the Discovery Plan HARD-GATE, routes the four phases (Discovery Plan, Visual Blueprinting, Prototype, Handoff) to the sibling skills and keeps session state. Use when the user says "let's explore this idea", "I have an idea I want to explore", "help me plan this out", "start discovery", "resume my exploration", "where did we leave off", or starts any conversation about a need, problem or idea before building. Not for hardening an existing prototype (use reengineering-vibe-code) or for engineering build work.
Running the Exploration Cycle
Front door and conductor of the exploration plugin. Process: process-overview.mmd and process-definition.md.
Contents
Constraints
- HARD-GATE: no capture, prototype or handoff work until the SME has approved the Discovery Plan (
PLAN_STATUS: APPROVEDor## SME Approval); a DRAFT never counts. Use the redirect in hard-gate-enforcement.md verbatim, offer no workaround. - State: the SQLite state engine is authoritative;
exploration/exploration-dashboard.mdis a read-only projection. Never rely on conversation memory for a gate. If you were dispatched as a subagent, skip this skill. - One question at a time, in the SME's business language (no git, branch or subagent jargon).
- Routing: an existing working prototype goes to
reengineering-vibe-code; technical codebase discovery goes tohanding-off-to-engineering. - Models: never name models or prices here; choose runtime and model through the
cli-agentskill.
Quick start
Run from this skill's folder, with CLAUDE_PROJECT_DIR set to the project:
python3 scripts/state_engine.py status
python3 scripts/validate_phase_gate.py 1
python3 scripts/check_gaps.py --files exploration/captures/brd-draft.md --threshold 3
Workflow
- Resume check: run
status; an in-progress session continues at its active phase (using-exploration-cycle.md). - Phase 0 Intake: interview, classify, write
exploration/session-brief.md(intake, brief); pick session type and dispatch (session-setup.mmd, dispatch). - Phase 1 Discovery Plan: discovery-planning.md and tracks; then the capture loop in
capturing-business-requirements. - Phases 2 and 3: hand to
building-interactive-prototypes. Phase 4: hand tohanding-off-to-engineering. - Each phase ends at its gate (state-and-gates.mmd); wait for the SME, then run the validator for that phase.
Verification
python3 scripts/validate_phase_gate.py <phase> # 1 to 4
python3 -m pytest scripts -q
Acceptance criteria: acceptance-criteria.md.
References
- Process: process-definition.md • orchestrator-loop.mmd • high-level-process.mmd • design-rationale.md (read to know why the loop halts where it does)
- Entry and state: exploration-workflow.md • exploration-orchestrator-guide.md • environment-check.md
- Phase 0 and 1: problem-framing-agent.md • discovery-planning-agent.md • exploration-cycle-orchestrator-agent.md (CLI-dispatch director)
- Seed template: exploration-dashboard.md
- Quality: architecture.md (artifact markers) • post-run-survey.md • domain-patterns.md and exploration-session patterns (known failures and escapes) • exploration-optimizer.md (retired loop, use
os-lab)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 469k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |