octocode-implement

To implement features from a specification document, you parse the spec into atomic tasks, build context by mapping repository structure, and execute a risk-aware plan with research-guided coding and validation checks.

Ensuring new code matches existing patterns requires context-driven discovery and research-guided analysis using LSP and code search, minimizing blind changes before executing incremental implementation and validation phases.

A phase-gated workflow helps translate specs into working code by enforcing sequential progression through SPEC, CONTEXT, PLAN, RESEARCH, IMPLEMENT, and VALIDATE stages, ensuring traceability and adherence to documentation.

Yes, you can use a multi-agent workflow to orchestrate deep analysis and incremental code changes from a spec, coordinating tasks across research, implementation, and validation phases to maintain risk-aware execution.

Research-driven implementation requires building a mental model of the codebase first, meaning complex specifications need decomposing into atomic tasks to prevent blind changes and ensure code passes compile, lint, and test validations.

Yes, you need a detailed specification to start implementation because the workflow parses the SPEC into a TodoWrite plan, driving subsequent context discovery, risk-aware planning, and incremental coding tasks.