Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Client Feedback to Build Brief

    0

    Turn client messages and screenshots into source-linked requirements, testable tickets, and an agent handoff.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Client Feedback to Build Brief

    Client Feedback to Build Brief

    Example session with this skill installed

    Turn these notes into a build brief and agent prompt. Do not code or create issues.
    S01 — Client owner, 09:00: “Change the submit label to ‘Send request’. Keep email/password login.”
    S02 — Same owner, 09:10: “After submission, show a receipt number. If it fails, preserve everything I typed.”
    S03 — Designer, 09:15: “Maybe remove login completely and use a public link?”
    S04 — Client owner, 09:20: “For this release, keep login. Public access can wait.”
    No repository, receipt format, or backend contract is provided.

    • Read your context and instructions
    • Compiled the client feedback to

    Scope: improve the signed-in submission flow. Preserve email/password login. Public access is deferred by S04. No code or external issue was created.

    IDRequirementSourcesStatus
    R01Submit control reads exactly “Send request”S01READY
    R02Success displays a receipt numberS02NEEDS DECISION: source/format
    R03Failed submission preserves entered valuesS02READY; current behavior unverified
    R04Keep email/password loginS01, S04READY constraint
    R05Public accessS03, S04DEFERRED

    Decision D01: What generates the receipt and what is its display format? Do not fabricate an endpoint, database field, or number.

    T01 — Update submit copy. Sources S01; requirements R01/R04. Acceptance: the signed-in submission control reads exactly “Send request”; login remains required. Discover the control and localization pattern. No file path is known.

    T02 — Preserve values after failure. Source S02; requirements R03/R04. Acceptance: given a completed form and a failed submit request, entered values remain available for retry and success is not shown. Proposed extra check for confirmation: prevent duplicate creation on retry.

    T03 — Show receipt on confirmed success. Source S02; R02. Blocked by D01 and discovery of the response contract. Acceptance after D01: confirmed success displays its agreed receipt; failure never displays a fabricated receipt.

    Suggested product priority: prevent lost input first, receipt confirmation second, copy third. Implementation may begin with T01 independently; T03 stays blocked. Effort, owners, dates, and validation commands are unknown.

    Agent handoff: inspect repository instructions, login boundary, submit control, localization, and request state. Implement T01/T02 only if coding is authorized. Preserve login. Hold T03 until D01 is answered. Discover relevant checks and report actual results. Do not deploy or create issues without a separate request.

    Coverage: all five requirements map to tickets, a protected constraint, or a deferred item. This is a fictional worked example, not a production run.

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

    About this skill

    Turn scattered client feedback into a build brief your coding agent can follow.

    Built for solo developers, freelancers, and small product teams receiving changes through chat, meeting notes, or screenshots. The workflow connects each requirement to its source, separates decisions from suggestions, preserves exact UI copy, and produces testable ticket drafts plus a bounded implementation handoff.

    What you get

    • Source ledger and atomic requirements with confidence and readiness.
    • Conflict/decision log and explicit scope boundaries.
    • Dependency-ordered ticket drafts with acceptance criteria.
    • A paste-ready prompt for your coding agent.
    • Reusable output contract and a fictional worked example.

    Created by cursi.dev. Includes reusable instructions, an output template, and a clearly labeled fictional example.

    Output depends on readable inputs, explicit scope, and known decision authority. Screenshots do not prove backend behavior. The skill does not verify implementation or guarantee delivery estimates; missing evidence and unresolved conflicts remain visible.

    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 25 days ago

    Permissions

    No special permissions declared or detected

    Listed25 days ago

    What's inside

    Frequently Asked Questions

    No. Paste the messages or supply files you are authorized to share. It does not connect to messaging accounts or collect conversations.

    Yes, when your agent supports image understanding. It preserves the working language and exact requested copy. Unreadable text is flagged rather than guessed; text-only agents can use a transcription.

    It drafts tickets and a coding-agent handoff. Creating issues, editing files, coding, or publishing requires a separate user request and suitable tools.

    It records the alternatives and their sources, uses explicit decisions when authority is established, and holds unresolved work instead of silently choosing.

    New in Business & Operations