serban·BOB·HAI·PSR·ToT

Process

Workflow, Assessment, and Reassessment

Every piece of work flows through a consistent workflow: assess it honestly, execute through phases, reassess when new information arrives, and retrospect when complete. The process is lightweight — each assessment takes 2–5 minutes.

The Workflow
1

Initial Assessment

Evaluate the work: work mode, involvement, size, risk, confidence, spec quality. Takes 2–3 minutes.

2

Execute

Work through phases: Research, Specification, Implementation, Review. Both tracks active.

3

Reassess

When triggers fire (research done, issues found, phase change), update the assessment. Learning, not error.

4

Retrospective

At completion: was the spec good enough? What would we do differently? Feed learnings into future assessments.

Assessment Fields

Work Mode

AIHuman & AIHuman

Who leads the work?

Involvement

LightEngagedIntensive

How much human attention does this need?

Size

SMLXL

How big is the scope?

Spec Quality

HighMediumLow

How well-defined is the work? Clear acceptance criteria, or vague intent?

Risk

LowMediumHigh

How predictable is the outcome?

Confidence

LowMediumHigh

How well do we understand the scope?

Specification Quality

The quality of the specification determines the quality of the output. This is the most valuable assessment dimension.

QualityIndicatorsWhat It Means
HighClear acceptance criteria, testable conditions, defined scopeAI can execute with minimal iteration
MediumGeneral direction clear, details emergingExpect collaborative refinement
LowVague intent, undefined scopeResearch phase needed before specification
Spec Quality x Size: Risk Prediction

The strongest predictor of delivery risk. If you're in a red zone, invest in specification before starting production.

SizeSpec HighSpec MediumSpec Low
SSmooth, fastMinor iterationQuick to fix
MSmoothSome iteration expectedResearch needed first
LSmooth if specs existExpect surprisesStop. Invest in spec first.
XLDelivers if disciplinedRisk zone. Phase the delivery.Do not start. Spec first.
Assessment Evolution by Phase

Assessments reflect current knowledge. As work progresses through phases, understanding deepens and assessments naturally refine. This is learning, not error.

PhaseTypical ProfileConfidenceSpec Quality
RequestBased on description aloneLow — many unknownsLow (intent only)
ResearchHuman or Human & AI, IntensiveLow → Medium — exploringLow → Medium
SpecificationHuman & AI, EngagedMedium — path clearerMedium → High
ImplementationAI or Human & AI, EngagedMedium → High — executingHigh (spec is written)
Review / TestingHuman & AI, EngagedHigh — validatingHigh (testing against spec)
CompleteFinal assessmentHigh — retrospectiveEvaluated (was the spec good enough?)
Reassessment Triggers

Don't update constantly — reassess at these specific points. Skip updates for minor progress, routine implementation steps, and small issues quickly resolved.

Research complete

Work mode, size, confidence, spec quality

Discoveries change the picture

Spec approved

Involvement, confidence

Scope is now defined

First milestone

Risk, confidence

Reality validates or challenges plan

Issues discovered

Risk, confidence, size

New information

Phase transition

All dimensions

Natural checkpoint

Completion

Everything (retrospective)

Learning for future estimates

Communicating Assessment Changes

Assessment evolution is learning, not error. Frame changes honestly:

Complexity dropped

Research found a simpler approach

Complexity increased

Deeper analysis revealed details to address

Risk increased

Testing surfaced considerations we’re now handling

Confidence improved

We have a clearer picture now

Scope grew

As we mapped this, we identified related needs