> ## Documentation Index
> Fetch the complete documentation index at: https://docs.integratewise.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Product Engineering User Path: From Discovery to Ship

> How product and engineering practitioners enter Spine, discover context, and move from understanding to action and follow-through.

The Product Engineering User Path follows the standard Spine flow, adapted for how PMs and engineers discover work, build context, and ship software. Each stage is supported by the unified context Spine Fabric assembles from tickets, code, design, and operations data.

<Steps>
  <Step title="Enter">
    Open the Product Engineering workbench from the workspace selector or a direct link.
  </Step>

  <Step title="Discover">
    Browse the Sprint Board, Roadmap, or Incident Queue to find work that needs attention.
  </Step>

  <Step title="Understand">
    Open an item to see linked entities, recent activity, and related incidents or releases.
  </Step>

  <Step title="Contextualize">
    Add or refine notes, update status, and tag stakeholders. Twin may surface missing links.
  </Step>

  <Step title="Decide">
    Choose the next action: move a ticket, approve a PR, or escalate an incident.
  </Step>

  <Step title="Act">
    Execute the action through a governed capability. Spine routes the request to the right source system.
  </Step>

  <Step title="Review">
    Confirm the outcome: updated ticket, merged PR, or resolved incident.
  </Step>

  <Step title="Continue">
    Hand off to the next owner. Continuity preserves full context for the next session.
  </Step>
</Steps>

### Related

* [Human Workbench](/internal-docs/domains/product-engineering/human-workbench)
* [AI Workbench](/internal-docs/domains/product-engineering/ai-workbench)
* [Execution Flow](/internal-docs/domains/product-engineering/execution-flow)
* [How It Works: Governed Actions](/how-it-works/governed-actions)
* [How It Works: Continuity](/how-it-works/continuity)