agentic-cockpit

Standardize change practices across the Agentic Cockpit monorepo.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edupazogle/agentic_cockpit --skill agentic-cockpit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentic-cockpit
Source: https://github.com/edupazogle/agentic_cockpit/tree/main/.agents/skills/agentic-cockpit
Command: npx skills add https://github.com/edupazogle/agentic_cockpit --skill agentic-cockpit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken integrations and accidental architecture violations by standardizing how changes should be made across the Agentic Cockpit monorepo.

Core Features & Use Cases

  • Repo organization & boundaries: Clarifies where functionality lives (Next.js cockpit, Python FastAPI gateway, run-store, and state machine) and what imports and writes are forbidden to keep the system coherent.
  • Wire format & workflow rules: Documents the gateway↔cockpit API routes, event streaming expectations, run status/state transitions, and HITL decision handover flow so engineers implement compatible behavior.
  • Operational and testing conventions: Establishes toolchain requirements (pnpm, uv, mypy/ruff) and testing/CI expectations to reduce regressions and integration drift.

Quick Start

Use the agentic-cockpit Skill when you are modifying /app, /lib/server, /gateway, or wiring scenario flows in the Agentic Cockpit monorepo.

Frequently Asked Questions about agentic-cockpit

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

FAQPage Schema
How do I prevent incompatible behavior between a Next.js cockpit and FastAPI gateway?

To prevent incompatible behavior, you must standardize change practices across the monorepo by enforcing exact API route contracts, strict file-boundary rules, and run-store as the single source of truth.

What is the correct way to handle run status transitions in a FastAPI gateway?

Run status transitions must follow scenario state machine rules and append-only event semantics, ensuring queued-to-running progress and HITL decision handover flows are properly wired to the run-store.

How do I safely update server-side run-store logic in an agentic monorepo?

Safely updating run-store logic requires adhering to documented toolchain versions like pnpm and uv, maintaining strict import boundaries, and preserving run-store as the single source of truth to avoid unsafe state mutations.

Do I need specific toolchain versions for Next.js and FastAPI monorepo development?

Yes, you need specific toolchain versions. The monorepo requires pnpm and uv for package management, alongside mypy and ruff for Python linting and type checking to reduce regressions and integration drift.

Why does my human-in-the-loop workflow break when updating cockpit app routes?

HITL workflows break when file-boundary rules are violated or event streaming expectations are ignored, requiring strict adherence to documented gateway-cockpit API routes and audit logging conventions.

What are the limitations when modifying scenario state machine transitions?

Modifying scenario state machine transitions is constrained by append-only event semantics and exact API route contracts, meaning you cannot perform unsafe data mutations or bypass the run-store source of truth.