The whole arc of an account beyond signup — settings, export, plan changes, and deletion — and whether the product treats users with dignity, even leaving.
Free & open · no signup · read-only — it ends by asking · nothing leaves your machine
You are working inside this repo. Mission: judge the account arc after signup — managing it, changing plans, exporting data, and leaving — and whether the product respects the user at every stage, including the exit. How a product handles leaving is how it earns being recommended.
Read-only pass. Trace the account, billing, and deletion flows; change nothing but the report file.
Phase 2 sweeps the codebase through every one of these, citing file and line for each finding.
can users find and change what governs their account; sane defaults
can a user get their data out, in a usable form, without support
upgrade, downgrade, cancel: clear, self-serve, no traps
a real delete path, what it removes, and honest handling of retained data
cancellation without hostage-taking; a graceful, respectful exit
coming back: is data preserved and return easy
dormant accounts, seat changes, ownership transfer, team departure
One structured report at the repo root — or in reports/, if you keep one — the same shape every time, ready for a teammate — or the optional Studio — to act on.
Every Goal Prompt follows the same four steps, so results are consistent and repeatable — no matter which one you run.
Map the stages.
Cite the flow or screen for every finding.
Rank by trust impact and legal exposure.
Create LIFECYCLE.md at repo root.
Copy it and paste it into your agent inside the repo you want checked.
Install the goal plugin once — two commands — then just type /goal:account-lifecycle.
/plugin marketplace add GhostlyGawd/goal-prompts/plugin install goal@goal-promptsOr install only this Goal Prompt as /goal-account-lifecycle:
curl -fsSL https://goal-prompts.vercel.app/install | BRIEF=108 shLet an agent fetch it mid-conversation, or pull the raw Goal Prompt by URL.
https://goal-prompts.vercel.app/raw/108.mdNothing hidden — this is the whole Goal Prompt, verbatim. Read it in a minute, edit it, or copy it as-is.
# Goal: Account Lifecycle Audit You are working inside this repo. Mission: judge the account arc after signup — managing it, changing plans, exporting data, and leaving — and whether the product respects the user at every stage, including the exit. How a product handles leaving is how it earns being recommended. Read-only pass. Trace the account, billing, and deletion flows; change nothing but the report file. ## Phase 1 — Walk the arc - Map the stages: settings, plan changes, data export, deletion, dormancy, and return. - For each, find the path a user takes and whether it is self-serve. - Note where a step requires contacting support that shouldn't. ## Phase 2 — Audit through 7 lenses Cite the flow or screen for every finding. 1. **Settings & control** — can users find and change what governs their account; sane defaults 2. **Data export** — can a user get their data out, in a usable form, without support 3. **Plan & billing changes** — upgrade, downgrade, cancel: clear, self-serve, no traps 4. **Account deletion** — a real delete path, what it removes, and honest handling of retained data 5. **Offboarding dignity** — cancellation without hostage-taking; a graceful, respectful exit 6. **Reactivation** — coming back: is data preserved and return easy 7. **Lifecycle edges** — dormant accounts, seat changes, ownership transfer, team departure ## Phase 3 — Curate - Rank by trust impact and legal exposure: no real deletion path outranks a clunky settings page. - Flag dark patterns — the deliberate friction on cancel or delete — for removal. - Separate "missing feature" from "hostile design"; name the hostile ones plainly. ## Phase 4 — Report Create `LIFECYCLE.md` at repo root: 1. **The arc, mapped** — each stage, its path, and whether it is self-serve 2. **Findings** — each: stage · location · what the user hits · the fix 3. **Dark patterns** — the deliberate friction to remove, called out 4. **Priority fixes** — ranked by trust and exposure, deletion and export first Start the report with today's date. If `LIFECYCLE.md` already exists from a previous run, read it first and lead with what changed since. ## Rules - A product with no self-serve delete or export is holding users hostage - Make leaving as easy as joining; that is what gets you recommended - No user accounts in this repo? Say so in a one-paragraph null report and stop — a null result is a valid finding. - If a `reports/` directory exists at the repo root, write the report there instead of the root. - Before asking, present the top findings as a ranked list in plain words - Report only — end by asking which lifecycle fixes to make first
reports/ directory exists at the repo root, write the report there instead of the root.The flagship. Understand the whole product, then surface prioritized opportunities across UI, UX, retention, engagement, community, and beauty.
How user signal re-enters the product — corrections captured or evaporating, thumbs nobody reads, and the complaint-to-fix path.
Every message the product sends out of the app — transactional email, push, in-app — for whether it is timely, wanted, clear, and controllable.
The product's own search — whether users can find what they are looking for: relevance, recall, forgiveness, and what happens on zero results.