implement

Execute sequential implementation tasks from order.md and todo.md with quality gates.

5|Updated Mar 22, 2026

Search Tags:#automation #workflow #tdd #specification #implement

Ready to run

npx skills add https://github.com/kzytateishi/spikeee-plugins-marketplace --skill implement-kzytateishi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/kzytateishi/spikeee-plugins-marketplace/tree/main/plugins/dev-workflow/skills/implement
Command: npx skills add https://github.com/kzytateishi/spikeee-plugins-marketplace --skill implement-kzytateishi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates end-to-end implementation by reading specification files (order.md and todo.md) and executing tasks sequentially, enabling a structured, reproducible development workflow.

Core Features & Use Cases

Sequential task execution: processes tasks from the specification in order, updating completion status as tasks are implemented.
Environment detection: auto-detects language, tooling, test/lint/build commands to tailor the workflow.
Quality gates: enforces tests, linting, type checks, and coverage thresholds before completion.
Spec-driven progression: supports TDD or standard workflows to drive feature development from specs.

Quick Start

Provide the specification directory path or feature name and run the implement command to start the end-to-end task implementation.

Frequently Asked Questions about implement

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

FAQPage Schema

How do I automate implementation from a specification document?▼

Automating specification-driven implementation requires reading order.md and todo.md files to execute tasks sequentially. This workflow supports both TDD and standard development approaches, updating completion status as each task is implemented.

Can I enforce quality gates like tests and linting before marking tasks complete?▼

Quality gates enforcing tests, linting, type checks, and coverage thresholds are applied before task completion. The workflow auto-detects your project's language and tooling to run the appropriate test and lint commands as mandatory checks.

What do I need to set up before running spec-driven task execution?▼

Spec-driven task execution requires defined specification files, test and lint configurations, and coding conventions. You need to provide a specification directory path or feature name to start the end-to-end implementation workflow.

Does this workflow support TDD or only standard implementation approaches?▼

Both TDD and standard implementation workflows are supported for driving feature development from specifications. The approach processes tasks sequentially from order.md and todo.md, tailoring the workflow to your chosen development methodology.

How does environment detection work for different programming languages?▼

Environment detection auto-detects the project's language, tooling, and test, lint, and build commands to tailor the workflow. This ensures deterministic task execution by matching quality gates to your specific development stack.