gsd-explore
Facilitates structured idea exploration and Socratic questioning before project execution.
Install
mkdir -p .claude/skills/gsd-explore-electroheadfx && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18704" && unzip -o skill.zip -d .claude/skills/gsd-explore-electroheadfx && rm skill.zipInstalls to .claude/skills/gsd-explore-electroheadfx
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Socratic ideation and idea routing — think through ideas before committing to plansKey capabilities
- →Guide developers through open-ended Socratic ideation sessions
- →Route outputs to GSD artifacts like notes, todos, or requirements
- →Translate `AskUserQuestion` to `request_user_input` for user interaction
- →Translate `Task(...)` to `spawn_agent` for sub-agent collaboration
- →Handle `request_user_input` rejections by presenting questions as a plain-text list
How it works
The skill guides a developer through an open-ended Socratic ideation session by asking probing questions and optionally spawning research. It then routes the resulting outputs to appropriate GSD artifacts.
Inputs & outputs
When to use gsd-explore
- →Ideation and brainstorming
- →Validating project concepts
- →Socratic refinement of requirements
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-explore. - Treat all user text after
$gsd-exploreas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected or unavailable, you MUST stop and present the questions as a plain-text numbered list, then wait for the user's reply. Do NOT pick a default and continue (#3018). - You may only proceed without a user answer when one of these is true:
(a) the invocation included an explicit non-interactive flag (
--autoor--all), (b) the user has explicitly approved a specific default for this question, or (c) the workflow's documented contract says defaults are safe (e.g. autonomous lifecycle paths). - Do NOT write workflow artifacts (CONTEXT.md, DISCUSSION-LOG.md, PLAN.md, checkpoint files) until the user has answered the plain-text questions or one of (a)-(c) above applies. Surfacing the questions and waiting is the correct response — silently defaulting and writing artifacts is the #3018 failure mode.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit.spawn_agenthas no inlinemodelparameter; GSD embeds the resolved per-agent model directly into each agent's.tomlat install time somodel_overridesfrom.planning/config.jsonand~/.gsd/defaults.jsonare honored automatically by Codex's agent router.fork_context: falseby default — GSD agents load their own context via<files_to_read>blocksTask(isolation="worktree")/Agent(isolation="worktree")→ no direct Codex mapping. Codexspawn_agentdoes not create or bind a git worktree automatically. Workflows that require this isolation must fail closed or use an explicit manual worktree protocol before spawning (#3360).
Spawn restriction:
- Codex restricts
spawn_agentto cases where the user has explicitly requested sub-agents. When automatic spawning is not permitted, do the work inline in the current agent rather than attempting to force a spawn.
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
Accepts an optional topic argument: $gsd-explore authentication strategy
</objective>
<execution_context> @/Users/lmarques/Dev/efx-mux/.codex/get-shit-done/workflows/explore.md </execution_context>
<process> Execute end-to-end. </process>When not to use it
- →When a workflow requires automatic git worktree creation or binding for isolation
Limitations
- →Codex `spawn_agent` does not create or bind a git worktree automatically
- →Codex restricts `spawn_agent` to cases where the user has explicitly requested sub-agents
- →The skill cannot proceed without a user answer unless specific non-interactive flags are set, user approval for defaults exists, or workflow contracts allow defaults
How it compares
This workflow uses Socratic questioning and structured routing to GSD artifacts, unlike a manual brainstorming session that might lack guided exploration or automated output organization.
Compared to similar skills
gsd-explore side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-explore (this skill) | 0 | 2mo | No flags | Beginner |
| product-manager-toolkit | 32 | 7mo | Review | Beginner |
| task-analyzer | 7 | 1mo | No flags | Beginner |
| micro-saas-launcher | 6 | 6mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by electroheadfx
View all by electroheadfx →You might also like
product-manager-toolkit
davila7
Comprehensive toolkit for product managers including RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, and go-to-market strategies. Use for feature prioritization, user research synthesis, requirement documentation, and product strategy development.
task-analyzer
shinpr
Metacognitive task analysis and skill selection. Analyzes task essence, estimates scale, and returns appropriate skills with metadata.
micro-saas-launcher
davila7
Expert in launching small, focused SaaS products fast - the indie hacker approach to building profitable software. Covers idea validation, MVP development, pricing, launch strategies, and growing to sustainable revenue. Ship in weeks, not months. Use when: micro saas, indie hacker, small saas, side project, saas mvp.
game-changing-features
davila7
Find 10x product opportunities and high-leverage improvements. Use when user wants strategic product thinking, mentions '10x', wants to find high-impact features, or says 'what would make this 10x better', 'product strategy', or 'what should we build next'.
job-search-strategist
proyecto26
Comprehensive job search strategy skill for analyzing job postings, discovering non-obvious insights, conducting conversational skills-matching interviews, identifying skill development needs, and creating creative, personalized application strategies. This skill should be used when users want help with job applications, career transitions, analyzing job opportunities, or developing targeted job search approaches that help them stand out from other candidates.
challenge
alirezarezvani
/em -challenge — Pre-Mortem Plan Analysis