Skip to main content

Initiatives

Sign Up And Login​

Use the web app to create a workspace or sign in.

Signup creates:

  • A workspace.
  • A first team.
  • Your user account as an admin.
  • A 14-day trial.

Initiative List​

Use the Initiatives page to scan all active work grouped by state. Each initiative card shows:

  • Initiative title.
  • External ID, such as ENG-123.
  • Last updated time.
  • Current state.
  • Document confidence when a document exists.

Use Add New when you want to create an initiative from the UI instead of Slack. When profiled intake is enabled, choose the work type, expected size, title, and optional initial context. bug and patch are distinct types; only bug or patch work sized xs or s can use the low-risk lane, and only when repo, evidence, and blocker checks pass. You can add context later through direct inrelay upload, Slack, or email.

Initiative Detail​

The initiative page is the canonical workflow surface. It shows the five visible stages:

  • Shape Brief.
  • PRD Review.
  • Technical Discovery & Refinement.
  • Delivery Plan.
  • Handoff Pack.

In the Shape Brief stage, use the page for:

  • Direct Markdown context entry.
  • Direct file upload for source material.
  • Latest quality and readiness details.
  • Pre-flight status, risk signals, and acknowledgement state when available.
  • Readiness score, blocker explanations, pending readiness questions, and quality details.
  • Confidence, coverage, conflicts, warnings, missed thresholds, and relevance signals.
  • Included and excluded artefacts.
  • The next available web action, disabled reasons, and workflow blockers.
  • Active or recent operation feedback for queued, running, retrying, partial, failed, or stale Shape Brief work.

As the initiative progresses, the same page adds PRD section-quality or lightweight brief review, gap resolution, Technical Discovery search-scope confirmation, cited code-inferred discovery proposals, Technical Discovery questions, draft Delivery Plan shaping with retained target-context assumptions, explicit Send to Linear, Handoff Pack candidate scope, repo/docs refinement, blueprint gates, pack preparation, and explicit publish controls.

When one of those actions starts long-running work, the page shows operation progress inside the affected stage or substep. Examples include source ingestion, PRD generation, task generation, Send to Linear, lightweight brief generation, repo/docs refinement, blueprint validation, batch Handoff Pack preparation, and publishing. Needs attention means inrelay has not seen healthy progress within the expected window; the worker may still finish and update the operation later.

The current stage promotes one next action when inrelay has enough backend state to choose it. Other manual or recovery actions stay secondary so repeated refinement, sync, validation, or PR-regeneration controls do not become the normal path.