Use cases
Ship a small change with focused checks
Use the quick paths for a clear, bounded change, with enough verification and independent review for the risk involved.
Match the workflow to the change
Small, low-risk changes can run inline with the Main agent in Build. When a bounded change needs independent implementation, review, and verification, start the specialist Quick workflow with /mini-spec-lane.
| Need | Path |
|---|---|
| A clear low-risk change with focused checks | Inline work with Main in Build. |
| A bounded change needing independent review | Quick lane: Implement → Code Review → Verify. |
| Requirements, architecture, or rollout decisions | Full Lane. |
State observable behavior and boundaries
Connect GitHub or Bitbucket and an agent provider in Integrations. Select the repositories for your product and let Factory setup prepare them automatically. Review and merge any required setup PRs in their respective repositories. Configure models in Agents and compute in Settings.
Open a session, select Build, and provide the relevant repositories and expected outcome. Use the command below when you want the specialist Quick workflow.
/mini-spec-lane Improve the empty state in the team member list.
Expected: show an invitation action when an owner has no members.
Members without invitation permission should see a read-only message.
Keep loading and error states distinct and preserve existing API behavior.
Done: reviewable PR with relevant UI and permission checks.The agent should clarify ambiguity before broadening scope. If the request reveals a larger contract or product decision, resolve that decision through the appropriate workflow.
Check the result before shipping
Inspect the diff and the verification output against the agreed scope. In the specialist Quick workflow, confirm review findings are resolved and Verify has completed the required checks. Check any limitations and apply the repository’s usual merge approval process.
Quick lane guide · Compare execution paths · Recover a failed step