AI Coding Tools
5/5
From asking about code to implementing and verifying real changes.
In this example, independent implementation tasks include requirements, changes, post-change checks, and an explicit record of unresolved issues.

AI Native Score
Platform engineer
12 dimensions reviewed
The shape of a workflow
51/60
Strong verification habits connect implementation, external tools, and repeatable evaluations. More systematic model comparisons would make the next choice easier to defend.
How the score works0 at the center · 5 at the edge
The full picture
What the score reflects, one practice at a time.
5/5
From asking about code to implementing and verifying real changes.
In this example, independent implementation tasks include requirements, changes, post-change checks, and an explicit record of unresolved issues.
5/5
Using connected tools and checking what actually happened.
Connected-tool results are read back and checked for completeness, with errors followed by recovery and another verification.
4/5
Applying reusable procedures and improving them through use.
Task-specific skills are applied and reviewed. A revised procedure is visible, but its subsequent use is not fully established.
3/5
Running automatic checks at the moments that matter.
Hooks perform automatic checks at useful moments. Follow-up evidence for exception handling is still missing.
5/5
Giving an agent the right information, and correcting it when needed.
Outdated context is corrected against source material, and the correction changes both the next decision and the delivered result.
4/5
Carrying useful knowledge across sessions and applying it again.
Saved rules inform work in another session. A validity review exists, but a later reapplication of the reviewed version remains unverified.
5/5
Designing feedback, retries, and clear stopping conditions.
A later execution reads persisted progress, respects retry and stop rules, and verifies its outcome separately from the generator’s own claim.
4/5
Connecting stages with explicit inputs, outputs, and dependencies.
Outputs flow between stages and some inputs are validated. Recovery and whole-flow validation are not completely demonstrated.
4/5
Dividing work between agents and checking the combined result.
Specialized agents return work that is integrated and checked for conflicts. Complete omission and duplication checks are still limited.
4/5
Keeping work separate and delivering it without unrelated changes.
Separate workspaces keep edits isolated. The delivery is reviewed, with incomplete evidence of the original workspace’s preserved state.
3/5
Choosing models for a reason and checking the effect of that choice.
Models are selected by role and used as assigned. Comparable evidence has not yet connected those choices to subsequent outcomes.
5/5
Evaluating AI outputs against criteria, then checking the evaluation itself.
Multiple AI executions are scored against defined criteria, grading errors are reviewed, and the corrected results are aggregated.
Keep doing this
Implementation and verification form one workflow, including an honest record of anything still open.
Progress survives between executions, and completion is checked independently.
Judgments are reviewed and corrected before they become a final result.
Try next
Compare two models on the same task and use quality, cost, and time to choose the next assignment.
Verify what happens when a handler fails, then confirm the recovery behavior in later use.
Connect the checked patch to the delivered commit and verify the original workspace stayed intact.