
Gsd Explore
- 1 installs
- Updated May 10, 2026
- diisk/libery.wallet
Runs a Socratic ideation session that explores an idea through probing questions, then routes the outcomes into GSD planning artifacts.
About
Guides a developer through open-ended ideation using probing questions, optionally spawning research, before committing to a plan. It routes results into GSD artifacts like notes, todos, requirements or new phases. A developer uses it to think an idea through before planning.
- Socratic ideation session that probes an idea through questions
- Routes outputs to GSD artifacts: notes, todos, seeds, research questions, requirements or phases
Gsd Explore by the numbers
- 1 all-time installs (skills.sh)
- Ranked #2,478 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Jul 8, 2026 (Skillselion catalog sync)
npx skills add https://github.com/diisk/libery.wallet --skill gsd-exploreAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1 |
|---|---|
| Last updated | May 10, 2026 |
| Repository | diisk/libery.wallet ↗ |
What it does
Runs a Socratic ideation session that explores an idea through probing questions, then routes the outcomes into GSD planning artifacts.
Files
<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 (Execute mode), present a plain-text numbered list and pick a reasonable default.
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 .toml at install time so model_overrides from .planning/config.json and ~/.gsd/defaults.json are honored automatically by Codex's agent router.
fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
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>
<objective> Open-ended Socratic ideation session. Guides the developer through exploring an idea via probing questions, optionally spawns research, then routes outputs to the appropriate GSD artifacts (notes, todos, seeds, research questions, requirements, or new phases).
Accepts an optional topic argument: $gsd-explore authentication strategy </objective>
<execution_context> @C:/repositorios/libery.wallet/.codex/get-shit-done/workflows/explore.md </execution_context>
<process> Execute the explore workflow from @C:/repositorios/libery.wallet/.codex/get-shit-done/workflows/explore.md end-to-end. </process>