implement

Coordinate software-engineer and tester agents to implement and commit a single ticket.

487|128|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/iusztinpaul/designing-real-world-ai-agents-workshop --skill implement-iusztinpaul
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/iusztinpaul/designing-real-world-ai-agents-workshop/tree/main/implement_yourself/.claude/skills/implement
Command: npx skills add https://github.com/iusztinpaul/designing-real-world-ai-agents-workshop --skill implement-iusztinpaul

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drives a single workshop ticket through the inner SWE↔Tester loop, handling branch creation, agent orchestration, verification, and a single completion commit.

Core Features & Use Cases

  • Orchestrates a complete end-to-end ticket flow for the implement_yourself workspace.
  • Coordinates a software-engineer agent and a tester (logic tickets) to implement, verify, and commit a ticket.
  • Provides a guided, one-ticket-per-invocation cadence with branch management and hand-offs for human review.

Quick Start

Invoke the /implement command to start processing a single ticket from implement_yourself/tasks and follow the prompts to review, run the engineers, verify, and commit.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I orchestrate end-to-end ticket execution for a single pre-groomed task?

End-to-end ticket execution is orchestrated by coordinating software-engineer and tester agents to implement a single ticket, covering branch creation, role-based hand-offs, AC-walk verification, and a final git commit within the implement_yourself workspace.

How does agent orchestration work for software engineering workflows?

Agent orchestration coordinates a software-engineer agent and a tester to implement, verify, and commit logic tickets. It manages role-based hand-offs between agents and provides a guided, one-ticket-per-invocation cadence with clear human review steps.

Can I process multiple tickets in a single workflow automation run?

Workflow automation for ticket execution is limited to one ticket per invocation. The orchestrator drives a single workshop ticket through the inner SWE and Tester loop, ensuring safe, auditable execution before moving the task to done.

What is the best way to automate branch creation and verification for e2e testing?

Automating branch creation and verification requires invoking an orchestrator command to process a ticket, which coordinates the software-engineer and tester agents to implement, verify acceptance criteria, and complete a final git commit.

Do I need pre-groomed tickets to use this e2e-testing workflow?

Pre-groomed tickets are required because the orchestrator executes a single pre-groomed ticket from the implement_yourself workspace, relying on acceptance criteria for AC-walk verification during the agent hand-offs.

When should I not use automated ticket-management orchestration?

Automated ticket-management orchestration should not be used for batch processing multiple issues, as it strictly enforces a one-ticket-per-invocation limit to ensure safe, auditable execution with human hand-off before moving to done.