AI Skill Source Integrations
WorkdayWorkday

Turn Workday process history into AI Agent Skills

Develop AI Agent Skills from workforce requests, approval history, and the explanations behind an exception. Preserve the dates, responsibilities, and conditions that make a decision reusable.

Keep the reasoning behind every handoff

Illustrative process study

A transfer needs a new owner

T-104 / 1 of 3Submitted
Effective date01August
Process
Internal transfer
Destination
Field Operations
Handoff owner
Current team
Manager note
“The receiving team is ready for the transfer on 1 August.”

The requested date is clear. The owner named in the handoff still needs examination.

T-104 / 2 of 3Returned for clarification
Effective date01August
Process
Internal transfer
Destination
Field Operations
Handoff owner
Needs confirmation
HR review note
“The request still names the current team’s owner. Confirm the receiving team’s owner before the handoff.”

The returned step reveals the dependency: a team change also changes who must receive the work.

T-104 / 3 of 3Ready for further review
Effective date01August
Process
Internal transfer
Destination
Field Operations
Handoff owner
Receiving team
Process owner note
“The receiving team’s owner is confirmed for 1 August. Keep that confirmation with the request.”

The owner and date now agree. Final approval remains a separate step in the process.

Follow the request
An illustrative reading of process history, with fictional details.

The opportunity

The return for clarification is part of the expertise

A completed workflow shows the outcome. The review notes can explain why a request was returned, which dependency was missing, and what made the revised request ready to proceed.

Use that reasoning to develop AI Agent Skills that help teams ask a better follow-up question, recognize an incomplete handoff, and find the right process owner.

The request still names the current team’s owner. Confirm the receiving team’s owner before the handoff.
The review note that changed the request

01 / Follow the responsibility

Each handoff adds a different kind of judgment

The manager describes the intended change. HR spots the missing dependency. The process owner confirms what the next reviewer needs. Keep those contributions distinguishable when developing the skill.

Responsibility map / Transfer T-104
1Manager
2HR partner
3Process owner
Source explanation / Manager
“The receiving team is ready for the transfer on 1 August.”
AI Agent Skill candidate

Establish the intended change

Ask which team will receive the work and when the change is intended to take effect. Keep the request and its business context together.

Source explanation / HR partner
“Confirm the receiving team’s owner before the handoff.”
AI Agent Skill candidate

Recognize an incomplete handoff

A named owner may belong to the current team. Ask who will own the work after the change and what confirms that responsibility.

Source explanation / Process owner
“The receiving team’s owner is confirmed for 1 August.”
AI Agent Skill candidate

Carry the condition into review

Retain the confirmation, its effective date, and the responsible role. Ask the process owner which approval is still required before the request can proceed.

This example follows one request. Actual roles, routing, and approvals depend on the organization’s configured process.

02 / Keep time in the reasoning

A different date can change the question

A confirmation has a context. If the effective date changes, the explanation that supported the original handoff may need another look.

Carry that dependency into the AI Agent Skill. Help an agent compare the new request with the evidence behind it and ask what the process owner needs to confirm again.

Explore reasoning analysis
Same transfer / Different timing
Requested effective date1 Aug
Confirmed team readiness1 Aug
Question for the process owner

Does the confirmation cover this date?

The requested date matches the receiving team’s confirmation. Keep both records available for the process owner’s review.

A matching date supports the handoff. It does not replace the remaining approval.

Requested effective date24 Jul
Confirmed team readiness1 Aug
Question for the process owner

What needs to be confirmed again?

The request now takes effect earlier than the confirmation covers. Ask the owner to review the changed date and the receiving team’s readiness.

A confirmation for 1 August cannot establish readiness on 24 July.

Explore how a changed effective date alters the question. These are illustrative scenarios, not an approval rule.

03 / Develop the reusable reasoning

A skill that knows what to ask next

Translate the source explanation into a candidate instruction. Have the process owner examine its scope, exceptions, and evidence before it becomes an AI Agent Skill.

Explore skill validation
Candidate instruction / Workforce handoff review

Examine a transfer request

When a change moves work to another team, confirm the receiving owner and the intended effective date. If the date or destination changes, revisit the supporting confirmation with the process owner.

Source evidence
Request, review note, and owner confirmation
Review boundary
The organization’s process and required approvals
Access context
Use authorized evidence and retain only the personal details needed for the task

Begin with a process your team knows well

Which request needed someone to explain the exception?

Choose a workforce process, a request that took a different path, and an owner who can explain why. Explore how that judgment could support your next AI Agent Skill.

Explore your Workday sources