Product document generation is initiated from the initiative page. Slack quality updates deep-link to that page and cannot bypass operational blockers.
Profiled initiative intake can collect work type, expected size, and optional initial context. Legacy title-only creation remains compatible and hydrates conservative defaults.
Delivery Plan generation has a web action and compatible Slack command, with the web UI treated as canonical for action eligibility and blockers. It creates inrelay draft tasks first; Linear issue creation happens only through explicit Send to Linear.
The visible workflow is Shape Brief, PRD Review, Technical Discovery & Refinement, Delivery Plan, and Handoff Pack. Internal initiative states remain more granular for compatibility and audit history.
Initiative operation feedback is a progress layer inside the visible stages. It covers queued, running, retrying, waiting-external, partial, failed, stale, nested, batch, and synchronous long-running work without changing workflow gates.
Lightweight briefs are limited to strict low-risk bug or patch initiatives sized xs or s; missing context, hard blockers, multi-repo scope, stale evidence, or high-risk categories use the normal PRD flow.
Repo-first Technical Discovery and cited code-inferred answer proposals apply to all repo-context initiatives when enabled. Auto-confirm and auto-apply remain low-risk-only, evidence-gated behaviors.
Delivery Plan target-context carry-forward and repeated Handoff Pack repo/docs question suppression use material signatures. Hard access, stale-index, missing-repo, and implementation-surface blockers remain visible and actionable.
Automated Handoff Pack readiness can run repo/docs refinement, low-risk non-hard repo/docs auto-carry-forward, Blueprint PR creation or update, approved-scope revision PR creation, and Blueprint validation after existing gates pass. It does not auto-confirm multi-repo scope, mark blueprints not required, approve PRs, merge PRs, or publish packs.
Handoff Pack preparation is separate from external publishing. Preparation can run automatically when gates pass, but publishing remains manual by default.
Newly flagged Handoff Pack First initiatives use source-led readiness, target confirmation, direct draft pack generation, approval PRs, and explicit publication without mandatory PRD or Delivery Plan gates. Existing and unflagged initiatives keep the classic workflow.
Handoff Pack First rollback uses handoff_pack_first_workflow_enabled=false: new mutations stop, existing records render read-only from persisted workflow_mode, and no automatic migration runs.
Discovery repo scope is retrieval scope only. Handoff Pack repository scope and blueprint mappings remain authoritative for implementation.
Repository scope for each Handoff Pack candidate is inferred, then confirmed or amended before it controls repo-specific refinement, blueprint output, or pack output.
Blueprint content is intentionally edited in GitHub for this version.
Handoff recovery controls are explicit: Refresh from GitHub is for stale Blueprint PR state, and Regenerate Blueprint PR is for gate-allowed PR repair.
GitHub read permissions are enough for indexing, pre-flight signals, discovery, and repo/docs refinement. GitHub write permissions are only needed for blueprint workflows and explicit Handoff Pack publishing to draft pull requests.
Linear workflow statuses remain team-owned. inrelay uses task IDs, issue descriptions, issue links, and labels for reconciliation.