Skip to content

Profile workflow maps

See who does what, where work returns for revision, and what each profile produces. Open a map below or download its SVG to share with your team.

Blue marks the input and result. Light blue marks an agent’s work. Green marks project verification. Amber marks a plugin extension. Roles describe responsibilities; they do not imply a separate agent process or parallel execution for every box.

Work to do	Profile
Make a small, bounded change	small_task
Deliver a feature	feature
Add a custom compliance step	complex_feature
Prepare a plan	planning
Investigate before implementation	research
Assess existing changes for delivery	delivery_audit
Review an existing working diff	code_review
Restructure existing code	refactor
Plan and implement a migration	migration

These maps show the built-in single-project recipes. Local configuration can change them. Failed verification and exhausted loops follow the active handoff policy; reaching a box does not mean its checks passed. Commit, publication and deployment are separate from the phase sequence.

Feature

The full development cycle: validate a plan, implement dependent subtasks, review, repair when needed, and assess readiness. Subtasks currently execute sequentially. The built-in default mode is pro.

feature Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Deliver a feature through planning, review and repair.

Small task

One planning pass followed by implementation. This recipe has no code-review loop or final-acceptance phase. Declared project verification still applies.

small_task Default: fast View workflow

Scroll sideways to read the full map on a small screen.

Plan and implement a small, bounded change.

Complex feature

Allows three planning rounds and adds compliance_check before code review. The built-in compliance handler is a no-op stub: a plugin must supply a real audit. Choosing this profile alone does not add security testing.

complex_feature Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Use a longer planning loop and a custom compliance hook.

Planning

Produce and validate a plan, with operator feedback after every verdict where interactive handoffs are supported. Implementation is a separate follow-up.

planning Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Prepare a reviewed plan for an operator decision.

Research

Uses the same planning recipe for investigation, with fast as its default mode. Its output is a reviewed plan, not an implemented change.

research Default: fast View workflow

Scroll sideways to read the full map on a small screen.

Investigate a question and produce a reviewed plan.

Delivery audit

Review current uncommitted changes and assess delivery readiness. This recipe does not implement fixes; the review phase skips when there is no working diff.

delivery_audit Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Assess whether existing changes are ready for delivery.

Code review

Uses the same two-phase recipe as delivery audit, with code review as the work intent. Findings do not start an automatic repair loop in this profile.

code_review Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Review the current working diff without implementing changes.

Refactor

Uses the feature recipe for restructuring: a reviewed plan, sequential dependent subtasks, review and repair, then final acceptance.

refactor Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Restructure code through tracked subtasks and independent review.

Migration

Uses the complex-feature recipe for migrations. Database-specific checks, rollback checks and a real compliance audit must be supplied by the project or a plugin; they are not created by the profile name.

migration Default: pro View workflow

Scroll sideways to read the full map on a small screen.

Plan a migration with a custom compliance hook and review.

Task

Internal workflow. Starts from an existing plan and runs implementation, review and repair, then final acceptance. It is hidden from fresh-run choices.

task Internal workflow View workflow

Scroll sideways to read the full map on a small screen.

Implement an existing plan in a scoped internal workflow.

Correction

Internal workflow. Starts by classifying recorded blockers from a rejected parent run, then implements, reviews and assesses the repair. It requires correction context and is not a fresh-task profile.

correction Internal workflow View workflow

Scroll sideways to read the full map on a small screen.

Address recorded blockers from a rejected parent run.

Beyond these maps

In cross-project runs, feature, complex_feature, refactor and migration also require the runner-owned contract_check and cross_final_acceptance gates after the relevant child work. See Cross-project projection.

The maps are generated from the built-in recipe definitions. Round counts describe the recipe budget; operator-directed retries can extend a run. Project verification determines which checks run and whether failures block.

Next

Profile semantics explains how to choose a workflow.
Profile reference lists configuration and schema fields.
Handoffs and advisors explains what happens when a run needs a decision.
Scheduled verification explains how to declare actual checks.