Research

Research open questions from a PRD or a user-provided set of questions. Categorize each question, spawn parallel research subagents for investigatable items, synthesize findings, and update the PRD.

This skill resolves unknowns where the answer exists somewhere and needs to be found — prior art, external constraints, codebase patterns, competitive landscape. For unknowns about visual design, UX, or interaction feel, use iterative:design-exploration instead.

When to Use

• After iterative:brainstorming produces a PRD with open questions that can be answered through research
• When the user has specific questions to investigate before planning
• When scope, requirements, or direction questions need answers before tech planning can proceed
• Can be invoked standalone with a list of questions (no PRD required)

Key Principles

1. Categorize before investigating — Not all questions belong here. Technical implementation questions (how to query X, which API to use) belong in tech planning's codebase exploration. Questions about visual design or interaction feel belong in iterative:design-exploration. This skill handles scope, requirements, external research, and prior art questions.
2. Parallel research — Spawn independent research subagents for each question. Questions are typically unrelated and benefit from concurrent investigation.
3. Update the source of truth — When a PRD exists, findings should update it directly. Answered questions move out of Open Questions; new constraints become requirements.
4. Present before committing — Show findings and proposed PRD changes to the user for approval before updating the document.