Factory

Start with the Factory guide for workflow setup and configuration.

Read .agent-factory/config.yaml and apply the optional skill_prompts.factory entry as additional project guidance. Configure the current project to turn selected product or maintenance signals into verified, reviewed changes. Factory coordinates the other modules; it does not assume a provider, repository, schedule, or autonomy level.

Set up

Use the Factory configuration reference for field meanings, examples, and host limitations.

1. Read .agent-factory/config.yaml if it exists. Preserve explicit choices.
2. Show the read-capable integrations this host exposes. There is no built-in Factory source catalog. Confirm the source scope; add a custom source only when a connected tool can read it.
3. Set each action policy independently: implement, reply, close, review, approve, publish, merge, deploy, recover, and notify.
4. Add optional per-skill prompts under skill_prompts when you want project-specific rules layered onto a module.
5. Choose schedules, time zone, worktree ownership, runtime, and notifications only where the host supports them.
6. Write the agreed config. Never put credentials or tokens in it.
7. If asked to create automations, create one job per enabled workflow, then read back its saved schedule, target, runtime, and notification settings. Report fields the host could not honor.

A config entry or written prompt does not prove a job exists. Treat unavailable or partial reads as unknown, not empty or successful.

Safe defaults