Aglet

Triage work when project decision context is missing

Missing decision context slows review and invites repeated debate. Triage should gather durable evidence, separate known rationale from reconstruction, and make the smallest context gap explicit so current work can proceed safely. A missing rationale should narrow current action without inviting a confident reconstruction from memory.

Establish what is happening

  1. State the current work

    Summarize requested outcome, implementation state, owner, dependencies, and current evidence. Identify the decision that collaborators need to understand and avoid treating a status or code shape as proof of intent.

  2. Collect durable clues

    Review linked requirements, changes, tests, feedback, decisions, handoffs, and timestamps. Mark what directly records rationale, what supports an inference, and what remains absent. Do not fill gaps from memory without attribution.

  3. Set a context boundary

    Choose reconstruct, request clarification, proceed provisionally, split scope, or pause. Record the current evidence and an owner for the missing decision context, including what would change the working assumption. Choose a provisional boundary when current work cannot wait for complete historical context.

What to carry forward

The output is a context brief that distinguishes documented facts, supported inferences, unknown rationale, and the next safe decision. Stop triage when collaborators can act within a stated boundary; do not invent a confident reason for an undocumented choice.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow