# Canonical NotFair workflow Human Guide

## What This Is For
Create grounded paid-media creative concepts, copy angles, refresh hypotheses, and measurable test briefs across advertising platforms. It gives the agent a clearer input/output frame for paid media: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the Canonical NotFair workflow agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for canonical NotFair workflow.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the Canonical NotFair workflow guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- a concept ID and hypothesis: audience × motivation × angle × format × one variable;
- the evidence source and claim ledger, with unsupported claims marked `needs_substantiation`;
- hook, primary message, CTA, destination, and placement adaptation;
- visual/production brief, including required rights or missing assets;
- success metric, guardrail, attribution window, observation window, and failure condition.

## Decision Points And Nuance
The original skill emphasizes: Supporting file: paid-ads/paid-ads-creative/SKILL.md, Work from named evidence, Produce a creative slate, Publication boundary.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- visual/production brief, including required rights or missing assets;

## Copy-And-Paste Prompt
```text
Use the Canonical NotFair workflow human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the nowork-studio/notfair-plugin skill entry for `paid-ads-creative`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# Canonical NotFair workflow

Read [`../../paid-ads/paid-ads-creative/SKILL.md`](../../paid-ads/paid-ads-creative/SKILL.md) completely, then follow it as the active workflow. Resolve every relative reference from that file against `../../paid-ads/paid-ads-creative/`.

---

## Supporting file: paid-ads/paid-ads-creative/SKILL.md

# Paid Ads Creative

Read `../shared/operating-contract.md` and `../shared/measurement-framework.md`. Route platform execution to `/notfair:google-ads-copy`, `/notfair:google-ads-assets`, `/notfair:meta-ads-creative`, `/notfair:paid-ads-x`, or `/notfair:paid-ads-linkedin` as appropriate.

## Work from named evidence

Start with a verified source: winning ads, search terms, customer research, approved landing-page claims, sales calls, reviews with permission, or a documented offer. Match each promise to its landing destination. Do not fabricate testimonials, ratings, prices, outcomes, availability, ownership, or product proof.

## Produce a creative slate

Deliver three distinct `ready_for_review` concept cards. Each card contains:

- a concept ID and hypothesis: audience × motivation × angle × format × one variable;
- the evidence source and claim ledger, with unsupported claims marked `needs_substantiation`;
- hook, primary message, CTA, destination, and placement adaptation;
- visual/production brief, including required rights or missing assets;
- success metric, guardrail, attribution window, observation window, and failure condition.

Do not make cosmetic variants of the same idea. Test one strategic variable at a time: hook, proof, format, angle, audience, or destination. Diagnose fatigue with complete-window frequency, link CTR, CPM, and delivery context before recommending a refresh.

## Publication boundary

Validate current platform specifications and policies from a verified source before publishing. A brief or generated image is not proof that a claim is permitted or that the platform accepted the asset. For platforms without a verified NotFair mutation surface, output an operator-ready brief and clear handoff rather than promising an upload.