Create a Cancer Care Family Brief

Use an AI skill to organize a restricted fictional cancer care family brief.

Introduction

30 Second Summary

Cancer care can leave a family juggling reports, unfamiliar terms, appointment dates, and questions across several places. That scatter makes the next useful question harder to see.

In this project, you will create a living brief for a fictional person named Alex. You'll use Antigravity CLI with Peter Yang's fuck-cancer Agent Skill before sharing the finished brief through Google Docs.

What You'll Build

Open Alex's brief before a mock appointment to see confirmed facts, pending results, next actions, medical terms, and the family's questions in one calm view.

By the end of this project, you'll have:

A family brief you can use to review confirmed facts, unresolved information, up to three next actions, plain-language terms, and no more than five appointment questions.
A bounded research shortlist with three to five trial candidates and no more than three second-opinion options, while leaving eligibility for the trial site or care team to confirm.
A restricted Google Doc that only named practice reviewers can open as the family's single shared copy.
Secret Mission: Apply a mock appointment update to the same brief while preserving its current plan and dated care-log history.

Are there any prerequisites?

You need a Mac, internet access, and a personal Google Account. The steps guide every software setup while the case stays entirely fictional.

Before We Start

This first checkpoint anchors the project in a real caregiving purpose before any tools or case material enter the workflow. A general purpose statement keeps the focus on who the brief supports while leaving private medical details out.

Set Up a Safer AI Workspace

You have already defined who a future family brief could support. Before an agent handles even fictional medical material, the workspace needs a working local tool with cautious controls.

In this step, you will install Google Antigravity CLI plus Python on your Mac. You will also choose conservative data settings before any case information enters the agent.

In this step, get ready to:

Install Google Antigravity CLI under a personal Google Account on the Free plan.
Set conservative permissions plus data-use preferences.
Install Python 3.15.2 with its macOS certificates.

Install and open Google Antigravity CLI

Google Antigravity CLI gives you a local terminal interface for working with an AI agent. Checking for it first covers Macs where the tool may already be installed.

Press Cmd+Space to open Spotlight.
Type Terminal into Spotlight.
Press Enter to open Terminal.

Check whether Antigravity CLI is already available by running this command:

agy --version

What does this command do?

The command asks Antigravity CLI to print its installed version. It also confirms that your shell can find the agy executable.

✔️ I see the required version

Antigravity CLI is ready if the output shows 1.5.0 or higher. You can continue below.

ⓧ I see an older version

Your installed release is older than 1.5.0. Run the official installer to update it.

Update Antigravity CLI by running this command:

curl -fsSL https://antigravity.google/cli/install.sh | bash

What does this command do?

The command downloads Google's official installation script over HTTPS. The pipe passes that script to bash for installation.

Press Cmd+N to open a fresh Terminal window.
Verify the updated installation by running this command:

agy --version

What should I see?

The command should print 1.5.0 or higher without an error. This confirms that the updated executable is available in the fresh shell.

Still seeing the older version?

The installer places the executable at ~/.local/bin/agy. Use the fresh Terminal window so your shell reloads its command path.

Check that the installer finished before you rerun the version command.

Help me update Antigravity CLI on my Mac.

ⓧ Command not found

Antigravity CLI is not installed yet. The official installer adds it to your Mac.

Install Antigravity CLI by running this command:

curl -fsSL https://antigravity.google/cli/install.sh | bash

What does this command do?

The command downloads Google's official installation script over HTTPS. The pipe passes that script to bash for installation.

Press Cmd+N to open a fresh Terminal window.
Verify the installation by running this command:

agy --version

What should I see?

The command should print 1.5.0 or higher without an error. This confirms that the new executable is available in the fresh shell.

Still unable to run agy?

Confirm that the installer completed before opening the fresh Terminal window. The default executable location is ~/.local/bin/agy.

Rerun the official installer if its first attempt stopped before completion.

Help me find my Antigravity CLI installation.

The first launch opens Antigravity's interactive terminal interface. It also begins the browser sign-in flow for a personal Google Account.

A personal account can use the Free plan. You will leave AI-credit overages disabled before entering any case information.

Start Antigravity CLI by running this command:

agy

What does this command do?

The agy command launches Antigravity's interactive terminal interface. The first launch guides you through authentication.

Choose personal Google Account authentication if Antigravity asks for an authentication method.
Complete the browser sign-in using your personal Google Account on the Free plan.
Return to Antigravity CLI after the browser confirms authentication.

Your agent is now available in Terminal under your personal account. That gives you the local workspace needed for the fictional exercise.

Choose conservative settings

Agent permissions determine when Antigravity pauses for your approval. Data-use settings control whether interactions may support product improvement.

Keep this practice fictional

Privacy settings can feel high stakes. This project keeps the boundary simple.

Google may record personal-account interactions to provide or protect the service. Its terms also allow improvement use according to your settings.

Turning telemetry off changes the improvement preference. Confidential records remain outside this workflow.

Use fictional information only throughout this project.

Open Antigravity's interactive settings panel by running:

/config

What does this command do?

The /config command opens the settings panel inside Antigravity CLI. This is where you control permissions plus account preferences.

Set the permission behavior to request-review.
Keep Use AI Credits turned off.
Select Account in the settings panel.
Turn Enable Telemetry off.
Press Esc to leave the settings panel.

That is the cautious baseline in place. Antigravity now requests review before sensitive tool actions while AI-credit overages plus telemetry remain off.

Can't find the settings?

Run the slash command from inside the Antigravity interactive interface. The /settings command opens the same settings panel if you need an alternative.

Look under Account for the telemetry preference.

Help me configure safer Antigravity settings.

Install Python for the trial-search helper

The skill's trial-search helper needs a Python runtime. This project uses Python 3.15.2 plus the certificate setup included with the official macOS installer.

Press Cmd+N in Terminal to open a second window.

Check whether Python 3.15.2 is already available by running:

python3.15 -VV

What does this command do?

The command invokes the installed Python 3.15 interpreter. The -VV option prints detailed version information.

✔️ I see the required version

Python is ready if the output includes 3.15.2. Continue to the certificate setup below.

ⓧ I see an older version

The trial-search environment for this project uses Python 3.15.2. Install that release from the official Python website.

Open the official Python macOS releases page in your browser.
Select Download macOS installer for Python 3.15.2.
Open the downloaded installer.
Complete the guided installation.
Press Cmd+N in Terminal to open a fresh window.
Verify the installed version by running:

python3.15 -VV

What should I see?

The detailed output should include Python 3.15.2. This confirms that the new interpreter is available.

Still seeing the older Python version?

Confirm that you selected the installer for Python 3.15.2. Use a fresh Terminal window after the installer finishes.

Help me verify Python 3.15.2 on my Mac.

ⓧ Command not found

Python 3.15.2 is not available yet. Install it from the official Python website.

Open the official Python macOS releases page in your browser.
Select Download macOS installer for Python 3.15.2.
Open the downloaded installer.
Complete the guided installation.
Press Cmd+N in Terminal to open a fresh window.
Verify the installation by running:

python3.15 -VV

What should I see?

The detailed output should include Python 3.15.2. This confirms that the interpreter is installed.

Still unable to run Python?

Confirm that the installer completed successfully. Use a fresh Terminal window before retrying the version command.

Help me find Python 3.15.2 on my Mac.

Finding the certificate helper is a little fiddly because it sits inside the installed Python application folder. Running it completes Python's SSL root-certificate setup.

Switch to Finder.
Press Shift-Command-G to open Go to Folder.
Enter /Applications/Python 3.15/ into the folder field.
Press Enter to open the folder.
Double-click Install Certificates.command.

A Terminal window runs the certificate setup. You should see output containing Successfully installed certifi plus update complete when it finishes.

Before you run the final checks, make a quick prediction about the version information each command will print.

Verify both installed runtimes by running these commands in Terminal:

agy --version
python3.15 -VV

What should I see?

The first command prints the installed Antigravity CLI version. The second command prints detailed Python version information.

Success means both commands return version information without an error. The output should show Antigravity CLI 1.5.0 or higher plus Python 3.15.2.

The safer workspace is ready. Antigravity is authenticated with conservative controls while Python can support the helper used later in the project.

One of the final checks failed?

Open a fresh Terminal window after either installer so the shell reloads its command path. Rerun only the version check that failed.

For Python certificate issues, rerun Install Certificates.command from /Applications/Python 3.15/.

Help me finish both version checks.

Your local tools plus privacy boundaries are in place. Next up, you will add the reusable skill and test what it can organize from a deliberately limited fictional account.

Install the Skill and Create a First Brief

Your safer Google Antigravity CLI workspace is ready for fictional practice material. The next goal is to add Peter Yang's fuck-cancer Agent Skill as a reusable organizer.

Family notes often mix known facts with unanswered questions. A local Markdown brief gives those categories one place while keeping missing evidence visible.

In this step, get ready to:

Install the fuck-cancer skill globally with each proposed action reviewed.
Confirm that Antigravity discovered the skill.
Create a fictional practice brief that preserves its information gaps.

Install the skill globally

A global skill remains available across Antigravity conversations. Your conservative permission setting lets you inspect the installation before any tool action runs.

Switch back to the Terminal window from earlier.
Start Antigravity by running this command:

agy

What does this command do?

The agy command starts the interactive Antigravity CLI session connected to your personal Google Account.

Paste the official global installation request exactly as shown:

Install the /fuck-cancer skill globally from https://github.com/petergyang/fuck-cancer

What does this request do?

This asks Antigravity to retrieve Peter Yang's repository. It also asks Antigravity to make the skill available globally.

Your request-review setting keeps each proposed tool action visible before it runs.

Review every proposed tool action before it runs.
Approve an action only when it directly supports the global skill installation.

✔️ Antigravity installs the skill

Antigravity has completed the global installation. Keep this session active for the discovery check below.

ⓧ Antigravity cannot install it

The manual route uses GitHub to download the complete skill folder. It places that folder in Antigravity's documented global skills location.

Ask Antigravity to create ~/.gemini/config/skills/ if that folder does not exist.
Review the proposed folder-creation action.
Approve the action only when its destination is ~/.gemini/config/skills/.
Stop the installation attempt after the destination folder exists.

The global destination is ready. The repository archive contains the complete skill folder.

Open Peter Yang's fuck-cancer repository in your browser.
Click Code above the repository files.
Click Download ZIP.
Locate the downloaded ZIP archive in Finder.
Double-click the ZIP archive to extract it.

Keep the skill folder complete

The SKILL.md file defines the skill for Antigravity. Copying the complete folder preserves that definition.

The scripts folder contains the bundled helper used later in the project. Keep it inside the skill folder.

Press Shift-Command-G in Finder to open Go to Folder.
Enter ~/.gemini/config/skills/ in the folder field.
Press Enter.
Open the extracted repository folder in Finder.
Open its skills folder.
Drag the complete fuck-cancer folder into the ~/.gemini/config/skills/ Finder window.
Open the copied fuck-cancer folder.
Confirm that its scripts folder is still present.

Can't find the copied skill folder?

Check that the final path is ~/.gemini/config/skills/fuck-cancer. Make sure you copied the inner skill folder from skills/fuck-cancer.

The copied folder must contain SKILL.md plus the scripts folder.

Help me check my global Antigravity skill folder.

Reload the skills list

A running Antigravity session needs to refresh before it can discover a skill added during that session. The skill list gives you a visible confirmation that discovery worked.

Refresh Antigravity's discovered skills by entering this command:

/skills reload

What does this command do?

The /skills reload command refreshes the skills Antigravity can load without requiring another installation.

Display the loaded skills by entering this command:

/skills

What does this command do?

The /skills command opens the skill-management surface so you can inspect the loaded skill names.

Find fuck-cancer in the loaded skills list.

Good progress. Seeing fuck-cancer here proves that Antigravity discovered the global skill.

Skill missing from the list?

Start a fresh Antigravity conversation if the current list did not refresh. Run the skill list command again after the new conversation starts.

For a manual installation, confirm that SKILL.md sits directly inside ~/.gemini/config/skills/fuck-cancer.

Help me find why Antigravity cannot discover the skill.

Create the first fictional brief

The first run gives the skill one biopsy fact plus one appointment date. This creates a fair test of how the brief handles missing evidence.

Before you send this, make a quick prediction about whether the brief will fill the missing details or leave them unresolved.

Send the fictional practice request by pasting this exact prompt:

/fuck-cancer My fictional family member Alex has been told that a colon biopsy found cancer. We have an oncology appointment on November 12, 2026, but we do not yet understand the scan or pending tests. Create a local Markdown brief for this practice case. Do not include real personal information.

What does this request do?

The request gives the skill two known details. It also asks for a local practice brief that contains fictional information only.

The missing scan interpretation plus test results remain evidence gaps. The skill must keep those gaps visible instead of inventing answers.

Review the proposed local file action before it runs.
Approve the action only when it creates the fictional Markdown brief.

Keep the current brief under one filename by sending this follow-up:

Rename the current local brief to Alex's Brief.md. Keep one brief only.

Why keep one file?

This keeps the exercise anchored to one source of truth. Renaming the current file avoids creating a second tracker.

Read the saved Alex's Brief.md in Antigravity's response.
Confirm that the colon biopsy finding appears as known information.
Confirm that the oncology appointment is dated November 12, 2026.
Locate the unresolved label for the scan meaning.
Locate the unresolved label for the stage.
Locate the unresolved label for the pending tests.
Confirm that no real personal information appears in the brief.

What should I see?

You should see the colon biopsy finding recorded as known. You should also see the oncology appointment dated November 12, 2026.

The scan meaning should remain unresolved. The stage should remain unresolved.

The pending tests should also remain unresolved. No real personal information should appear.

That visible uncertainty is the intended result. The first brief organizes what the family knows without pretending that a brain dump can replace clinical evidence.

Brief filled in missing details?

Do not accept an invented stage or scan interpretation. Return to the exact fictional prompt above so Antigravity can regenerate the brief from only the supplied facts.

Help me remove unsupported claims from the fictional brief.

Your global skill is working with one fictional local brief. Next, you'll add a fictional report so the family can replace vague gaps with better questions while preserving uncertainty.

Turn the Report Into Questions

Your first fictional brief exposed the limits of the original brain dump. It kept scan meaning, stage, and pending tests visibly unresolved.

The fictional report gives the fuck-cancer Agent Skill enough evidence to sharpen the living brief. Your job is to preserve every remaining uncertainty. Those gaps become useful appointment questions.

In this step, get ready to:

Add report-based facts to the fictional brief.
Separate confirmed findings from suspicious findings and pending tests.
Turn the remaining gaps into an appointment question list in a temporary local note.

Add the fictional report

A pathology result can confirm one fact while imaging still raises an unconfirmed possibility. The brief needs both evidence levels without turning suspicion into a stage claim.

Return to the Google Antigravity CLI conversation from earlier.
Update Alex's Brief.md by pasting this fictional report prompt:

/fuck-cancer Update Alex's brief from this fictional report. Pathology: colon adenocarcinoma. CT: liver lesions described as suspicious for metastases; the oncology team has not confirmed the stage. Mismatch repair proteins are intact. RAS and BRAF results are pending. The oncology appointment is November 12, 2026.

What does this prompt protect?

The report confirms colon adenocarcinoma and intact mismatch repair proteins.
The CT wording remains suspicious because the oncology team has not confirmed the stage.
RAS and BRAF stay Pending until their results are available.

Review every proposed edit before approving it.
Approve the edit only when it updates the existing Alex's Brief.md file.

You'll see colon adenocarcinoma and intact mismatch repair proteins among the confirmed facts. The liver lesions stay suspicious while RAS and BRAF appear as Pending.

Report facts missing from the brief?

Check that the prompt begins with /fuck-cancer.
Confirm that you approved the edit to the existing Alex's Brief.md file.

Help me check why the fictional report did not update Alex's existing brief.

Keep certainty labels intact

Plain-language explanations can accidentally flatten different evidence levels. Clear labels preserve the boundary between a confirmed result and a possibility that still needs clinical review.

Refine the current brief by pasting this follow-up prompt:

Explain the report terms in plain language. Keep suspicious findings separate from confirmed findings, label tests already in progress as Pending, and do not choose treatment or estimate prognosis.

What does this follow-up change?

Plain language makes the report terms easier for the fictional family to discuss.
The status instructions keep suspicious findings separate from confirmed findings.
The clinical boundaries leave treatment and prognosis decisions with the care team.

Confirm that the suspicious liver findings remain separate from confirmed facts.
Confirm that RAS and BRAF are labeled Pending.
Confirm that no treatment choice appears.
Confirm that no prognosis estimate appears.
Approve the proposed update to Alex's Brief.md.

You'll see explanations for the report terms alongside their evidence status. The brief retains no more than three next actions.

Certainty labels getting blurred?

Compare the suspicious liver finding with the confirmed pathology section.
Check that tests already in progress use the exact label Pending.
Reject any proposed edit that turns the liver finding into a confirmed stage.

Help me review the fictional brief for diagnosis creep or blurred certainty labels.

Build the appointment question list

Uncertainty becomes useful when it leads to focused questions for the care team. A short first-person list gives the family a practical way to discuss recommendations and tradeoffs.

Generate the appointment questions by pasting this prompt:

Prepare up to five short, respectful first-person questions for the November 12 appointment. Focus on the clinician's recommendation, reasoning, choices, tradeoffs, timing, and quality of life.

Why limit the question list?

The five-question limit keeps the list usable during an appointment.
First-person wording makes each question ready to read aloud.
The requested topics keep the conversation focused on the care team's reasoning and the family's priorities.

Review the generated list for no more than five questions.
Confirm that every question uses respectful first-person language.
Confirm that the list focuses on recommendation, reasoning, choices, tradeoffs, timing, or quality of life.
Select the final question list in Antigravity CLI.
Copy the selected list by pressing Cmd+C (macOS) or Ctrl+C (Windows).
Create a temporary note in your Mac's local notes app.
Paste the copied list by pressing Cmd+V (macOS) or Ctrl+V (Windows).

That's the appointment preparation secured. The fictional family now has a short question list it can rehearse without creating another version of the brief.

Questions too broad or too definite?

Check that the list contains no more than five questions.
Remove any wording that assumes a treatment choice or confirmed stage.
Keep each question focused on one topic.

Help me tighten the fictional appointment questions without asking for treatment advice.

Before you ask for the final brief, which details do you expect to remain unresolved?

Show the updated living brief by pasting this prompt:

Show the updated brief.

What does this final check prove?

This displays the current brief after both updates. It lets you check the evidence labels, action limit, and appointment questions in one place.

You'll see pathology and mismatch repair status under confirmed facts. The liver lesions remain suspicious while the stage remains unconfirmed.

RAS and BRAF appear as Pending. The brief contains plain-language explanations plus no more than three next actions.

The appointment section contains up to five respectful first-person questions. No treatment choice, prognosis estimate, or stage claim appears.

Final brief missing a requirement?

Check that you approved both updates to the same Alex's Brief.md file.
Compare the displayed brief with the report details in the first prompt.
Confirm that the temporary note contains the same final question list.

Help me compare the updated fictional brief with the required facts and boundaries.

Your living brief now turns report evidence into a focused appointment plan. Next, you'll examine possible trials and second opinions without claiming eligibility.

Research Trials and Second Opinions

Your local fictional brief now separates confirmed findings from suspicious findings. It also marks the RAS result plus the BRAF result as Pending.

Now you'll use the installed Agent Skill to research possible trials near Toronto. You'll also gather a short set of second-opinion options.

Detailed search results can look authoritative even when key eligibility details remain unknown. This step keeps every result conditional until the trial site or care team confirms it.

In this step, get ready to:

Run a bounded search for trial candidates near Toronto.
Check each trial lead for decision-relevant evidence.
Produce a shortlist within the project limits.

Run a bounded research request

The bundled Python helper queries the official ClinicalTrials.gov API. It requires no API key.

Clinical trial searches must exclude names plus care identifiers. This practice request relies only on the fictional brief.

Return to the Antigravity CLI conversation from earlier.

Before you run the request, do you think a detailed trial result can confirm eligibility on its own?

Submit the bounded research request by pasting this prompt:

/fuck-cancer Find relevant trials near Toronto for this diagnosis, and no more than three second-opinion options. Use the fictional brief, label unknown eligibility, and do not contact anyone.

What Does This Request Control?

The location keeps the trial search centered near Toronto.
The explicit cap prevents the second-opinion results from becoming an unmanageable directory.
The unknown-eligibility instruction keeps every trial result conditional.
The final sentence blocks outreach to any organization.

Inspect the proposed helper action when Antigravity asks for approval.
Approve the bundled Python helper for this fictional request.

You should see possible trial candidates based on the fictional diagnosis. Any specific-looking NCT number remains a research lead that needs confirmation.

Research Helper Did Not Run?

Confirm that the installed ~/.gemini/config/skills/fuck-cancer folder still contains its scripts folder.
Review the proposed action again if Antigravity paused for permission under request-review.

If the helper still cannot run, help me check the installed skill folder and the proposed Python action.

Inspect the evidence boundaries

A linked study record makes a trial lead easier to investigate. Eligibility remains unresolved until the trial site or care team reviews the full criteria.

Review each trial candidate's linked NCT number.
Confirm each candidate names the intervention.
Confirm each candidate states the phase.
Confirm each candidate identifies the nearest open site.
Confirm each candidate gives a possible fit rationale.
Confirm each candidate states an unresolved eligibility question.
Reject any sentence that says Alex qualifies.
Reject any sentence that presents a treatment as the answer.

That's the crucial distinction secured. Every retained candidate is now a lead for confirmation instead of a treatment conclusion.

Evidence Field Missing?

Ask the skill to complete the missing field from the linked study record.
Remove the candidate if the missing detail cannot be supported.

For help assessing a result, help me identify which evidence fields are missing from this fictional trial candidate.

Keep only decision-relevant results

A living brief should hold only results that support the family's next conversation. A search result earns space when it changes what the family should ask next.

Ask the skill to keep the strongest three to five trial candidates.

You should see lower-priority candidates disappear from the proposed shortlist.

Ask the skill to keep no more than three second-opinion options.

The second-opinion section should now contain a focused set of options.

Ask the skill to add a current action only when a result changes what the family should ask next.

The proposed brief should preserve the existing action limit. Research that does not affect the next conversation stays out of What to do next.

Review the proposed change to Alex's Brief.md.
Confirm the CT liver lesions remain suspicious.
Confirm the stage remains unconfirmed.
Confirm the RAS result remains Pending.
Confirm the BRAF result remains Pending.
Approve the proposed brief edit.

Before you inspect the saved brief, do you expect any result to read as confirmed eligibility?

Return to Alex's Brief.md from earlier.
Count the retained Toronto-area trial candidates.
Count the retained second-opinion options.
Check every trial candidate for a linked NCT number.
Check every trial candidate for an intervention.
Check every trial candidate for a phase.
Check every trial candidate for the nearest open site.
Check every trial candidate for a possible fit rationale.

What Should I See?

The trial section contains three to five Toronto-area candidates.
Every candidate includes an unresolved eligibility question.
Every confirmation requirement names the trial site or care team.
The second-opinion section contains no more than three options.
The brief never states that Alex qualifies.
The brief preserves the confirmed findings.
The brief preserves the suspicious findings.
The brief preserves the Pending results.
No organization has been contacted.

Shortlist Outside the Limits?

Ask the skill to remove lower-priority trials until only three to five remain.
Ask the skill to remove lower-priority second-opinion options until no more than three remain.
Restore any suspicious finding that was presented as confirmed.

If the brief still overstates the evidence, help me revise the fictional shortlist without claiming eligibility.

You've turned broad search results into a bounded set of questions for professional confirmation. Next, you'll move the living brief into a restricted Google Doc for the fictional family review.

Share One Restricted Brief

Your local brief now separates confirmed facts from suspicious findings. It labels Pending results clearly.

Next, you will place that brief in one restricted document in Google Docs. A single shared copy prevents practice reviewers from working from competing versions.

Sharing creates a privacy decision about who can open the document. You will limit access before rehearsing one update routine.

In this step, get ready to:

Create one Google Doc from the local fictional brief.
Restrict access to named practice reviewers with deliberately chosen roles.
Rehearse a single-document review routine.

Create the shareable Google Doc

A shared brief works when its structure survives the move from local Markdown to the browser. Manual transfer lets you check each section before anyone else sees it.

Open Google Drive in your browser with the same personal Google Account.
Select My Drive.

You should see the files stored in your personal My Drive.

Create a new Google Doc.
Rename the document Alex's Brief.

You should see Alex's Brief at the top of the document. The title contains no diagnosis or alarming language.

Open the existing local Alex's Brief.md file from its saved location on your Mac.
Copy the full fictional brief.
Paste the copied brief into Alex's Brief.
Arrange the pasted content under these five headings: Patient information, What to do next, What we know, Medical terms, and Care log.

You should see all five sections in one document. The confirmed facts remain separate from suspicious findings and Pending results.

Select the next actions under What to do next.
Apply the native numbered-list format from the Google Docs toolbar.

You should see no more than three next actions in one numbered list.

Select the appointment questions in the brief.
Apply the native numbered-list format from the Google Docs toolbar.

You should see up to five appointment questions in a numbered list. The caveated trial candidates and second-opinion options should remain in the same document.

Why Transfer the Brief Manually?

Automatic document creation from a free local Antigravity session lacks a reliable documented path for this workflow. Manual transfer gives you a clear review point before sharing.

The local Alex's Brief.md file remains available as your practice source.

Restrict access before sharing

Access settings deserve a careful check because they determine who can read the brief. This fictional case gives you a safe place to practise that decision.

Click Share in the top-right corner of Google Docs.
Select Restricted under General access.

You should now see Restricted under General access. Only people with access can open the document.

Enter the email address of each named practice reviewer.
Choose Viewer, Commenter, or Editor for each reviewer based on the access that person needs.

The access list should now show only the people reviewing this fictional exercise. Each person should have an intentional role beside their name.

Use the Smallest Role

Give each reviewer only the access needed for the rehearsal. Reserve Editor for someone who genuinely needs to change the brief.

Open Settings in the Share dialog.
Turn off Editors can change permissions and share when reviewers do not need to reshare the document.

The resharing control should now appear off. This keeps access decisions with the document owner.

Return to the Share dialog.
Click Send to apply the reviewer access.

You should see Restricted under General access. The access list should contain only the named practice reviewers with their selected roles.

Does the Access List Look Wrong?

Check that the document is in My Drive under the same personal Google Account used for this exercise.

For an unintended reviewer, choose Remove access from that person's access menu. Click Save.

Help me correct restricted sharing in Google Docs.

Rehearse the family review

A living brief needs a shared reading routine as much as restricted access. The rehearsal reveals whether each reviewer can find the information they need without starting another tracker.

Ask one practice reviewer to read the confirmed items under What we know aloud.
Ask another practice reviewer to read every Pending item aloud.
Ask another practice reviewer to read the appointment questions aloud.
Choose one person to take notes after appointments.
Assign that same person to update this single document.

Each reviewer should be able to locate their section in the same document. One designated updater keeps future changes in one place.

Before your final check, do you expect the Share dialog to show open access or only the reviewers you named?

Reopen the Share dialog.
Confirm that General access shows Restricted.
Confirm that the access list contains only the named practice reviewers.
Confirm that each reviewer has the intended role.
Confirm that Editors can change permissions and share is off when that restriction is needed.

You should see Restricted under General access. Only the named practice reviewers should appear in the access list with their intended roles.

You handled the sensitive access check carefully. The practice reviewers now have one restricted brief with one designated updater.

Secret mission

Update the Brief After a Mock Appointment

A living brief stays useful when the current plan reflects the latest appointment while the care log preserves what happened. In this challenge, you will review a fictional update before applying it to the same restricted family brief.

Clean Up Your Resources

Keeping these fictional resources stays at $0 within Antigravity's Free-plan quota, although Alex's Brief counts against your existing Google Account storage allowance. Decide whether to keep the resources, pause your CLI session, or delete the fictional artifacts.

Resources you used:

Global Agent Skill folder at ~/.gemini/config/skills/fuck-cancer, including its scripts folder.
Local fictional Markdown brief named Alex's Brief.md.
Temporary local note containing the fictional appointment questions.
Restricted file in Google Docs named Alex's Brief, plus its named practice-reviewer access.
Antigravity interaction history containing the fictional exercise.

Keep everything running

No action needed. Choose this if you want to reuse the fictional workflow or keep practising updates.

Retain the global fuck-cancer skill folder.
Retain Alex's Brief.md as a fictional template.
Retain the temporary appointment-question note for future practice.
In Alex's Brief, open Share to confirm that only the named practice reviewers still have access.
Keep General access set to Restricted.
Review each person's Viewer, Commenter, or Editor role periodically.
Retain the fictional Antigravity conversation only if you want its practice history.

Pause - I'll come back to this later

Pausing closes the Antigravity session while preserving the fictional workflow for later. The restricted document remains available to its named reviewers.

Exit Antigravity CLI by entering /exit.
Leave ~/.gemini/config/skills/fuck-cancer in place.
Leave Alex's Brief.md on your Mac.
Leave the temporary appointment-question note in its current app.
In Alex's Brief, open Share to confirm that General access still shows Restricted.
Keep each named reviewer's intended role unchanged.

Delete - I don't want to use this again

This cleanup removes only the fictional practice artifacts. Your general tool installations remain available.

Return to Alex's Brief in Google Docs.
Click Share.
Open each named reviewer's access menu.
Choose Remove access for each reviewer.
Click Save.
In My Drive, move Alex's Brief to the bin.
Permanently delete Alex's Brief from the Google Drive bin.

You've closed the shared-copy loop. The fictional document is no longer available to its former reviewers.

Locate Alex's Brief.md with Finder search.
Move Alex's Brief.md to Trash.
Return to the temporary appointment-question note from earlier.
Delete the note in the app where you saved it.
In Finder, click Go in the menu bar.
Select Go to Folder.
Enter ~/.gemini/config/skills/.
Move the fuck-cancer folder to Trash.

You've now cleared the local practice files from your Mac.

Request deletion of the fictional Antigravity interaction by emailing antigravity-support@google.com.
Identify only the fictional practice conversation in the request.
Exclude all real medical details from the request.
Empty the Mac's Trash to make the local file deletions permanent.

The local artifacts are now gone. Your Antigravity interaction has a documented deletion request.

Protect Real Patient Information

Confirm the patient's permission before using real records.
Review the chosen account's privacy fit.
Review the account's data-use settings.
Review the account's retention terms.

Nice Work!

You made it. You built a privacy-conscious workflow that keeps a fictional family's cancer information in one current living brief.

You've learned how to:

Configured Google Antigravity CLI with request-review permissions for a fictional practice case. Installed Peter Yang's fuck-cancer Agent Skill globally. Used /fuck-cancer to keep confirmed facts separate from suspicious findings. Marked unresolved results as pending.
Explained report terms in plain language. Prepared respectful appointment questions. Used the bundled Python helper to shortlist caveated trial candidates with linked NCT numbers. Left eligibility decisions with the care team.
Shared the brief through Google Docs. Set General access to Restricted. Limited access to named practice reviewers with deliberate roles. Kept the family on one source of truth.
Secret Mission: Updated the current plan after a mock appointment. Recorded the MRI order plus the November 19 follow-up. Preserved the November 12 entry in the dated care log. Kept the liver findings unconfirmed. Continued using the same tracker.

Ready to quiz yourself?