AI SKILL · WORKING METHODS
Result definition Skill
Turn a broad request into a checkable delivery agreement.
Trial example · 2026-11-17 · Not validated in a business pilot
When to use it
Before work begins, when the team has not agreed what to deliver, for whom and what counts as complete. It supports requirement clarification, not stakeholder approval or legal, financial or other professional judgment.
Inputs
The user and accountable owner; the decision or action the user needs to take next; the original request; scope and timing; known constraints. If the user or purpose is missing, ask rather than invent a complete-looking plan.
Steps
- Extract the user, purpose and constraints and retain their sources.
- Translate activity labels into observable deliverables.
- Specify required content and exclusions.
- Propose checkable acceptance criteria and flag unconfirmed items.
- Submit the agreement to the requester and acceptance owner for review.
Output format
User: Intended use: Deliverable and scope: Acceptance criteria and basis: Exclusions: Open questions: Approver, version and date:
Acceptance and takeover
Each criterion must serve the intended use. Facts need sources; unknowns must remain visible. The owner must be able to assess each item. Pause for conflicting purposes, missing authority or unconfirmed standards. An agreement does not itself authorize external commitments or execution.
Copyable task instruction
Use the supplied request to prepare a delivery agreement. Identify the user and their next action, then organize scope, acceptance criteria and constraints. Separate facts, suggestions and unknowns. Do not guess missing data. Use the output format above; if purpose or ownership is unclear, first list the essential questions.
Repeatability check
Ask another colleague to use the same inputs and standards. Compare purpose, scope and key criteria. Record any extra explanations and revise the trial specification.