Create initiatives in Slack or the UI. In the UI, choose work type, expected size, and optional initial context when profiled intake is enabled.
Add all available context before drafting, including direct Markdown when it is the fastest way to capture a brief.
Treat low-confidence, warning-heavy, or hard pre-flight reports as a prompt to add context, acknowledge risk, or resolve conflicts.
Use the UI for PRD section review, gap resolution, rejection, approval, and export.
Approve only when gap sections are filled or marked not applicable and the PRD is good enough to drive Technical Discovery & Refinement.
Confirm or amend discovery repo search scope when inrelay asks, accept or edit cited code-inferred answers where they are correct, then answer remaining discovery questions with concrete implementation constraints and source-backed assumptions.
Generate and shape the draft Delivery Plan after discovery is complete or intentionally closed, reviewing retained target-context assumptions when material signatures have not changed.
Use Send to Linear when the inrelay task list is final and the team is ready to create issues.
Confirm or amend Handoff Pack repository scope, then let inrelay run automated readiness, resolve hard repo/docs blockers, and carry forward repo/docs questions only when the UI asks for that decision.
Use Linear for day-to-day delivery state after handoff.
Use GitHub for blueprint review and merge, and publish prepared Handoff Packs explicitly when enabled.