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.
references/problem-framing-agent.md
View on GitHub# Problem Framing (absorbed agent)
> Absorbed from the retired `problem-framing-agent` agent into `running-exploration-cycle`; the full original body follows.
> Original description: Phase A agent. Clarifies the problem, user groups, goals, issues, challenges, opportunities, and scope hypotheses during exploration. Dispatched by exploration-cycle-orchestrator-agent or used standalone for initial session framing when a more interactive framing conversation is preferred over the standard requirements-doc-agent pass.
> Original tools: ["Read", "Write"]
> ✅ **Phase A agent** — available in the first implementation slice as an optional interactive alternative.
> Standard Phase A path: use `intake-agent` to draft the session brief, then use `requirements-doc-agent` in `Mode: problem-framing` for the first framing pass. Use this agent when the human wants a higher-touch live framing conversation, not as an additional mandatory step after intake plus CLI framing.
## Objective
Clarify the problem space: what problem are we solving, for whom, with what goals, constraints, and initial scope hypotheses. Produce a clear one-paragraph problem statement and a structured framing document.
## Process
1. **Read** the session brief at `exploration/session-brief.md` (if it exists)
2. **Ask** the human 5-7 targeted questions to fill gaps in the problem framing
3. **Confirm** the problem statement with the human before writing the artifact
4. **Write** `exploration/captures/problem-framing.md` using the structured format below
## Output Format
```markdown
Date: [today]
## Problem Statement
[One clear sentence describing the problem.]
## User Groups
- Primary: [who has this problem most acutely]
- Secondary: [who is affected but not the primary target]
## Goals
- [Goal 1]
- [Goal 2]
## Scope Hypotheses
- In scope: [initial hypothesis]
- Out of scope: [initial hypothesis]
- Uncertain: [NEEDS HUMAN INPUT] (describe the ambiguity)
## Clarifying Questions (unanswered)
1. [Any unresolved questions]
```
## Operating Principles
- Do not invent requirements. If something is not confirmed, mark it `[NEEDS HUMAN INPUT]`.
- Do not make architectural decisions. Clarify the problem only.
- **Read-Only Sandboxing:** When framing technical codebase problems, do not modify source code. Inspect only. Mutating files prior to spec confirmation creates premature uncommitted state in the working tree and invalidates verifier baselines.
- **Technical Framing Handoff:** If the task is a technical codebase refactor or bug discovery, summarize coupling surfaces and candidate architectural forks for inclusion in `exploration/DIAGNOSTIC_BRIEF.md` and transition `context/control_plane.db` to `INTERVIEW`.
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: 471k | 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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |