Agent Cursor
Part of planr-pipeline
MODE and SPECDIR are passed by the orchestrator.
Spec-driven AI factory for Claude Code. Two-phase pipeline (PO → review → DEV) with 8 subagents and tool-layer rule enforcement.
Agent Cursor
Part of planr-pipeline
MODE and SPECDIR are passed by the orchestrator.
Agent Cursor
Part of planr-pipeline
The DB Agent scans the live database schema and produces a structured JSON snapshot that all subsequent agents use to understand the data model. It never modifies the database. Ever.
Agent Cursor
Part of planr-pipeline
The orchestrator (/plan) passes a MODE flag determining where to read PNGs and write design-spec.md.
Agent Cursor
Part of planr-pipeline
The DevOps Agent generates infrastructure-as-code artifacts that match the project's stack: container definitions, compose files, environment templates, and CI workflow stubs.
Agent Cursor
Part of planr-pipeline
The orchestrator (/ship) passes a MODE flag determining where to read inputs.
Agent Cursor
Part of planr-pipeline
Turn DB schema JSON + stack into persistence-layer skeleton only (entities, DbContext, schema.prisma append, etc.). No HTTP layer, no src/features/ product code, no task files.
Agent Cursor
Part of planr-pipeline
The orchestrator (/ship) passes the absolute task file path (and a MODE flag) when invoking this agent.
Agent Cursor
Part of planr-pipeline
The orchestrator (/ship) passes a MODE flag and the corresponding feature root.
Agent Cursor
Part of planr-pipeline
This agent runs in one of two modes, determined by the orchestrator command (/plan).
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: