docs: add Factory issue implementation recipe

[warp-agent-staging]

What this feature does

An implementation factory turns approved GitHub, Linear, or Jira issues into tested draft pull requests while keeping specification and merge decisions with people. Shipped in v0.2026.10.07.08.29.stable_00 (2026-10-07).

Summary

Replaces the issue-implementation scaffold with a ready-work recipe that routes issues through the foreman, optional specification, implementation, validation, and independent review.

Changes

src/content/docs/factories/use-cases/issue-implementation.mdx

• Adds source-specific ready-work triggers and filters.
• Adds a foreman automation example and a six-step configuration procedure.
• Documents test, visual-proof, review, permission, and human-merge expectations.

Content design plan

Audience and JTBD: A team with an approved backlog that wants agents to implement bounded work and hand back reviewable pull requests.

Problem: Existing integration and agent pages do not show how to turn a tracker readiness signal into a validated code change without bypassing product or merge gates.

Goals:

• The reader can choose a reliable ready-work signal.
• The reader can route implementation through the shortest safe factory path.
• The reader can preserve acceptance criteria and human merge control.

Purpose and value: The guide connects tracker intake to the default factory roles and gives teams a constrained first implementation workflow.

Content type: Feature documentation (combined) — the reader needs workflow guidance and provider-specific setup.

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

High-impact scenarios:

• Covers: approved issues from GitHub, Linear, and Jira that produce draft pull requests.
• Excludes: implementing every new issue, unresolved product decisions, and agent-controlled merging.

Unverified claims

• Linear Issue state changed and Jira Agent session created labels were verified in current configuration sources, but not exercised in live provider UIs.

Documentation risk

Risk: engineering-review-required
Rationale: Adds new public Factory workflow guidance and configuration examples 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 provider-specific ready-work trigger recommendations.
• Confirm when the default foreman should skip or require triage and specification.

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.