jon-devlapaz Technical Assessment Loop
Use this skill at checkpoints to decide whether evidence supports continuing, changing course, or closing.
Workflow
- Restate objective, current plan, and current system state.
- Inventory evidence: changed files, tests, inspections, review findings, artifacts, user feedback, and unresolved assumptions.
- Compare evidence against requirements, integration state, verification, validation, and risk.
- Identify drift: scope creep, weak evidence, stale assumptions, hidden dependencies, or validation gaps.
- Decide one action: continue, rework, split scope, escalate, pause for input, or close.
- Record the decision, evidence, residual risk, and next checkpoint trigger.
- Do not close work because tests passed if validation or user intent is still unproven.
- Output a checkpoint note: objective, evidence, gaps, risk, decision, next action.
Source grounding
Start with references/source-grounding.md, then inspect Section 6.7 pages extraction/pages/page_165.md through extraction/pages/page_171.md before making technical-assessment claims.