controller

Coordinate phase transitions and guardrails for end-to-end bugfix workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/stackrox/ambient-workflows --skill controller-stackrox
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: controller
Source: https://github.com/stackrox/ambient-workflows/tree/main/workflows/bugfix/.claude/skills/controller
Command: npx skills add https://github.com/stackrox/ambient-workflows --skill controller-stackrox

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides centralized control over multi-phase bugfix workflows, ensuring phase gates and user prompts govern progression.

Core Features & Use Cases

  • Phase-gated orchestration of bugfix tasks (assess, reproduce, diagnose, fix, test, review, document, pr, summary).
  • Enforces user decision points via AskUserQuestion to prevent auto-advancement.
  • Provides structured recommendations and next-step options to guide agents and humans.

Quick Start

Announce a phase, run the corresponding phase skill, then await user input before advancing.

Frequently Asked Questions about controller

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

FAQPage Schema
How do I orchestrate multi-phase bugfix workflows with phase gating?

You orchestrate multi-phase bugfix workflows by coordinating phase transitions across assess, reproduce, diagnose, fix, test, review, document, pr, and summary stages. The controller enforces gating logic and explicit user prompts to prevent auto-advancement, ensuring safe, orderly progression and auditable decisions.

What is phase-gated orchestration for AI agent bugfix tasks?

Phase-gated orchestration is a control mechanism for AI agent bugfix tasks that enforces user decision points between workflow phases. It applies sequencing rules and structured recommendations to prevent auto-advancement, ensuring every phase transition requires explicit human approval before proceeding.

How do I stop automated agents from skipping bugfix workflow phases?

To stop automated agents from skipping bugfix workflow phases, the controller implements gating logic via explicit user prompts to proceed. This prevents auto-advancement by requiring human confirmation at each phase gate, ensuring all decisions are auditable and progression is orderly.

Can I customize the phase sequence for my bugfix workflow?

The bugfix workflow phase sequence covers assess, reproduce, diagnose, fix, test, review, document, pr, and summary. The controller applies phase sequencing rules to coordinate transitions, providing structured recommendations and next-step options to guide agents and humans through the end-to-end process.

What's the best way to structure an end-to-end bugfix workflow with guardrails?

The best way to structure an end-to-end bugfix workflow with guardrails is using centralized control over multi-phase tasks. This approach enforces phase gates and user prompts to govern progression, applying across all phases with structured recommendations to ensure safe and auditable decisions.

Why do I need user prompts at every bugfix workflow phase transition?

User prompts at every bugfix workflow phase transition are needed to enforce user decision points and prevent auto-advancement. This gating logic ensures safe, orderly progression and creates auditable decisions, keeping human oversight central to the AI agent orchestration process.