I am a technical people leader with a passion for building teams that make amazing things. Overall with 16+ years of experience with a broad range of technical.
My kid is learning phonics.
While explaining what he learned, he told me that when A and I come together, "A" makes the sound and "I" goes silent.
Apparently, phonics predicted the future of Artificial Intelligence.
Artificial is getting louder. Intelligence is going silent.
AI made documentation cheap to generate. It didn’t make understanding automatic.
A paragraph explains. A diagram connects. A decision table exposes exceptions.
The skill is choosing the form that fits the question.
One field guide: https://t.co/OQ1wj1AOxO
“They spent 10 minutes reading the docs.”
Learning? Confused? Making coffee?
Ask them to trace a request.
Comprehension Bench tracks answers, manual scores, missing work, and practice history.
How do you test understanding?
https://t.co/VuvhmmLKJD
“Everyone knows what ‘workspace’ means.”
Product means a collaboration area.
Infrastructure means a deployment environment.
Which definition did your AI retrieve?
Org Lexicon adds scope, sources, and human approval.
https://t.co/xXG8z8Zsfi
“We changed the policy.”
Did anyone tell the onboarding guide? The support docs? That forgotten FAQ?
Decision Ripple turns a changed decision into a queue of passages worth reviewing—with a reason for every match.
https://t.co/DJNd7cyrHR
“Here’s the architecture diagram.”
Great. Where does the request fail? Which source lines support that arrow?
Living Explainers lets readers explore authored request paths, inspect references, and see stale evidence.
https://t.co/iD5RCUSE15
“Editors can share.”
“Inactive members cannot.”
So… can an inactive editor share?
That’s a product decision waiting to become a bug.
Intent Workbench lets you run the rules and inspect conflicts before coding.
https://t.co/2q14IMCuHg
“Just make it clearer.”
Then “must not” becomes “may.”
24 hours becomes 48.
An approval condition disappears.
Would you catch all three?
Meaning Diff flags these patterns for review.
https://t.co/OXjjD3nkDb
“Done. All tests pass.”
Against which files? Before or after the last edit?
I built Proofpacket to keep AI completion claims tied to recorded commands and file fingerprints.
What evidence do you ask your coding agent for?
https://t.co/vvo2TAlNd3
“It’s valid JSON.”
Cool. The count is true and the required list is empty.
Your handoff also skipped “Unresolved questions.”
Output Contracts checks the explicit rules your downstream workflow depends on.
What’s your output contract?
https://t.co/Yx0FVRLsuY
For years, technical debt looked like TODOs.
Missing tests. Missing docs. Refactors postponed.
Now AI writes the code, tests, and documentation in minutes.
The new technical debt is TULU:
“To Understand Later, Usually.”
And that debt is far more dangerous.
Most writing skills clone content across platforms and auto-publish. Engineering is build, validate, push. The push is yours.
7 skills, 6 formats, one voice profile that's a file you edit, not a slider.
https://t.co/aDxwbXsAIn