More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Creative Briefs That Survive First Contact

    1

    Turn a vague idea into a tight, two-page brief a builder can execute without guessing: ten intake questions, measurable objectives, fenced scope, named approvals, marked assumptions.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Creative Briefs That Survive First Contact

    Creative Briefs That Survive First Contact

    Example session with this skill installed

    I run a fictional mobile bike-repair service called Spoke & Stone. I need a brief for a booking website before the spring riding season. I can answer some questions and want you to decide the rest and mark your assumptions. Give me the full brief plus the rubric score.

    • Read your context and instructions
    • Compiled the creative briefs that

    BRIEF — Spoke & Stone booking website, invented scenario and numbers for this demo only.

    Snapshot: a one-page booking site for Spoke & Stone, a fictional mobile bike-repair service, launching three weeks before spring riding season to turn riders with a broken bike into booked repair visits.

    Audience: primary — city riders whose bike just broke; they browse on phones, decide in under a minute, and book by tapping. Desired behavior: book a repair visit. Secondary: local cycling clubs — they change the work only by needing a group-booking link.

    Objectives: 60 booked visits within 30 days of launch, counted in the booking form; quote-to-booking path within 3 taps, verified by click test.

    Key message: Spoke & Stone fixes your bike where it broke. First draft ("Book bike repair that comes to you") failed the could-only-belong-here test and was rewritten.

    Voice and tone: direct, not blunt. Capable, not boastful. Plain, not flat.

    Visual direction: workshop calm — charcoal, cream, safety yellow; one bold sans for headings. Like: repair-service sites with large tool photography and clear pricing. Reject: dark-mode storefronts, pop-up discount banners.

    Scope: one page with hero, service list (5 services), booking form, service-area map. Out of scope: online parts shop, accounts, blog.

    Constraints: hard — launch 21 days before season; no budget for a booking platform, so the form emails the owner directly. Soft — service count may grow from 5 to 7.

    Success criteria: 60 bookings within 30 days; quote-to-booking within 3 taps.

    Approvals: the owner approves design and copy by the Friday before launch week; approved means a yes in writing to the final draft. First draft named no deadline and scored 0 on approvals; fixed before delivery.

    Assumptions marked: booking form emails the owner directly; service count starts at 5. Rubric score: 12 out of 12. The brief ships.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    A brief is a translation job, and most of them fail at it: the builder guesses, the guess is wrong, and the mistake surfaces late when it is expensive. This skill starts with a ten-question intake — what is being made, why, for whom, what they should do afterward, personality, visual direction, scope, constraints, measured success, and who approves — run in a single round, with "decide for me" accepted wherever the requester defers and every filled-in assumption marked so it can be corrected cheaply. From there it writes the brief in a fixed order: a one-paragraph snapshot, a primary audience with a desired behavior, objectives each paired with a number, a deadline, and a counting method, one key message that could only belong to this project, voice adjectives each paired with what they are not, visual direction with reference images plus rejection notes, countable deliverables with an explicit out-of-scope list, hard limits named before soft ones, success criteria restated as an acceptance checklist, and approvals naming the approver, the scope, the deadline, and what approved means. A six-line scoring rubric finishes the job: a brief ships at 10 or above out of 12, with no line at zero. Edge cases cover redesigns, campaigns, briefs for AI agents, missing budgets, disagreeing teams, and one-day jobs, and the failure-mode catalog names the wishlist brief, the adjective brief, the approval-shaped hole, objectives without signals, silent invention, and the brief that grows.

    • It cannot brief a project whose core idea is still undecided; that is discovery, and the skill stops rather than freezing the wrong idea.
    • It produces a brief, not a full specification or development ticket; those come after the brief settles what and why.
    • A brief is only as good as its approver: if no one can say yes, the skill names that hole but cannot fill it.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    No special permissions declared or detected

    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Answer what you can and defer the rest. The skill asks the sharpest missing questions in one round, accepts "decide for me" wherever you defer, and marks every assumption it fills in so you can correct it cheaply.

    About two pages. Anything longer is a specification wearing a brief's clothes, and nobody reads it twice. The template keeps every section tight by design.

    Put the disagreement into the brief as a named open question with an owner and a deadline, not smoothed over. A smoothed-over disagreement reappears as a revision round.

    New in Branding & Design