docs: add Factory SDLC automation recipe

[warp-agent-staging]

What this feature does

An SDLC factory coordinates intake, triage, planning, implementation, review, and UI verification for one product while people approve material specifications and merges. Shipped in v0.2026.10.07.08.29.stable_00 (2026-10-07).

Summary

Replaces the SDLC scaffold with a supported one-factory recipe that uses the default role agents and explains the boundary for multi-factory coordination.

Changes

src/content/docs/factories/use-cases/end-to-end-sdlc-automation.mdx

• Defines stage outputs, access boundaries, and human gates.
• Adds a foreman intake automation and seven-step setup procedure.
• Documents revision and verification flow plus the lack of a native cross-factory dependency graph or automatic merge stage.

Content design plan

Audience and JTBD: An engineering leader whose individual Factory stages are reliable and who wants to connect them into a controlled product-development workflow.

Problem: Primitive and role docs do not explain the supported default for connecting stages or where cross-factory coordination stops.

Goals:

• The reader can configure one factory with role-specific agents and one intake signal.
• The reader can keep specification approval and merge as human gates.
• The reader can identify when external coordination is required.

Purpose and value: The guide gives teams a supported composition model without implying a dependency graph or automatic merge capability that does not exist.

Content type: Feature documentation (combined) — the reader needs an orchestration model and setup procedure.

Skill and template: draft_feature_doc / .agents/templates/feature-doc.md.

High-impact scenarios:

• Covers: one product, repositories that ship together, default role agents, review revision, and conditional UI verification.
• Excludes: atomic cross-factory workflows and automatic merging; external events, webhooks, or Factory MCP can coordinate non-atomic handoffs.

Unverified claims

• The cross-factory dependency and automatic-merge limitations were checked against current definitions and schemas, but require Factory product-owner confirmation before merge.

Documentation risk

Risk: engineering-review-required
Rationale: Adds new public Factory orchestration guidance and product-boundary claims that require product review.
Docs override: none

PR stack

• #895 — Navigation and structure
• #896 — Issue triage
• #897 — Code review
• #898 — Issue implementation
• #899 — Production incident resolution
• #900 — Computer Use verification
• #901 — End-to-end SDLC automation

Dependency: #895 is the shared base and targets main. PRs #896–#901 each independently target factory/factory-use-cases-structure; no guide PR depends on another guide PR.

Human review focus

• Confirm the one-factory recommendation and default role sequence.
• Confirm the cross-factory and automatic-merge boundary wording.

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 10, 2026 12:44am UTC

[warp-agent-staging]

This PR was generated with Warp.

Comment @warp-staging-factory on this PR to send it follow-up work.