# What each quadrant leaves behind

Turn repeated work into reusable AI workflows. Make decisions, ownership and growth visible.

[Human guide](https://jasminejames.dev/leading-deeper/choose-ai-assistance/#framework-artifacts) · [Structured JSON](https://jasminejames.dev/leading-deeper/framework-artifacts.json)

These are adaptable examples, not internal documents or claims that a particular automation is deployed. A skill describes reusable work; the agent environment controls tools, access, runs and review.

## Local skills

Work I own · Low leverage

**Artifact:** Reusable instructions for gathering context, drafting and checking a personal workflow.

**Example:** Adaptable example: prepare a stakeholder-update draft from selected repository and issue-tracker material; flag priority conflicts for a person.

**Purpose:** Reduce repeated preparation while keeping the update owner responsible for accuracy and stakeholder decisions.

## Central skills

Work my team owns · Low leverage

**Artifact:** A shared skill or automation with a named owner, scoped access and an explicit review step.

**Example:** Adaptable example: draft a support answer from approved knowledge, or propose a knowledge update for human review.

**Purpose:** Make recurring work reusable across the team. Central means shared and maintained; the agent environment controls tools, read/write access, runs and review.

## Decisions and ownership agreements

Work I own · High leverage

**Artifact:** An agreement covering the outcome, why this person, decisions they own, support and a review point.

**Example:** Adaptable example: agree how an engineer new to CI will lead a migration, what they decide and where the leader will help.

**Purpose:** Align meaningful ownership with strengths and growth, while making leadership decisions and support explicit.

## Team-owned plans and evidence

Work my team owns · High leverage

**Artifact:** A team-owned plan, decision record and evidence of results and learning.

**Example:** Adaptable example: a CI migration plan with cross-team decisions, checks for workflow continuity and performance parity, and learning to review.

**Purpose:** Support autonomous delivery and growth; assess the customer outcome and what the engineer learns as work progresses.

These artifacts support better decisions, autonomy, growth and customer outcomes. Producing a document is not the outcome.
