← All skills

Work records · Workhuman AI practice

Keep the reasoning after the session

I use a logging workflow to preserve the problem, the decision and its evidence, then prepare useful progress records.

log-work
Context architecture · Relevant knowledge, organised before generation.
Context architecture · Relevant knowledge, organised before generation. Conceptual illustration created with AI.

The problem

Why this belongs
in the workflow.

Decisions and evidence can disappear into chat history, making later explanations and handoffs harder.

What the skill makes explicit.

01

Record why a change was made as well as what changed.

02

Turn follow-up work into clear, ordered actions.

03

Prepare tracker updates through the configured workflow and its delivery boundary.

Evidence and learning

From instructions
to practice.

The supplied version includes operational adaptations for structured task handoffs and lessons from earlier integration problems.

Contribution and evidence scope

A configured tracker workflow is not proof that tasks were created or that a team adopted it. No tracker actions run from this portfolio.

Source: the supplied log-work skill and associated records. Internal component identifiers and company endpoints are omitted.

Process flow

How this skill handles a task.

Decisions and evidence can disappear into chat history, making later explanations and handoffs harder.

  1. 01

    Capture context

    Collect the problem and relevant session context.

  2. 02

    Record the decision

    Preserve what changed and why it changed.

  3. 03

    Attach evidence

    Connect the record to supporting evidence.

  4. 04

    Prepare the handoff

    Prepare ordered next actions and the configured delivery.

DECISION CHECKPOINT

Is the delivery configuration confirmed?

Proceed

Prepare the handoff through the configured workflow.

Alternative / follow-up

Keep an internal draft when external delivery is unconfirmed.

Editorial map of the documented instructions, not a recorded execution.

Inside the skill

Instructions you can inspect.

Source excerpt from log-work/SKILL.md, lines 12 to 16. The same text is available directly below.

The rule that matters most

Log what was decided and why, not what was typed. A list of files touched is worthless in three weeks. The reason a decision went one way, the number that changed someone's mind, the thing that turned out to be wrong — that is what gets read later.

If the session produced no decision, write one line saying so and stop. Do not pad.