BUNDLE Security scanned5 skills

    Client Handover Kit — five documents for handing over a project

    Five client-ready documents for handing over a finished project, in one consistent style, each checked against your real code, data and running app.

    Finishing the code is half the delivery. The client also needs to know what's in the database, that it works, how to use it, where their data goes, and which accounts, renewals and backups they now own. This kit writes all five, ready to send as HTML or PDF.

    • DB Handover: "What's in our database?"
    • Test Handover: "Is everything really done?" (with a sign-off page)
    • Manual Handover: "How do my staff use it?" (real screenshots)
    • Dataflow Handover: "Where does our customers' data go?"
    • Handover Sheet: "What do we own, what renews when, and where are the backups?"

    They tell one consistent story. In the included example (a fictional coffee shop) the same refund issue appears as defect #3 in the test report, as a note in the user manual, and as a traced flow with an action in the data flow; the 759 orders counted in the database report are the same 759 the handover sheet's restore test brought back.

    Same rules in all five: nothing reported that wasn't actually checked; anything uncertain is settled with you before writing, so the client reads facts and decided actions; no passwords, secrets or real customer data; no developer jargon in the client's copy.

    Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.

    陸晉緣 | Chin-Yuan Lu
    Created by
    陸晉緣 | Chin-Yuan Lu
    $19$25
    Save 24% · $6

    One payment, lifetime access. 5 skills unlock instantly in your library.

    Money-back guarantee

    Instant unlock in your library

    Free updates from the creator

    What's included

    5 skills
    1/5
    Dataflow Handover — where your client's data actually goes

    A business-level data flow from your code: where data comes in, what happens to it, where it's stored, who sees it and where it leaves, every arrow traced to code and every gap settled with you before writing.

    View skill
    $5$3.80Save 24%
    2/5
    DB Handover — a database report your client can read

    Turns your project's database into a plain-language handover document for the client: what each table holds, how they connect (ER diagram), what the statuses mean, where personal data lives, and the agreed actions.

    View skill
    $5$3.80Save 24%
    3/5
    Handover Sheet — every account and renewal your client owns

    Scans your project for the services it depends on, checks real certificate and domain expiry dates, settles ownership with you, and writes the operations sheet your client keeps: who owns each account, who pays, when it renews, where the backups are, and what still has to move.

    View skill
    $5$3.80Save 24%
    4/5
    Manual Handover — a user manual with real screenshots

    Walks your running app role by role, one action per step, captures real screenshots, and writes the manual your client's staff can follow alone, without passwords, customer data or developer jargon.

    View skill
    $5$3.80Save 24%
    5/5
    Test Handover — an acceptance report that proves it's done

    Maps every agreed feature to tests that were actually run, records expected vs actual with evidence, re-verifies fixes, and ends with a sign-off page your client can accept feature by feature.

    View skill
    $5$3.80Save 24%

    See it in action

    Dataflow Handover — where your client's data actually goes

    Dataflow Handover — where your client's data actually goes

    Example session with this skill installed

    Make a data flow document for my client from this project: where does customer data go?

    • Read your context and instructions
    • Compiled the dataflow handover

    Bean & Kettle back office: Data flow

    Version 2026-11-09 · Source project code and database schema, 2026-11-09 · For the shop owner

    Fictional example. Every solid arrow is traced to the included code; dashed arrows are steps handled outside this project, as stated by the developer.

    Overview

    flowchart LR
        Customer([Customer])
        Owner([Owner])
        Staff([Staff])
        Store{{Online store platform}}
        Pay{{Payment provider}}
        subgraph System["Bean & Kettle back office (this project)"]
            BO[Back-office page]
            DB[(Shop database)]
            Report[Revenue calculation]
        end
        Customer -. "name, email, order" .-> Store
        Store -. "payment" .-> Pay
        Store -. "writes orders" .-> DB
        Owner --> BO
        Staff --> BO
        Owner --> Report
        DB --> Report
    

    In one sentence: orders and payments are handled by the online store platform; this project holds the shop database and the back office, which lets staff view orders and the owner refund orders and check revenue.

    Process 1: An order comes in

    #What happensDataStored inWho
    1Customer checks out in the online store🔒 name, email; products, quantitiesonline store platformcustomer
    2Payment is taken🔒 payment detailspayment provider (never in the shop database)payment provider
    3Store writes the order into the shop database🔒 name, email; order, linescustomers, orders, order_itemsonline store platform

    Watch out: order confirmation emails are not sent in this version; they are part of phase 2.

    Process 2: Owner refunds an order

    #What happensDataStored inWho
    1Owner opens an order and clicks Refund orderorder number, total—owner only
    2Owner confirms; the page shows status refunded and lowers that month's revenueorder statusthe open page onlyowner
    3Owner returns the money in the payment provider's dashboardamountpayment providerowner

    Watch out (important): the refunded status is

    not saved to the shop database in this version: it disappears when the page is reloaded. Saving refunds is scheduled before go-live. The back office does not contact the payment provider; the money is returned by hand in step 3.

    Process 3: Owner checks monthly revenue

    #What happensDataStored inWho
    1Revenue calculation reads paid and shipped orders, leaving out test accountsorders, customers' test flagread onlyowner only (staff refused)
    2Owner opens Revenue in the back officemonth, orders, revenuefigures built into the pageowner only

    Watch out: the revenue page shows figures written into the page itself; connecting it to the revenue calculation is scheduled before go-live.

    Process 4: Signing in

    Watch out (security): in this version the account list is readable by anyone who opens the page and any password is accepted. It is replaced by server sign-in before go-live.

    Where personal data lives and travels

    DataEnters atStored inLeaves toWho can see it
    🔒 Customer nameonline store platformcustomers.name—owner, staff
    🔒 Customer emailonline store platformcustomers.email—not shown in the back office
    🔒 Payment detailsonline store platformpayment provider onlypayment provider—
    Staff/owner emailsign-in pageinside the page code—anyone who opens the page (until server sign-in)

    This project's own code sends nothing outside the system: no web requests, email sending or payment calls.

    Recommended actions

    Current stateActionWhoWhen
    Refunds are shown on the page but not savedSave the refunded status to the shop databasedeveloperbefore go-live
    Revenue page shows figures built into the pageConnect the page to the revenue calculationdeveloperbefore go-live
    This version's sign-in accepts any passwordReplace with server sign-in and stored, hashed passwordsdeveloperbefore go-live
    Money is returned by hand in the payment providerRecord the provider's refund reference on the orderownerfrom go-live
    No order confirmation emailsAdd confirmation emailsdeveloperphase 2
    Revenue months follow UTC timeGroup revenue by the shop's local timedeveloperphase 2

    Delivered as dataflow.md plus a print-ready HTML (diagrams drawn); the developer appendix traces every step to file and function.

    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 these skills and uses them on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every skill in this bundle goes through our trust checks.

    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.

    Frequently asked questions

    Yes — every skill in Client Handover Kit — five documents for handing over a project is also sold on its own product page. The bundle just packages them together at a discount (save 24% vs buying each one separately).

    Yes. When you own the bundle your connected agent can load the latest version of any included skill. Updates the creator publishes after your purchase are included at no extra cost.

    All skills in this bundle use the open SKILL.md standard and work with Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot, Windsurf. The compatibility list on this page is computed from the included skills.

    The bundle price is set 24% below the combined retail price of the 5 paid skills included. You pay once and unlock every skill in your library instantly.

    Bundles are covered by the same money-back guarantee as individual skills. Doesn't do what its page promises? You get your money back.

    No, each works alone. The kit saves you $6 against buying them separately and gives every document the same look.

    Each document is written in the language you use (or ask for).

    Send me a message through Agensi from my creator profile. I read every note, and reported problems are fixed in the next update of the skill.