implement

Implement backlog tasks into production code and tests with commit messages.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill implement-gudzenkov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/gudzenkov/SuperClaudeZero/tree/main/.claude/skills/implement
Command: npx skills add https://github.com/gudzenkov/SuperClaudeZero --skill implement-gudzenkov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces manual effort by turning backlog tasks into production-ready code and tests, ensuring traceable delivery and consistency with project standards.

Core Features & Use Cases

  • Reads backlog details from BACKLOG.md and applies architecture guidance to implement tasks
  • Generates production code and accompanying tests that follow existing patterns
  • Produces a clear, ready-to-commit patch with a suggested commit message

Quick Start

Provide a backlog task ID or description and this skill will generate production code, tests, and a ready-to-commit patch.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I turn backlog tasks into production code automatically?

To turn backlog tasks into production code, provide a task ID or description from BACKLOG.md. The skill reads the task details, aligns with existing architecture patterns, and generates production-ready code along with accompanying tests.

Can I generate tests and a commit message from a BACKLOG.md task?

Yes, you can generate tests and a commit message from a BACKLOG.md task. The skill analyzes the task details and project conventions to produce both the accompanying tests and a suggested commit message for a ready-to-commit patch.

What is the best way to implement code that follows existing architecture patterns?

The best way to implement code that follows existing architecture patterns is to use a task-driven approach. By reading backlog details and applying architecture guidance, the generated code maintains consistency with your established project standards and conventions.

Does this approach work for software development workflows without predefined architecture guidance?

This approach is designed for software development workflows where tasks are defined in BACKLOG.md and guided by architecture patterns. Without predefined architecture guidance or backlog details, the skill cannot align the generated production code with project conventions.

How do I ensure traceable delivery when implementing backlog items?

To ensure traceable delivery when implementing backlog items, the skill reduces manual effort by producing a clear, ready-to-commit patch. This patch includes production code, tests, and a suggested commit message directly tied to the original task.

Why does code generation need project conventions to produce a ready-to-commit patch?

Code generation needs project conventions to produce a ready-to-commit patch because it must analyze existing architecture patterns. This ensures the generated production code and tests follow established standards, maintaining consistency and traceability across the codebase.