# Agents

This project uses an automated agentic development system configured in `.cursor/`.

## Quick Start

Type `/autopilot` to start or continue the full workflow. The orchestrator detects project state and picks up from there.

## System Overview

See [.cursor/README.md](.cursor/README.md) for the full documentation, including:
- Available skills and their trigger commands
- Workflow stages (BUILD → SHIP → EVOLVE)
- `_docs/` folder structure
- Subagent architecture

## Codex Bootstrap

For new Codex chats in this repository, use this startup order:

1. Read [`.cursor/CODEX_CONTEXT.md`](.cursor/CODEX_CONTEXT.md)
2. Read [`_docs/_autopilot_state.md`](_docs/_autopilot_state.md)
3. Read only the relevant skill file under `.cursor/skills/` for the user's request
4. Read only the relevant `.cursor/rules/*.mdc` files and `_docs/` artifacts for that request

Treat:

- `.cursor/` as the workflow, policy, skills, and agent definition layer
- `_docs/` as the project's persisted memory and execution state

Current known workflow status for this repo:

- Flow: `existing-code`
- Step: `2` (`Test Spec`)
- Status: `in_progress`
- Main blocker: expected-results artifacts are incomplete, so black-box verification cannot be finalized yet

The compact Codex-oriented map of skills, agents, rules, and current state lives in [`.cursor/CODEX_CONTEXT.md`](.cursor/CODEX_CONTEXT.md). Use it as the default bridge instead of re-reading the entire `.cursor/` tree every time.

## Key Commands

| Command | What it does |
|---------|-------------|
| `/autopilot`, `/auto` | Full guided workflow (problem → deploy) |
| `/problem` | Interactive problem gathering |
| `/research` | Deep research methodology |
| `/plan` | Architecture and component planning |
| `/decompose` | Atomic task decomposition |
| `/implement` | Batched parallel implementation |
| `/deploy` | Containerization, CI/CD, observability |

## Rules

Coding conventions, git workflow, quality gates, and technology preferences are defined in `.cursor/rules/`. These are automatically applied based on file type or context.

For Codex specifically:

- if the user asks to continue the Cursor workflow, follow `.cursor/skills/autopilot/*` and the current `_docs/_autopilot_state.md`
- if the user asks for direct implementation or debugging, work directly in code while still honoring the relevant `.cursor/rules/*.mdc` files and existing `_docs/` decisions

## MCP Servers

This project integrates with Jira or Azure DevOps for work item tracking. Copy `.cursor/mcp.json.example` to `.cursor/mcp.json` and fill in your credentials.
