explore-idea
Explore Idea
Scope and Entry
Explore whether a problem deserves work and what outcome is worth pursuing. This is an explicitly chosen standalone workflow, not an automatic replacement for a repository's lifecycle. If the choice conflicts with an established process, ask which to use before creating competing artifacts. Do not silently migrate assets.
Entry points are optional. Settled requirements can go to slice-work; a clear,
small change can go directly to design-change. Reuse accepted decisions instead
of restarting discovery. Recommend these entry points without invoking them.
This phase produces no production code. An experiment needs separate, explicit authorization of its question, bounds, effects, and stopping condition. Exploration does not authorize commits, pushes, deployments, or new dependency installation.