implement

Accepts text, voice, or visual input; responds with text or synthesized speech depending on availability and preference of user.

1|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/RomainDECOSTER/ironforge --skill implement-romaindecoster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/RomainDECOSTER/ironforge/tree/main/copilot/skills/implement
Command: npx skills add https://github.com/RomainDECOSTER/ironforge --skill implement-romaindecoster

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implementing Sudocode issues in dependency order requires strict discipline and traceable commits. This skill automates the end-to-end workflow, enforcing a RED-GREEN-REFACTOR-COMMIT cycle and updating Sudocode after each commit.

Core Features & Use Cases

  • Strict TDD workflow: Enforces a RED-GREEN-REFACTOR-COMMIT cycle for each issue.
  • Context7 integration: Leverages library documentation to inform implementation and reduce guesswork.
  • LSP diagnostics: Uses language-server data when available to improve correctness.
  • Sudocode synchronization: Updates issue status after each commit to keep tracking accurate.
  • Flexible starting point: Accepts an optional issue ID or automatically moves to the next pending issue.

Quick Start

Invoke the implement skill with an optional issue ID to start from, or omit the argument to pick the next pending Sudocode issue.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate Sudocode issue implementation with strict TDD?

You can automate Sudocode issue implementation by invoking the implement skill, which enforces a strict RED-GREEN-REFACTOR-COMMIT cycle for dependency-ordered issues and updates Sudocode after each commit.

What is the RED-GREEN-REFACTOR-COMMIT cycle for test-driven development?

The RED-GREEN-REFACTOR-COMMIT cycle is a strict test-driven development workflow that moves work from failing tests to passing tests, refactors the code, and creates a traceable commit for each dependency-ordered issue.

How do I start implementing a specific Sudocode issue by ID?

To start implementing a specific issue, invoke the implement skill with an optional issue ID argument. If omitted, it automatically selects and processes the next pending Sudocode issue.

Does this TDD automation work with Context7 and LSP diagnostics?

Yes, the implementation workflow integrates with Context7 to leverage library documentation and uses LSP diagnostics when available to improve code correctness during the test-driven development cycle.

Can I use this for dependency-ordered issue processing in BMAD workflows?

Yes, this skill applies to dependency-ordered issues and ensures a BMAD-driven RED-GREEN-REFACTOR-COMMIT cycle, including pre-implementation checks and graph-context augmentation if available.

What are the limitations of automating TDD cycles for issue tracking?

This automation requires available LSP diagnostics and Context7 integration for maximum correctness, and it is specifically designed for Sudocode issues, limiting its use with other issue tracking platforms.