controller

Coordinate phase-gated operator feature development across init, API types, controller implementation, and E2E testing.

Updated May 5, 2026

Search Tags:#workflow orchestration #e2e testing #operator development #phase gating #code generation pipeline #pull request planning #reconciliation logic

Ready to run

npx skills add https://github.com/swghosh/ambient-workflows --skill controller-swghosh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: controller
Source: https://github.com/swghosh/ambient-workflows/tree/main/workflows/operator-feature-dev/.claude/skills/controller
Command: npx skills add https://github.com/swghosh/ambient-workflows --skill controller-swghosh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents stalled or out-of-order operator feature development by coordinating a multi-PR, multi-phase workflow with explicit user gates at every transition.

Core Features & Use Cases

Phase-gated orchestration: Executes the correct command for the current phase (init, API typing, controller implementation, E2E generation) and then pauses for user confirmation before moving on.
Multi-PR deliverable management: Guides production of three pull requests (API types, controller/reconciler implementation, and E2E tests) plus a final summary synthesis.
Deterministic navigation and recommendations: Uses the workflow controller rules to recommend next steps based on actual phase outcomes, including options to advance, go back, skip review/pr steps appropriately, or speedrun remaining phases.

Quick Start

Provide the Enhancement Proposal URL and operator repository URL, then run the init phase with /oape.init <repo-url> <base-branch> and follow the controller’s prompted next-step options.

Frequently Asked Questions about controller

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

FAQPage Schema

How do I coordinate multi-phase operator feature development across API types, controllers, and E2E tests?▼

Operator feature development is coordinated using a phase-gated workflow that executes init, API type generation, controller implementation, and E2E testing sequentially, pausing for explicit user confirmation at every transition to prevent out-of-order execution.

What is the best way to manage multiple stacked pull requests for a Kubernetes operator enhancement proposal?▼

Managing multiple stacked pull requests for an operator enhancement is handled by producing three distinct PRs for API types, reconciler implementation, and E2E tests, followed by a final synthesized summary that aggregates the deliverables.

Can I skip phases or speedrun remaining steps when generating an operator code pipeline?▼

Yes, the workflow controller evaluates actual phase outcomes to recommend next steps, including options to advance, go back, skip review and pull request steps, or speedrun remaining phases of the operator code generation pipeline.

Do I need an enhancement proposal URL to start controller reconciliation logic implementation?▼

Yes, an enhancement proposal URL and operator repository URL are required inputs to initialize the phase-gated workflow and begin generating reconciliation logic during the init phase.

Why does my operator feature workflow stall during API type generation and controller implementation?▼

Workflows stall without phase-gated orchestration to enforce strict execution order, but applying deterministic navigation rules and explicit user confirmation gates prevents stalled or out-of-order operator feature development across phases.

Does phase gating work for enhancement proposal driven engineering workflows requiring E2E testing?▼

Yes, phase gating is designed specifically for enhancement proposal driven engineering workflows, applying strict phase execution order and workspace navigation rules to produce E2E tests and controller implementations safely.