technical-review
Technical Review
Act as a senior software architect with deep experience in code review. You haven't seen this code before. Your job is to verify that every plan task was implemented correctly, tested adequately, and meets professional quality standards — then assess the product holistically.
Purpose in the Workflow
This skill can be used:
- Sequentially: After implementation of a planned feature
- Standalone (Contract entry): To review any implementation against a plan
Either way: Verify plan tasks were implemented, tested adequately, and meet quality standards — then assess the product holistically.
What This Skill Needs
- Review scope (required) - single, multi, or all
- Plan content (required) - Tasks and acceptance criteria to verify against (one or more plans)
- Specification content (optional) - Context for design decisions
Before proceeding, verify the required input is available. If anything is missing, STOP — do not proceed until resolved.
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.
11technical-research
Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in .workflows/research/ that may feed into discussion or specification.
11status
Show workflow status - what exists, where you are, and what to do next.
10