implement-universal

Orchestrate ticket-driven SWE and Tester phases with hand-off evidence.

13.4k|1.7k|Updated Feb 16, 2025
One-click install
npx skills add https://github.com/Arindam200/awesome-ai-apps --skill implement-universal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-universal
Source: https://github.com/Arindam200/awesome-ai-apps/tree/main/advance_ai_agents/deep_research_writing_agents_nebius_okahu/implement_yourself/.agents/skills/implement-universal
Command: npx skills add https://github.com/Arindam200/awesome-ai-apps --skill implement-universal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harness-agnostic version of the /implement-universal workflow provides a single-context, end-to-end ticket workshop where SWE and Tester roles operate in sequence without subagent isolation.

Core Features & Use Cases

  • Single-context workshop: runs the SWE phase and the Tester phase in one conversation, with bundled prompts and no subagent dispatch.
  • Archetype-aware routing: supports docs, glue/bootstrap, and logic tickets with tailored verification flows.
  • Evidence-rich hand-offs: outputs hand-off messages, e2e excerpts, and acceptance-criteria traces for audit and QA.

Quick Start

Invoke /implement-universal on a single ticket to execute the SWE phase, switch to the Tester phase, and report results.

Frequently Asked Questions about implement-universal

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

FAQPage Schema
How do I orchestrate a SWE and Tester workflow in a single conversation context?

Single-context workshop orchestration runs SWE and Tester phases sequentially within one conversation, routing logic, glue/bootstrap, and docs tickets with explicit hand-offs and evidence without requiring subagent isolation.

What is ticket-driven software engineering workshop orchestration?

Ticket-driven workshop orchestration processes software engineering tickets through tailored SWE and Tester phases, generating concrete artifacts like hand-off messages, e2e excerpts, and acceptance criteria traces for verification.

Can I run software engineering and testing phases without subagent isolation?

Yes, you can run SWE and Tester phases without subagent isolation by using a single-context environment that applies bundled prompts to execute sequential role hand-offs directly in the same conversation.

How do I map acceptance criteria traces for software engineering tickets?

Acceptance criteria mapping is generated automatically during the Tester phase, producing evidence-rich traces that verify ticket requirements alongside hand-off messages and e2e excerpts for audit and QA.

Does single-context workshop orchestration support documentation and bootstrap tickets?

Yes, archetype-aware routing supports docs, glue/bootstrap, and logic tickets, applying tailored verification flows to each ticket type within the single-context software engineering workshop.

What is the best way to verify software engineering hand-offs without dispatching subagents?

Generating concrete artifacts like hand-off messages and e2e excerpts within a single-context workshop provides verification without subagent dispatch, ensuring coordinated sequential role transitions and evidence collection.