Problem
What problem this solves
Many delivery mistakes start by coding too early, before the real problem or best direction is clear.
Skill Detail
Explore a problem space before coding so you do not harden the wrong idea into implementation.
A non-coding exploration skill for clarifying ambiguity, options, and risks before the build phase starts.
Problem
Many delivery mistakes start by coding too early, before the real problem or best direction is clear.
Outcome
You get a clearer problem frame and sharper implementation options, plus a durable exploration report when the exploration is substantial or explicitly traced.
Why It Matters
This skill is useful when the urge to move fast would otherwise hide important product or architecture uncertainty.
Related Skills
Turn a fuzzy request into an implementation-ready contract before code starts mutating the repo.
The spec-writing skill for shaping non-trivial work into a clear user story, behavior contract, executable task list, and chantier history.
Open skill pageTriage a bug fast, decide whether it is safe to patch now, and route it correctly.
The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.
Open skill pageResearch a topic deeply enough that you can make a better product or GTM decision afterward.
A structured research skill for gathering evidence, checking current-source freshness, and saving reusable workflow reports.
Open skill pageGo Deeper
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.