implement

Orchestrate a single workshop ticket from grooming to commit.

13.4k|1.7k|Updated Feb 16, 2025

Search Tags:#workflow #workshop #orchestrate #ticket-management #tester #swe

Ready to run

npx skills add https://github.com/Arindam200/awesome-ai-apps --skill implement-arindam200

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/Arindam200/awesome-ai-apps/tree/main/advance_ai_agents/deep_research_writing_agents_nebius_okahu/implement_yourself/.claude/skills/implement
Command: npx skills add https://github.com/Arindam200/awesome-ai-apps --skill implement-arindam200

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides an automated orchestration workflow to run a single workshop ticket from grooming through commit, coordinating the SWE and Tester roles and branch/commit lifecycle.

Core Features & Use Cases

Guides a single-ticket implementation loop: from grooming to task completion and commit, with optional automatic routing by archetype.
Manages a fixed default branch implementing/from-scratch and reuses it for subsequent tickets, stacking commits.
Provides end-to-end workflow steps: launching the SWE agent, orchestrator checks, and automated ticket transitions to tasks/done/, with standardized commit messages.

Quick Start

Type /implement to begin a one-ticket workshop and follow the prompts to groom, implement, 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 a single workshop ticket from grooming to commit?▼

Orchestrate a single workshop ticket by launching the workflow to guide SWE and Tester roles through grooming, acceptance criteria walks, branching, and the final commit lifecycle end-to-end. Type /implement to begin and follow the prompts to groom, implement, verify, and commit.

Can I batch multiple tickets together in a workshop orchestration workflow?▼

No, this orchestration workflow prevents multi-ticket batching and strictly processes a single ticket at a time. It enforces this constraint to ensure focused coordination between SWE, Tester, and orchestrator roles from grooming through to the final commit.

What is the default branch name for workshop ticket implementation?▼

The default branch name for workshop ticket implementation is implementing/from-scratch. This fixed fallback branch is reused for subsequent tickets, stacking commits on top of each other to maintain a consistent implementation history.

How do verification and automated ticket transitions work in workshop orchestration?▼

Verification in workshop orchestration relies on Makefile targets and standardized git commit messaging to validate task completion. Once verified, the workflow automates ticket transitions to the tasks/done/ directory, closing the implementation loop for that specific ticket.

Do I need a Makefile to run the single-ticket workshop workflow?▼

Yes, a Makefile is required as the workflow relies on Makefile targets for verification alongside git commit messaging. These targets are integral to orchestrating the SWE agent, orchestrator checks, and automated transitions to tasks/done/.