speckit.implement

Execute Speckit implementation tasks from tasks.md using a TDD workflow.

2|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.implement
Source: https://github.com/lofidonut3/oh-my-speckit/tree/main/skills/speckit.implement
Command: npx skills add https://github.com/lofidonut3/oh-my-speckit --skill speckit-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the execution of the Speckit implementation workflow by processing and running all tasks defined in tasks.md, enabling a repeatable, test-driven feature delivery.

Core Features & Use Cases

  • Automated Task Execution: Reads tasks.md and plan.md, executes tasks in sequence using a TDD approach, and marks completed tasks.
  • OpenCode Command Processing: Loads and processes the .opencode/commands/speckit.implement.md file, applying syntax transformations like $ARGUMENTS, $1, @filepath, and !command.
  • Workflow Integrity: Enforces prerequisites, loads design documents, and ensures tasks progress through phases from plan to verification.

Quick Start

Run the speckit.implement command to execute the official implementation workflow for your project. If the primary command file is missing, check the legacy path .opencode/command/speckit.implement.md or ensure .opencode/commands/speckit.implement.md exists.

Frequently Asked Questions about speckit.implement

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

FAQPage Schema
How do I automate TDD task execution from a tasks.md file?

Automate TDD task execution by processing tasks.md in sequence, running each task iteratively, and marking completed items to ensure repeatable test-driven feature delivery.

What is the OpenCode command file syntax for processing variables and file paths?

OpenCode command file syntax supports specific transformations including $ARGUMENTS, $1 for variables, @filepath for file references, and !command for executing shell commands during task processing.

How does a TDD-driven workflow enforce prerequisites before executing implementation phases?

TDD-driven workflow enforces prerequisites by loading design documents and plan.md first, ensuring tasks progress correctly through phases from initial plan to final verification.

Does the Speckit implementation workflow work without the .opencode/commands directory?

The Speckit implementation workflow checks the primary .opencode/commands/speckit.implement.md path, and falls back to the legacy .opencode/command/speckit.implement.md if the primary file is missing.

Why does my automated build execution stall during task loading phases?

Automated build execution stalls during task loading if prerequisites fail validation, if plan.md is missing, or if OpenCode command files contain syntax errors preventing proper task parsing.

Can I run Speckit implementation tasks end-to-end without manual intervention?

Run Speckit implementation tasks end-to-end without manual intervention by reading tasks.md, executing prerequisites automatically, loading design documents, and progressing through all defined task phases.