Skip to content

richfrem/agent-plugins-skills / plugins/agent-exploration-cycle/.apm/skills/running-exploration-cycle

running-exploration-cycle

Verified

Runs 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.

FileKindSize
SKILL.mdskill md4.6 KB
assets/exploration-dashboard.mdmarkdown1.8 KB
evals/evals.jsonconfig6.0 KB
references/acceptance-criteria.mdmarkdown2.2 KB
references/architecture.mdmarkdown6.3 KB
references/design-rationale.mdmarkdown6.3 KB
references/discovery-planning-agent.mdmarkdown4.7 KB
references/discovery-planning-tracks.mdmarkdown5.9 KB
references/discovery-planning.mdmarkdown2.4 KB
references/dispatch-strategies.mdmarkdown5.7 KB
references/domain-patterns-exploration-session.mdmarkdown3.3 KB
references/domain-patterns.mdmarkdown1.7 KB
references/environment-check.mdmarkdown1.7 KB
references/exploration-cycle-orchestrator-agent.mdmarkdown16.7 KB
references/exploration-optimizer.mdmarkdown8.9 KB
references/exploration-orchestrator-guide.mdmarkdown3.7 KB
references/exploration-session-brief.mdmarkdown2.1 KB
references/exploration-workflow.mdmarkdown2.4 KB
references/hard-gate-enforcement.mdmarkdown3.3 KB
references/high-level-process.mmdother885 B
references/intake-agent.mdmarkdown12.0 KB
references/orchestrator-loop.mmdother1.3 KB
references/post-run-survey.mdmarkdown1.7 KB
references/problem-framing-agent.mdmarkdown2.7 KB
references/process-definition.mdmarkdown3.7 KB
references/process-overview.mmdother3.7 KB
references/session-setup.mmdother1.3 KB
references/state-and-gates.mmdother1.0 KB
references/using-exploration-cycle.mdmarkdown2.3 KB
requirements-dev.inother69 B
requirements.inother60 B
scripts/check_gaps.pyscript2.5 KB
scripts/dispatch.pyexecutablescript23.6 KB
scripts/exploration_session.pyexecutablescript15.9 KB
scripts/sandbox_runner.pyscript8.7 KB
scripts/smoke_test.pyscript5.1 KB
scripts/state_engine.pyscript21.9 KB
scripts/test_dispatch_authorization_gate.pyscript4.0 KB
scripts/test_dispatch_security.pyscript10.0 KB
scripts/test_exploration_integration.pyscript14.7 KB
scripts/test_integration.pyscript4.4 KB
scripts/test_path_traversal.pyscript1.8 KB
scripts/test_phase_premium_counter.pyscript2.0 KB
scripts/test_sandbox_runner.pyscript5.6 KB
scripts/test_session_start_hook.pyscript2.4 KB
scripts/test_state_engine.pyscript13.5 KB
scripts/test_validate_phase_gate.pyscript12.7 KB
scripts/validate_phase_gate.pyexecutablescript8.7 KB

references/acceptance-criteria.md

View on GitHub
# Acceptance Criteria: running-exploration-cycle

## 1. Routing
- [ ] Triggers on exploring-an-idea requests ("let's explore this idea", "help me plan this out", "resume my exploration", "where did we leave off").
- [ ] Does not trigger for engineering build requests, or for an existing working prototype: that goes to `reengineering-vibe-code`. A mid-intake mention of existing code redirects once, with the canonical wording.
- [ ] Technical codebase discovery (refactor, bug, subsystem) goes to `handing-off-to-engineering`, not through the phases.

## 2. HARD-GATE
- [ ] No capture, prototype or handoff work starts without an SME-approved Discovery Plan (`PLAN_STATUS: APPROVED` or `## SME Approval`).
- [ ] A plan marked `## Plan Status: DRAFT` never satisfies the gate; `python3 scripts/validate_phase_gate.py 1` exits 1 for it and 0 for an approved plan.
- [ ] "Just build it" is answered with the redirect text of [hard-gate-enforcement.md](hard-gate-enforcement.md) verbatim, with no workaround offered.

## 3. State
- [ ] `python3 scripts/state_engine.py status` prints "No active exploration session" without a database and a JSON object with the session and task counts when one exists.
- [ ] The dashboard is treated as a read-only projection of the state engine; a gate is never passed from conversation memory.
- [ ] An in-progress session is resumed at its active phase, with a short plain-language recap first.

## 4. Intake and brief
- [ ] The brief is written to `exploration/session-brief.md` using the canonical headers in order; unfilled fields carry `[INTAKE DRAFT — confirm]` or `[NEEDS HUMAN INPUT]`.
- [ ] The expert's own phrasing of the trigger is preserved verbatim.

## 5. Conduct
- [ ] One question per message, in business language: none of the jargon listed in [design-rationale.md](design-rationale.md).
- [ ] Each phase ends at its gate with a plain summary and the outcome path; completion is recorded only after a clear yes and a passing `validate_phase_gate.py <phase>`.
- [ ] No model IDs, prices or runtime flags are named; model and runtime choices are left to the `cli-agent` skill.

## 6. Code
- [ ] `python3 -m pytest scripts -q` passes from the skill folder.
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall