Skip to main content

Implementation Packs And Draft Pull Requests

Implementation packs are generated from:

  • The approved product document.
  • Completed or manually closed discovery.
  • The generated task.
  • Relevant codebase index summaries and selected full files when GitHub access allows it.
  • Blueprint mappings when blueprints are enabled.

Without blueprints, implementation-pack generation is normally triggered when a synced Linear task moves into an in-progress state.

With blueprints enabled, packs wait until the relevant blueprint is approved or explicitly marked not required. Users can then generate approved blueprint packs from the Work Package UI.

Each pack includes:

  • Task summary.
  • Acceptance criteria.
  • Relevant product context.
  • Technical context.
  • Suggested approach.
  • Implementation checklist.
  • Open questions.
  • Testing notes.
  • Out of scope.

Draft Pull Requests​

When auto pull requests are enabled and GitHub write permissions are available, Relay creates a branch named like:

relay/ENG-123-implement-the-checkout-retry-message-hierarchy

It writes RELAY_PLAN.md and opens a draft pull request. When the pull request becomes ready for review, Relay can post a review comment. When the pull request is merged, Relay marks the task done from the GitHub webhook.