Explore

Explore a task or design through systematic questions until reaching shared understanding.

If an issue number is given, fetch it with gh issue view $ARGUMENTS and use it as the starting point.

Ask me questions one at a time about this task until we have a shared understanding of what to build. Walk through each decision branch, resolving dependencies in order. For each question, provide your recommended answer based on the codebase.

If a question can be answered by reading the code, read the code instead of asking.

See also

• plan for formal task breakdown once scope is clear
• build for execution after alignment

Red flags

• Asking questions answerable from the codebase
• Jumping into implementation before decisions are clear