[warp-agent-staging]

What this feature does

Your existing factory can coordinate intake, triage, planning, implementation, review, and UI verification while people approve specifications and decide whether to merge. Shipped in v0.2026.10.07.08.29.stable_00 (2026-10-07).

Summary

Replaces the SDLC scaffold with a recipe for connecting stages in an existing factory, preserving issue and PR context through human handoff.

Changes

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

• Defines stage outputs, foreman-mediated approval, and implementation on the specification's existing branch and PR.
• Adds a foreman intake automation, six setup steps, and separate tests for intake, approval, revision, exclusions, and failures.
• Reuses existing automations, links custom verifier setup, and scopes the recipe to one factory with human-controlled merging.

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: Individual role and stage docs do not show how to connect intake, approval, implementation, review, and verification while keeping the same issue and PR.

Goals:

• The reader can connect existing factory agents through a selected intake signal without overlapping automations.
• The reader can keep specification approval and merge as human gates.
• The reader can test stage handoffs, revision, and failure reporting before widening intake.

Purpose and value: The recipe connects existing stages with durable issue and PR context, explicit human gates, and observable test outcomes.

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: cross-factory orchestration and automated merging. Separate-factory handoffs are planning considerations, not a capability guarantee.

Unverified claims

• The former product-wide claims about absent cross-factory dependencies and automatic merging were removed, not confirmed. The page now describes this recipe's scope without asserting those capabilities are unavailable.
• No live end-to-end factory or Computer Use workflow was exercised.

Documentation risk

Risk: engineering-review-required
Rationale: Adds public factory workflow guidance, automation configuration, verification handoffs, and human approval policies that require engineering 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

• Review the connected workflow, especially specification approval, same-PR implementation, revision, and verifier evidence handoff.
• Confirm the setup and test instructions fit an existing factory's automations and repository policies.

Validation

• Review fixes are pushed in 8e946dd33ca2484b8376dd373f9387e61f2d3440.
• Typecheck, build, and generated-output regression checks passed during implementation. The automation example passed state-independent parser validation; that does not prove live integration or runtime behavior.
• Rechecked all 26 internal links, compression, and whitespace. No actionable style findings; the glossary warning for the verified Automations label remains.
• Supporting source and production configuration were checked at warp-server 27c9fb8049c27037c15833ab711f7b7a131bf6ac. Checked-in configuration is not deployment or end-to-end evidence.

View conversation

Co-Authored-By: Warp agent@warp.dev

[vercel]

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

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 28, 2026 3:11am UTC

[warp-agent-staging]

This PR was generated with Warp.

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

  

[rachaelrenk]

Review summary

The recipe connects SDLC stages, but its existing-factory setup, automation reuse, activation/testing, verifier configuration, and spec-to-PR handoff need correction; product-boundary claims remain unconfirmed. Found: 1 critical, 5 important, 1 suggestion, 0 nits. Request changes.

Editorial verdict

Keep this page's task: connecting existing stages into a controlled SDLC workflow. Keep the stage outputs and a concrete end-to-end example, while linking stage setup to the narrower recipes, default behavior to the lifecycle page, and measurement details to their reference pages. Move failure handling into actionable tests and remove the repeated best-practices checklist. Narrow or confirm the product-wide limitation claims rather than treating schema absence as proof.

Validation

• Reviewed head 7616c82ba6a7b7b52c89c4091445f83f4118c37e against its stack parent; no documentation edits or parent-sync merge.
• Typecheck: 0 errors and 0 warnings; heading-variable tests: 5 passed; build passed.
• Generated heading/TOC and homepage JSON-LD checks passed; 11 internal links passed.
• Focused style lint, compression contract, and structural PR contract passed; risk classification is appropriate.
• Checked defaults, GitHub automation seeding, and relevant production configuration at warp-server 27c9fb8049c27037c15833ab711f7b7a131bf6ac. Checked-in configuration is not end-to-end or deployment evidence.
• No live factory or Computer Use workflow was exercised. Product-wide limitations remain unconfirmed.

Verdict

Request changes. Submitted as a non-blocking comment review.