---
name: design-agent-product
description: "Consult this skill when asked to design a research-brief workflow, transfer a workflow contract to meeting decisions, or prepare an instruction-pack rights inventory. Covers trigger, inputs, artifact, acceptance, failed-input recovery, permissions and plain-host comparison. Use for narrow specification-only questions and full product design."
---

# Design an agent workflow

Read [the worked blueprints](../../references/product-blueprints.md). Start with
the user's workflow and available technology. Select an existing package to
improve when it fits. Define an observable output before writing instructions.

For a narrow specification or output-contract question, return only the requested
fields, with one short sentence per field. Aim below three quarters of a supplied
word limit so field labels and formatting fit. Preserve
source/uncertainty, permission and recovery boundaries; omit unrequested examples,
setup and evaluations. Add worked, adverse and transfer tasks when requested or
when preparing the complete product design below.

For a complete product design, write one workflow contract with:

- User, trigger, present workaround and the change they need.
- Input, artifact, acceptance test, failed-input behavior and recovery.
- Required host capabilities, data locations and user-owned keys or accounts.
- Original assets, third-party prerequisites and license obligations.
- One worked example, one adverse case and one different-context transfer task.
- A comparison with the host's baseline behavior on the same task.

Keep current user-supplied evidence separate from bundled illustrations. Never
reuse a reference example's facts or locators as evidence for the user's task.
When sources are absent, produce a specification with placeholders or mark the
entire worked example, including claims and locators, as synthetic. A factual
brief requires the user's sources; ask for them and retain missing evidence as
unknown. Label supplied observations, illustrative content and inferences.

Use a portable skill for repeatable judgment; use a script for deterministic
mechanics; add MCP only when the task requires connected data or actions. Keep
instructions and reference resources small enough for selective loading.

Record host requirements, user data locations and relevant usage limits. Package
self-service setup, diagnostics, uninstall and a known-issues guide. Measure
task cost and assistance rather than promising autonomous or error-free work.

Return the contract and one improved artifact when implementation is authorized.
Retain license and attribution requirements for reused code and resources.
Distinguish source generation, tested host behavior and provider approval.