gsd-explore
From the author
Use when the user wants to think through an idea before committing to a plan, e.g. /gsd-explore auth strategy. Runs a Socratic session, optionally spawns research, then routes output to notes, seeds, requirements, or new phases.
Install
npx skills add coco-research/coco --skill gsd-explore -a claude-code
Installs to .claude/skills/gsd-explore/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- gsd-research-phasecoco-research/cocoUse when you want phase research without planning: to investigate before deciding a phase is feasible, or to re-research after a plan already exists. Standalone command; most workflows should use /gsd-plan-phase instead.Science★ 911
- gsd-plan-phasecoco-research/cocoUse after a phase has been discussed, or when the user asks for a PLAN.md for a roadmap phase. Researches, spawns gsd-planner, verifies with gsd-plan-checker, and iterates; supports --gaps, --prd, --skip-research.Planning★ 911
- gsd:spec-phasedavepoon/buildwithclaudeSocratic spec refinement — clarify WHAT a phase delivers with ambiguity scoring before discuss-phase. Produces a SPEC.md with falsifiable requirements locked before implementation decisions begin.Planning★ 3.7K
- gsd-list-phase-assumptionscoco-research/cocoUse when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback.Planning★ 911
- brainstormcodeaholicguy/ai-devkitAI DevKit · Use when the user asks to brainstorm, ideate, generate ideas, expand options, challenge ideas, pressure-test ideas, compare concepts, narrow choices, name something, plan content angles, explore strategy, evaluate product ideas, technical approaches, experiments, or decisions.Planning★ 1.7K
- gsd-progresscoco-research/cocoUse when the user asks where the project stands, what to do next, or to resume after a break. Summarizes recent work and what is ahead, then routes to executing an existing plan or planning the next one.Planning★ 911
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in