implement

Coordinate coding tasks through five disciplined practices in Octopus.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill implement-leocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/leocosta/octopus/tree/main/skills/implement
Command: npx skills add https://github.com/leocosta/octopus --skill implement-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates a disciplined, repeatable coding workflow inside Octopus to replace ad-hoc coding with a structured, auditable process that aligns code changes with quality gates and reviews.

Core Features & Use Cases

  • Implements the five practices: TDD loop, plan-before-code, verification-before-completion, simplify pass, and commit cadence, applied automatically to code edits.
  • Works alongside existing rules/common/* and doc-lifecycle to coordinate code, docs, and reviews without duplicating rules.
  • Supports engagement on feature work, bug fixes, and refactors while maintaining safe, incremental commits and traceable decisions.

Quick Start

Start a code task and follow the five practices—TDD loop, plan-before-code, verification-before-completion, simplify pass, and commit cadence—to guide the change from intention to verified delivery.

Frequently Asked Questions about implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a TDD workflow for code edits in Octopus?▼

To enforce a TDD workflow for code edits, this skill coordinates the TDD loop alongside plan-before-code, verification, and commit cadence practices. It automatically guides feature work and refactors to deliver verified, reviews-ready code changes.

What is the best way to structure code tasks for bug fixes and refactors?▼

The best way to structure code tasks for bug fixes and refactors is applying five practices: TDD loop, plan-before-code gate, verification-before-completion, simplify pass, and commit cadence. This ensures safe, incremental commits and traceable decisions.

How does a plan-before-code gate improve code verification?▼

A plan-before-code gate improves code verification by requiring intention validation before implementation starts. It coordinates with rules and doc-lifecycle to align code changes with quality gates, ensuring verifiable and reviews-ready task delivery.

Can I use this workflow coordination for feature work across different languages?▼

Yes, you can use this workflow coordination for feature work across different languages. It applies to most coding tasks and contexts automatically, guiding changes from intention to verified delivery without duplicating existing rules.

Does this coding workflow duplicate existing rules and documentation processes?▼

No, this coding workflow does not duplicate existing rules and documentation processes. It works alongside rules/common and doc-lifecycle to coordinate code, docs, and reviews, orchestrating a structured process without overlapping rule definitions.

Why should I use a structured coding workflow instead of ad-hoc code edits?▼

You should use a structured coding workflow instead of ad-hoc code edits to replace unstructured changes with a disciplined, auditable process. It aligns code changes with quality gates and reviews, maintaining safe incremental commits and traceable decisions.