technical-implementation
Technical Implementation
Orchestrate implementation by dispatching executor and reviewer agents per task. Each agent invocation starts fresh — flat context, no accumulated state.
- Executor (
../../agents/implementation-task-executor.md) — implements one task via strict TDD - Reviewer (
../../agents/implementation-task-reviewer.md) — independently verifies the task (opus)
The orchestrator owns: plan reading, task extraction, agent invocation, git operations, tracking, task gates.
Purpose in the Workflow
This skill can be used:
- Sequentially: To execute a plan created by technical-planning
- Standalone (Contract entry): To execute any plan that follows plan-format conventions
Either way: dispatch agents per task — executor implements via TDD, reviewer verifies independently.
What This Skill Needs
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