explore
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
planfor formal task breakdown once scope is clearbuildfor execution after alignment
Red flags
- Asking questions answerable from the codebase
- Jumping into implementation before decisions are clear
- Treating assumptions as confirmed facts
More from cniska/skills
plan
Design a feature or behavior change through dialogue. Use when asked to plan, scope, design, or break down work before coding.
9debug
Debug systematically with structured triage. Use when tests fail, builds break, or runtime behavior doesn't match expectations.
7security-audit
Audit security risks, trust boundaries, and unsafe defaults. Use when reviewing security posture or assessing risk before release.
5arch-audit
Audit architecture, boundaries, and design consistency. Use when reviewing module boundaries, extension seams, or contract drift.
5git
Manage commits, branches, and change history. Use when committing, branching, or managing version control.
4docs
Review docs for drift, missing updates, and terminology changes. Use when code changes should be reflected in documentation.
4