unac-pipeline

Orchestrate the end-to-end unac-agents pipeline from intake to merge-ready delivery.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/uesleinasch/unac-agents --skill unac-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unac-pipeline
Source: https://github.com/uesleinasch/unac-agents/tree/main/skills-claude/unac-pipeline
Command: npx skills add https://github.com/uesleinasch/unac-agents --skill unac-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill acts as the controller for the end-to-end unac-agents pipeline, coordinating from user request intake to final code approval and deployment readiness, ensuring a single, serial flow with explicit gates and handoffs.

Core Features & Use Cases

  • Serial orchestration of all pipeline phases (intake, Jira card, architecture plan, execution, QA, review, and closure).
  • Gate-based human reviews to prevent drift and ensure alignment with the user.
  • Sub-skill dispatch pattern to invoke product-owner, Jira, architect, tech-lead, developer, QA, and reviewer in a controlled sequence.
  • Maintains state artifacts in .unac/{item-id}/ for traceability and re-entry.

Quick Start

Provide the backlog item details and start the pipeline to move it from intake through deployment end-to-end.

Frequently Asked Questions about unac-pipeline

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

FAQPage Schema
How do I orchestrate a full software development pipeline from Jira backlog intake to merge-ready code?

Pipeline orchestration automates the end-to-end flow from user request intake to code merge readiness by coordinating cross-role handoffs between Product Owner, Architect, Developer, QA, and Reviewer through serial dispatch and gated reviews.

What is gated code review orchestration and when do I need it for cross-role coordination?

Gated orchestration enforces strict phase sequences and human review gates between roles like Tech Lead and QA, preventing drift and ensuring alignment when backlog items require coordinated, multi-step delivery.

How do I maintain pipeline state and traceability for backlog items across multiple development phases?

Pipeline state persistence stores traceability artifacts in a dedicated .unac/{item-id}/ directory for each backlog item, enabling re-entry and tracking across intake, architecture, execution, QA, and closure phases.

Can I automate Jira ticket creation and architecture planning as part of a continuous delivery pipeline?

Yes, serial orchestration invokes dedicated subagents for Jira card creation and architecture planning in a controlled sequence, moving items from user request intake directly into execution and deployment readiness.

How do I handle blocked or failed outcomes during automated QA and code review handoffs?

The pipeline implements defined escalation gates for blocked or failed outcomes, pausing the serial dispatch process to prevent drift and ensure issues are resolved before proceeding to the next phase.

Does the unac-pipeline support parallel task execution or is it strictly sequential?

The pipeline enforces a strict phase sequence using serial dispatch, meaning subagents for Developer, QA, and Reviewer execute in a controlled, sequential order rather than running in parallel.