operant

Activate paid cloud mode by entering your Operant API key

Manually process a call trigger file through the pipeline

Start the operant-pi voice pipeline (webhook server + tunnel + Retell registration)

Show current operant-pi pipeline status

Stop the operant-pi voice pipeline (kill server, tunnel, clean PIDs)

Use this agent when the pipeline enters the audit phase and needs verification of the implementation against the spec. Typical triggers include dev phase completing with no blockers and the pipeline transitioning to audit state, and re-audit after a revision cycle where dev fixed previously failed requirements. See "When to invoke" in the agent body for worked scenarios.

Use this agent when the pipeline enters the dev phase and needs code implementation from an approved implementation spec. Typical triggers include all 4 SDLC artifacts being approved and the pipeline transitioning to dev state, a revision cycle where the auditor found failures and dev needs to fix them, and blocker resolution where the user unblocked an issue and dev resumes. See "When to invoke" in the agent body for worked scenarios.

Use this agent when the pipeline needs the next SDLC artifact produced (intent-and-constraints, high-level-design, adr-lite, or implementation-spec). Typical triggers include pipeline advancing to an sdlc state after requirements are written, a review being approved and the next artifact needed, and manual invocation via /process to kick off spec production. See "When to invoke" in the agent body for worked scenarios.

<!-- #core -->

<!-- #core -->

Knowledge about the operant-pi voice pipeline -- FSM states, transitions, phases, artifact sequence, human gates, and how the autonomous development loop works. Use when Claude needs to understand pipeline behavior, interpret pipeline state, route decisions based on FSM state, or debug pipeline issues.

<!-- #core -->

11 hooks across 9 events