Program Truth
A TPM workflow for checking whether the status story matches the work underneath it.
Context
Program Truth is a documentation-first workflow for program operators who need to reconcile execution reality across Jira, Confluence, meeting notes, and local planning files.
The familiar problem: the parent ticket says one thing, while task-level evidence shows something messier. A status update can look green because the summary is clean, not because the work is actually unblocked.
What changed
- Split status work into facts, assumptions, blockers, owners, dates, and open questions.
- Made the update traceable to source evidence instead of relying on memory or meeting narration.
- Treated the parent-ticket story as a claim to verify, not the final truth.
- Kept the output reviewable enough for leadership updates without exposing private project details.
Evidence I can show
- Public repository structure and prompts for evidence-first program review.
- Sanitized examples of how blockers, owners, and decisions are separated before a report is written.
- Npm installer and doctor flow for setting up the skill in local agent environments.
- A repeatable workflow that can be adapted to Jira and Confluence-heavy delivery environments.
Why It Matters
Good status work is not about making the slide look green. It is about knowing what is true early enough to do something about it.