bug-fix

Coordinate an end-to-end bug-fix pipeline from discovery through QA validation.

19|3|Updated Jul 19, 2024

Search Tags:#automation #qa #pipeline #triage #foundation #bug #orchestrate

Ready to run

npx skills add https://github.com/danielterra/FOUNDATION --skill bug-fix-danielterra

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bug-fix
Source: https://github.com/danielterra/FOUNDATION/tree/main/.claude/skills/bug-fix
Command: npx skills add https://github.com/danielterra/FOUNDATION --skill bug-fix-danielterra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a fully-managed orchestration of the Foundation bug-fix lifecycle, guiding the flow from initial support investigation to QA validation, ensuring no step is skipped and no devs are contacted directly by the PO.

Core Features & Use Cases

End-to-end bug pipeline orchestration across support, architect triage, developer back-end/frontend, and QA.
Enforces workflow rules and guardrails, including status transitions and data persistence, while keeping the PO out of direct dev work.
Use Case: When a bug IRI is reported, the skill triggers the full process, moves the bug through stages, and consolidates test instructions for QA.

Quick Start

Provide the bug IRI to initiate the full bug-fix pipeline from support to QA.

Frequently Asked Questions about bug-fix

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

FAQPage Schema

How do I orchestrate an end-to-end bug-fix pipeline from discovery to QA validation?▼

To orchestrate an end-to-end bug-fix pipeline, provide the bug IRI to initiate the process. The skill coordinates sub-agents through support investigation, architect triage, developer delivery, and final QA validation, enforcing workflow guardrails and persisting status updates at each stage.

What is the best way to automate bug triage and prevent product owners from contacting developers directly?▼

Automating bug triage requires a centralized orchestration skill that enforces workflow guardrails, keeping the PO out of direct developer work. The skill manages all PO communication and coordinates the flow from support investigation through architect triage to development delivery.

Can I use this orchestration skill for both backend and frontend bug workstreams?▼

Yes, the orchestration skill applies to bug-IRIs across both backend and frontend workstreams. It guides sub-agents through the respective development delivery stages while enforcing order and guardrails throughout the entire bug-fix lifecycle.

How do I start the bug-fix lifecycle when a bug IRI is reported?▼

When a bug IRI is reported, you start the bug-fix lifecycle by passing the exact bug IRI to the skill. This triggers the full process from support to QA, moving the bug through stages and consolidating test instructions for QA validation.

Does this bug pipeline orchestration skill require any external dependencies or components?▼

No, the bug pipeline orchestration skill operates with zero external dependencies or components. It functions independently to coordinate the end-to-end lifecycle, persisting the dossier and status updates at each stage without requiring additional modules.

Why does the product owner need to communicate only through the orchestration skill during bug resolution?▼

The product owner must communicate only through the orchestration skill to enforce workflow guardrails and ensure no steps are skipped. This prevents direct developer contact, maintaining an organized flow from support investigation to QA validation.