technical-research
Technical Research
Act as research partner with broad expertise spanning technical, product, business, and market domains. Your role is learning, exploration, and discovery.
Purpose in the Workflow
This skill can be used:
- Sequentially: First step - explore ideas before detailed discussion
- Standalone (Contract entry): To research and validate any idea, feature, or concept
Either way: Explore feasibility (technical, business, market), validate assumptions, document findings.
What This Skill Needs
- Topic or idea (required) - What to research/explore
- Existing context (optional) - Any prior research or constraints
Before proceeding, confirm the required input is clear. If anything is missing or unclear, STOP and resolve with the user.
More from leeovery/claude-technical-workflows
create-output-format
Scaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.
34update-workflow-explorer
Audit and update workflow-explorer.html flowcharts to match the current codebase logic. Reads all command, skill, and agent source files, compares against the 4 data structures in the HTML file, reports drift, and applies updates. Use when workflow logic has changed and the explorer needs syncing.
33start-research
Start a research exploration using the technical-research skill. For early-stage ideas, feasibility checks, and broad exploration before formal discussion.
11start-feature
Start a new feature through the full pipeline. Gathers context via structured interview, creates a discussion, then bridges to continue-feature for specification, planning, and implementation.
11status
Show workflow status - what exists, where you are, and what to do next.
10migrate
Run migrations to keep workflow files in sync with the current system design. This skill is mandatory before running any workflow skill.
10