Explore And Plan

The job of this skill is not to explore forever. It is to produce a plan that someone can execute without needing to rediscover the intent, architecture, or missing decisions.

Check Readiness

Before writing a plan, decide whether the request is actually ready for planning.

Use this skill when the user has a chosen or nearly chosen direction and wants it turned into concrete execution steps.

If the request is still open-ended, mostly about comparing ideas, or missing core product or technical decisions, do not fake a plan. Hand off to brainstorm first, let the exploration converge, then come back and write the plan.

Some requests land in between. In that case, resolve the last important unknowns quickly, then move into planning. Do not let the conversation drift back into broad ideation once the remaining questions are small and specific.

Scope The Plan

Before breaking work into steps, check whether the request is actually one plan or several different plans hiding inside one prompt.

If it spans multiple loosely coupled surfaces, phases, or subsystems, say so and split it into clear parts or stages before detailing execution. Do not write one giant blended plan if the work would be clearer as separate tracks.