Skip to main content

Implementation Blueprints

Blueprints are an optional gate between Linear tasks and implementation packs.

Use blueprints when:

  • A task may touch multiple repositories.
  • Exact repository ownership is not obvious during discovery.
  • Engineers need to review implementation approach before an agent-ready pack is generated.
  • The team wants GitHub pull request review as the approval surface.

Blueprint Flow​

  1. Relay groups generated tasks into Work Packages.
  2. A user creates a blueprint pull request from the Relay UI.
  3. Engineers edit blueprint.md and relay.yaml in GitHub.
  4. Relay validates required sections, Mermaid architecture diagram presence, metadata shape, and metadata references.
  5. GitHub review state is reflected back into Relay.
  6. Merging the blueprint pull request approves the blueprint.
  7. Relay can generate repo-specific implementation packs for approved targets.

If no blueprint is needed, use No blueprint required in the Work Package UI and provide a reason. Relay still needs explicit repository mapping before implementation packs can be generated.