Get deliverables in Google Drive

What you'll get

Deliverables as real files rather than text in a chat window: a financial model as a spreadsheet you can hand an investor, a strategy document formatted for a board, a content calendar your team can open without ever meeting Marg. Chat is where the work gets done. Drive is where the work that has to outlive the conversation goes to live.

The steps

1. Connect Drive once (chapter 24 covers connections). Everything below assumes it is live.

2. Ask for the deliverable in its natural format. You rarely need a special command, because the workflow notices on its own when output has earned a real document:

/marg:route build our hiring plan for the next two quarters as a spreadsheet

When a specialist produces something document-shaped, a model, a tracker, a formal report, it flags the format, the document generator renders the actual file, and the file lands in Drive. What returns to your chat is the link.

3. Manage Drive files directly when you want to. Three skills cover the full file lifecycle without you leaving the conversation:

create a doc in Drive called "Q3 pricing decision" with the analysis above

append the new churn numbers to the Q3 pricing doc

move the old pricing draft to trash

Create, edit, and delete each run through the connection, so none of them sends you to a browser tab.

What comes back

One Drive link per deliverable, each pointing at a real file in your own folder structure. Spreadsheets arrive as spreadsheets with working columns, documents arrive properly formatted, and both are yours to share onward under normal Drive permissions. The file belongs to your Drive rather than to Marg, which means access control stays exactly where your company already manages it, with nothing new to govern.

Variations

• Board-grade rendering: when a document needs real polish, pagination, charts, a cover structure, the specialized team's document generator does the heavy formatting (chapter 16). Ask for "a board-ready PDF" and your request takes that path automatically.
• Local files instead: if you would rather have the output in your project folder than in Drive, say so. Blueprint deliverables, for one, land locally by default (chapter 19).

If something goes wrong

• "Drive is not connected": see chapter 24, then retry. The skills check the connection before they attempt anything, so you get a clear message instead of a half-created file.
• The file landed in the wrong folder: tell Marg where it belongs and it moves it, or name the destination folder in the original request to skip the shuffle entirely.
• An edit touched the wrong document: edits name their target before applying, and Drive's own version history covers whatever slips through. Open the file's history to restore any earlier state.