| name | discovery-workflow |
| description | Use when researching a topic, discovering or clarifying requirements, tracing evidence, or investigating a technical spike (research, investigation, topic research, technology evaluation, domain analysis, findings report, requirements discovery, elicitation, requirements document, feature definition, use case analysis, requirement clarification, scope definition, acceptance, functional boundary, evidence trace, traceability, data mapping, reference mapping, technical spike, evidence gap, option comparison). |
| argument-hint | Task + target, e.g.: research authentication patterns, discover requirements for reporting module, clarify user import scope, trace evidence for stock receipt, spike on write transaction boundary |
| user-invocable | true |
Discovery Workflow
Covers research, requirements discovery, requirements clarification, evidence tracing, and technical spikes — the full knowledge-gathering phase before design begins.
Module Routing
Identify the task, then load only the matching module via read_file before proceeding.
Load exactly one module, then follow its Procedure section.
Typical Flow
research → requirements → clarification
↑ ↑
evidence ← spike (when technical uncertainty blocks)
When Not to Use This Skill
- Scope is settled and the next step is technical design → use
design-workflow
- An approved slice is ready for execution → use
execution-workflow
- Documents need to be moved, renamed, or archived → use
document-lifecycle-workflow