An experimental workflow for delivering software changes through configured checks, pull requests, review updates, and merge verification. It follows project permissions and release conditions, and reports missing evidence or checks before treating delivery as complete.
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
Review the instructions the agent will receive before you install.
Start with the Factory guide for workflow setup and configuration.
Read .agent-factory/config.yaml, the optional
skill_prompts.factory-ship entry, and the repository's instructions before
publishing. See the Factory configuration reference. The prompt adds project guidance; editing code does not by itself authorize a PR update, approval, merge, or deployment.
Hold the work when ownership, authorization, a required check, or live host state is missing or unclear. State the exact next step; do not turn an inconclusive result into success.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Guide public skill additions and updates through file placement, catalog documentation, installation discovery, integration settings, and validation. Distinguish ordinary skills from instruction-based, app-backed, and generated skills so each receives the appropriate checks.
Monitor another AI agent’s work and independently investigate the same task. Compare the original request with actual changes and test evidence, report gaps and concrete follow-up steps, and make limited fixes when authorized.
Open Agent-Native apps beside the conversation through Dispatch MCP, a connection for app tools. Create or edit content using the current screen and selection, then read saved results back to confirm the changes.
Organize large coding tasks with Claude Fable directing lower-cost subagents. Delegate bounded research, edits, and tests, then have Fable verify evidence, resolve conflicting findings, integrate changes, and review the final result.
Organize work so an expensive AI model handles planning, judgment, and final review while cheaper helper agents perform bounded research, coding, and testing. Define ownership and verification requirements, then inspect the evidence and integrate their results centrally.
Configure a software delivery workflow that turns selected feedback and maintenance signals into verified, reviewed changes. Define information sources, schedules, working directories, and separate permissions for actions such as implementation, merging, deployment, and notifications.