Developer ExperienceDeveloper experience

Why

/eng-org:why

What it does

Identifies the first missing or incomplete pipeline stage for a requirement and prints the exact command needed to unblock it. One diagnostic block, one fix command — nothing more. This command is strictly read-only.

When to use it

Run when a requirement seems stuck and you need to know what is missing. It walks the pipeline forward from stage 1 and stops at the first gap, so you always get the actionable next step.

Inputs

  • REQ id

Outputs

  • diagnostic block (printed to terminal, no file written)

Example

/eng-org:why REQ-20260723-d904-01 — prints one block: the last completed stage, the current blocker, and the exact fix command such as "/eng-org:run-tests REQ-20260723-d904-01".