“Close the handoff after uploading the package.”
The earlier rule made an assumption
The wording treated upload completion as sufficient. Keep this version to understand what the later review changed.
Historical wording / Superseded in this exampleDevelop AI Agent Skills from the reasoning inside runbooks, decision records, and page discussions. Preserve why a rule exists, which exception it allows, and who can explain the boundary.
Keep the explanation in the margin connected to the rule
Runbook / Version 6
Complete a delivery with a clear reference, a receiving owner, and an explicit acceptance record.
The opportunity
A runbook tells a team what to do. The discussion around it can explain which failure it addresses, what a reviewer challenged, and why an exception is narrower than it first appears.
Develop that reasoning into AI Agent Skills that explain a requirement, recognize its limits, and bring unresolved questions back to the people responsible for the work.
01 / Follow how the guidance changed
The old wording, the reviewer’s explanation, and the recorded decision serve different purposes. Preserve their relationship when developing a candidate skill.
“Close the handoff after uploading the package.”
The wording treated upload completion as sufficient. Keep this version to understand what the later review changed.
Historical wording / Superseded in this example“The receiving team could not use the file. We need their confirmation.”
The comment records why the old condition was insufficient. It is evidence for the reasoning, not a substitute for the agreed requirement.
Review evidence / Explain the reason for the change“Retain receiving-owner confirmation. The pilot may use a next-day review window.”
The updated runbook requires acceptance and qualifies the pilot timing exception. Keep both connected to the owner and the decision record.
Current example / Acceptance required, pilot timing qualified02 / Develop the knowledge into a skill
Preserve the requirement, the reason it exists, and the exception’s limits. Test the explanation with the owner before carrying it into another workflow.
Explore skill validationStart with the experience behind the record
Bring the page, the discussion that shaped it, and the person who understands the exception. Explore how that knowledge could become an AI Agent Skill.
Explore your Confluence sources
Keep identity and responsibility together
Retain the source reference and the receiving owner. A folder name alone cannot establish who accepted the work.
Preserve the experience behind the requirement
The added confirmation responds to a failed handoff. Keep that rationale attached so the requirement can be examined in another situation.
State what the exception actually changes
The timing allowance has a defined scope. Preserve the acceptance requirement so the exception is not broadened into automatic closure.