AI Skill Source Integrations
AsanaAsana

Turn Asana project decisions into AI Agent Skills

Develop AI Agent Skills from task discussions, dependencies, and the decisions behind a delivery plan. Preserve why work moved, what could continue, and which conditions still had to be met.

Keep the reasoning behind the revised plan

Illustrative project / R-42

Regional rollout

8–12 July
Follow the change in the plan
Task / Owner
Correct sample dataData owner8–9 Jul
Draft rollout guideEnablement8–10 Jul
Review readinessReview lead10 Jul
Start pilotDelivery lead11 Jul
Review before pilot
Delivery lead / Planning note
“Review the corrected sample before the pilot. The rollout guide can be drafted in parallel.”
Reasoning to retain

Keep the review condition visible

The plan depends on a representative sample reaching the reviewer. Guide preparation has a separate path and can proceed from the existing outline.

Task / Owner
Correct sample dataData owner8–10 Jul
Draft rollout guideEnablement8–10 Jul
Review readinessReview lead10 Jul / Needs review
Start pilotDelivery lead11 Jul / Needs review
Review date needs attention
Data owner / Task comment
“One sample still uses the old mapping. The correction needs another day, so the readiness review must wait.”
Reasoning to retain

Find which work the change affects

The sample now overlaps the planned review. That dependency calls for a revised review date and a check of the pilot milestone. The guide draft can continue.

Task / Owner
Correct sample dataData owner8–10 Jul
Draft rollout guideEnablement8–10 Jul
Review readinessReview lead11 Jul
Start pilotDelivery lead12 Jul
Dependency preserved
Delivery lead / Replanning note
“Move the readiness review to 11 July and the pilot to 12 July. Keep the guide draft moving. The pilot still depends on the review.”
Reasoning to retain

Preserve the condition behind the new dates

The revised dates give the review its required input. They record the intended sequence. The review outcome still determines whether the pilot is ready to proceed.

An illustrative schedule and task discussion. The dates express a plan. They do not establish that the work or review is complete.

The opportunity

The date changed.
The explanation is the asset

Project history records more than a sequence of tasks. Comments and dependency changes can reveal how an experienced lead recognized a blocker, protected a review, and kept other work moving.

Develop that judgment into AI Agent Skills that help teams ask what a delay affects, identify who needs to respond, and preserve the conditions behind a revised commitment.

The decision worth preserving

Move the review and pilot. Keep the independent draft moving.

One changed input. Different consequences for different tasks.

01 / Read the dependency

Which work actually needs that input?

A dependency explains a sequence. The task discussion explains why it matters. Examine the review path alongside the work that can continue, and retain the owner’s reasoning for each.

Dependency study / Regional rollout
Review path
PilotRequires the review outcome
Parallel work
Source explanation / Required input
“One sample still uses the old mapping.”

The review needs a representative input

A missing correction changes what the reviewer can evaluate. Ask whether the sample is ready and which review tasks depend on it.

Ask the project owner

What must be corrected before this review can answer its question?

Source explanation / Decision before the pilot
“The pilot still depends on the review.”

The revised date carries the same condition

Moving a milestone does not establish readiness. Preserve the review requirement and the owner who can confirm its outcome.

Ask the project owner

What result must the reviewer record before the pilot can proceed?

Source explanation / Work that can continue
“Keep the guide draft moving.”

Keep independent work separate

The draft can use the existing outline while the sample is corrected. Retain that explanation so a future plan change does not delay work unnecessarily.

Ask the project owner

Which part of this task can continue with the inputs already available?

This example describes the dependencies in one plan. A project owner establishes which inputs and review outcomes are required in another.

02 / Develop the reusable reasoning

Carry the decision into the next plan

Turn the project discussion into candidate skill behavior. Keep the source, rationale, and limits together so an expert can decide what applies beyond this rollout.

Source decisionReasoning to preserveCandidate AI Agent Skill behavior
1

Move the review

The sample needs another day.

The review needs a corrected, representative input. A calendar slot alone does not make that input ready.

Identify the affected review, ask the data owner what remains open, and surface the scheduling consequence.

2

Continue the draft

The guide uses an existing outline.

This work has the input it needs. Its draft can progress while the sample correction is underway.

Separate tasks that need the delayed input from tasks that can continue. Confirm that distinction with the owner.

3

Preserve the review condition

The pilot follows the readiness decision.

A revised pilot date preserves the intended sequence. The review still has to establish readiness.

Carry the required review outcome and its owner into the revised plan. Keep unresolved conditions explicit.

These are candidate behaviors for expert examination, with the original task discussion and dependency evidence attached.

Explore skill validation

Begin with a plan that had to change

What did your team protect when the plan moved?

Choose a project, a meaningful change in its dependencies, and the lead who made the call. Explore how that delivery judgment could become an AI Agent Skill.

Explore your Asana sources