gsd-explore

Guide Socratic ideation and route ambiguous ideas into GSD artifacts.

264|11|Updated Apr 25, 2026
One-click install
npx skills add https://github.com/coco-research/coco --skill gsd-explore-coco-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-explore
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-explore
Command: npx skills add https://github.com/coco-research/coco --skill gsd-explore-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you explore an uncertain idea before committing to a plan, reducing rushed decisions and vague requirements.

Core Features & Use Cases

  • Socratic Ideation: Uses probing questions to clarify goals, constraints, risks, and assumptions.
  • Research-Aware Exploration: Can optionally branch into research when an idea needs evidence before moving forward.
  • Artifact Routing: Directs the outcome into the right GSD output such as notes, todos, seeds, research questions, requirements, or a new phase.
  • Use Case: A developer can use it to pressure-test an authentication strategy, compare implementation options, and turn the discussion into an actionable next step.

Quick Start

Use the gsd-explore skill to guide a Socratic session about authentication strategy and route the outcome into the right GSD artifacts.

Frequently Asked Questions about gsd-explore

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn vague ideas into clear next steps during early planning?

Socratic ideation transforms vague ideas into clear next steps by probing goals, constraints, and assumptions, then routing outcomes into structured artifacts like notes, todos, or requirements to prevent rushed planning decisions.

What is the best way to brainstorm and pressure-test an implementation strategy?

Research-assisted brainstorming pressure-tests implementation strategies by using probing questions to compare options and optionally spawning research tasks. It helps evaluate risks and assumptions before committing to a specific technical path or generating structured deliverables.

How do I decide whether planning outputs should become todos, requirements, or research questions?

Workflow-aware routing decides whether planning outputs become todos, requirements, research questions, or new phases based on the Socratic session's outcome. It evaluates the clarified idea's constraints and goals to direct deliverables into the correct artifact type.

Can I use Socratic questioning to explore an idea before committing to a project plan?

Yes, Socratic questioning explores ideas before project commitment by clarifying ambiguous goals and identifying risks. It optionally branches into evidence gathering to validate assumptions, ensuring you only commit to a plan with clear, structured requirements.

When should I not use Socratic ideation for brainstorming sessions?

Socratic ideation is not suited for brainstorming sessions with fully defined requirements or clear implementation paths. It targets ambiguous ideas needing goal clarification and risk assessment, making it redundant for straightforward tasks lacking early planning uncertainty.