explore

Explore

You are tasked with analyzing solution options for new features or changes by invoking parallel skills and synthesizing their findings into actionable recommendations optimized for design consumption.

Input

$ARGUMENTS — feature/change description, optionally with paths to tickets or research docs.

Metadata

node "${SKILL_DIR}/../_shared/now.mjs"
echo
node "${SKILL_DIR}/../_shared/git-context.mjs"

Copy values verbatim — do not reformat the timezone offset.

Flow

1. Input → 2. Generate candidates → 3. Candidate checkpoint → 4. Per-candidate fit → 5. Synthesize → 6. Metadata → 7. Write doc → 8. Present → 9. Follow-ups

The final artifact feeds design.

Steps

Step 1: Input Handling

1. No argument provided — respond with:

   I'm ready to research solution options. Please provide:
   - What feature/change you want to explore
   - Any requirements or constraints you know about
   - Reference to relevant ticket or research documents if available
   
   I'll analyze the current codebase, generate solution options, and provide recommendations.
   

   Then wait for the user's request.

2. Read any files mentioned — tickets, research docs, related artifacts:

   • Read them FULLY first using the Read tool WITHOUT limit/offset parameters
   • Read these files in main context before invoking skills
   • Extract requirements, constraints, and goals
   • Identify what problem we're solving

Step 2: Generate Candidates and Dimensions

Generate 2–4 named candidates from three sources, then merge into one shortlist:

• Ecosystem scan — spawn web-search-researcher for any topic where the candidate space includes external libraries, frameworks, or services. Prompt it to return 2–4 named options with one-line "what it is" + canonical doc link per option. Skip only when the topic is wholly internal (e.g., "how to organize this service layer") and the orchestrator's design-space enumeration plus the user shortlist already cover the space.
• Design-space enumeration — orchestrator names abstract shapes from first principles when applicable (pub/sub vs direct-call vs event-bus; sync vs async; manual mapping vs auto-mapper). One-line "what it is" per shape.
• User shortlist — if the user pre-named candidates in the entry prompt ("compare TanStack Query vs SWR"), include those verbatim.