PMX · Product workflow · Prototype

Make the next
decision clear.

The PRD exists. What can engineering do next—and what still needs an answer?

PMX connects product intent, engineering review and delivery evidence. It puts the next decision in front of people, with the source context behind it, so work can move forward without reconstructing the agreement from a chat.

Explore the workflow ↓
Illustrated workflowExample · Activity export

Next decision

Is the intent clear enough
to investigate the approach?

A request to export activity does not need every implementation detail settled before engineering can explore the options.

Proposed activity
Feasibility investigation
Expected output
Options, constraints and a recommendation
Decision stays with
The accountable reviewer and receiver

An explanation of the product flow, not a live project or an approval.

The product question

Less coordination.
A clearer agreement.

Coding agents make implementation faster. They still need to know which problem matters, what was agreed, and whether a new answer changes the work.

The challenge is to capture that meaning without turning product development into a long form. PMX reuses existing context and brings forward the decisions that block the next step.

From intent to results

Keep the thread intact.

  1. 01

    Product intent

    Bring the existing PRD from Linear or start a working draft. Keep the source and the proposal distinct.

  2. 02

    Engineering activity

    Choose what should happen next: technical design, investigation or implementation planning. Define its expected output.

  3. 03

    Review & agreement

    Inspect the assessment and its source quotations. Resolve blocking decisions and agree the scope and approach.

  4. 04

    Handover

    Issue a versioned package. The receiver can accept it or ask for clarification before work proceeds.

  5. 05

    Results

    Record implementation, verification, release and outcomes separately, against the work they describe.

Decisions behind the design

Helpful assistance.
Explicit authority.

Reuse the source

Linear holds the source. PMX captures it and keeps working drafts and recorded decisions separate. Editing a draft does not silently publish it back.

Review the actual revision

Agreement belongs to a specific version and its context. Changed answers can reopen review instead of carrying an old approval forward.

Show what the evidence proves

An implementation report, a passing check and a release are different records. AI proposals stay advisory; reported evidence is not independent verification.

Current state · October 2026

Built for human decisions.
Designed toward delegation.

The working prototype covers source capture, review, receiving questions, handover and delivery records. A September walkthrough exercised the flow through the hosted feedback pilot using explicitly labelled test work.

That demonstrates a bounded workflow, not customer adoption or a measured productivity gain. The repository remains private. Organisational identity, multi-user access controls and autonomous execution are not claimed as delivered.

The longer-term aim is to let an organisation delegate more of the lifecycle to its chosen agents, one authorised scope at a time.

Discuss PMX ↗
Next project · WirkraumFrom source data to a field tool ↗