Menu
Use when starting any conversation - establishes how to find and follow the business exploration workflow.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | using-exploration-cycle |
| description | Use when starting any conversation - establishes how to find and follow the business exploration workflow. |
Before responding to ANY user message (including answering general questions or scoping requests), you MUST verify the state of the active exploration session. If a session is in progress, you DO NOT have a choice: you MUST route execution through the active phase of the exploration-workflow.
Before generating any response:
exploration/exploration-dashboard.md exists.**Status:** field.Complete, the prior session has ended. You may answer normally or offer to start a new exploration.In Progress or TBD, identify the **Current Phase:**.exploration-workflow skill. Never directly invoke child skills unless authorized by the orchestrator. Do NOT answer the user's question directly in freeform prose.exploration-workflow skill to initiate Phase 0 intake.The SQLite state database and programmatic phase artifacts are the absolute state authority. The markdown dashboard is a read-only projection of the database. Do not rely on conversational chat history to assume a phase is complete or that a gate has been passed.
When executing the workflow or waiting for sub-agent execution / task completions:
(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.
(Industry standard: Sequential Agent / Agent as a Tool) Primary Use Case: Delegating a well-defined task to a worker agent, verifying its execution, and repeating if necessary. Inner/outer agent delegation pattern. Use when: work needs to be delegated from a strategic controller (Outer Loop) to a tactical executor (Inner Loop) via strategy packets, with verification and correction loops.
(Industry standard: Loop Agent / Single Agent) Primary Use Case: Self-contained research, content generation, and exploration where no inner delegation is required. Self-directed research and knowledge capture loop. Use when: starting a session (Orientation), performing research (Synthesis), or closing a session (Seal, Persist, Retrospective). Ensures knowledge survives across isolated agent sessions.
(Industry standard: Routing Agent / Orchestrator Pattern) Primary Use Case: Analyzing an ambiguous trigger and routing it to one of the specific specialized implementations. Routes triggers to the appropriate agent-loop pattern. Use when: assessing a task, research need, or work assignment and deciding whether to run a simple learning loop, red team review, dual-loop delegation, or parallel swarm. Manages shared closure (seal, persist, retrospective, self-improvement).
(Industry standard: Review and Critique Pattern) Primary Use Case: Iterative generation paired with adversarial review, continuing until an 'Approved' verdict is reached. Orchestrated adversarial review loop. Use when: research, designs, architectures, or decisions need to be reviewed by red team agents (human, browser, or CLI). Iterates in rounds of research → bundle → review → feedback until approved.
(Industry standard: Meta-Learning System / Automated Autoresearch) Primary Use Case: Continuous, self-improving orchestration of an agentic system over multiple sessions. Use when: building a continuous improvement layer that autonomously identifies workflow friction, postulates hypotheses, and tests improved instructions/coding skills against an objective headless benchmark before merging and persisting.