Chapter 16 : Complete workflows

The building blocks show their full value when you chain them together. Here are eight end-to-end workflows, drawn from real work situations. You'll learn almost nothing new here, and that's on purpose: each workflow takes building blocks from the previous chapters and assembles them over a week that looks like yours. Find the one closest to your own, and start there.

Chapter 16 · 4 min read

Workflow 1Meetings: from meeting to action items

MeetingsSkillconnectors
  1. Launch "New meeting in this project" when the meeting starts. Jay records and transcribes.
  2. At the end, your /cr Skill pulls out decisions, action items, deadlines and open questions, and files the minutes in the folder.
  3. Jay prepares follow-up email drafts in your mailbox and adds the deadlines to your calendar, once you approve.
  4. The following week, "what did we decide about the deadline?" finds its answer in the transcript.

Workflow 2The monitoring brief that runs itself

Projectweb searchFlow
  1. Create a "Monitoring" project with its folder and the JAY.md from chapter 4: players, topics, sources.
  2. Run a first monitoring brief in Thinking mode and refine it until you like the format.
  3. Schedule it every Monday at 8 a.m., in Auto, with a notification.
  4. Every quarter, ask for a summary of the last twelve briefs in the folder: that's where the trends show up.

Workflow 3Preparing for a client meeting

ConnectorsPappersBrowserproject
  1. Jay reads your calendar and spots the meeting.
  2. It looks up the history of your exchanges in your email and the documents in the client's folder.
  3. It adds the company's Pappers record and a search on its latest news.
  4. It writes a brief in the Atelier: goals, questions, likely objections, opening line. With the "Ready for tomorrow" flow, it's waiting for you every evening.

Workflow 4From rough draft to LinkedIn post

Projectideation
  1. Dictate your idea as it comes, or paste it into the "My voice on LinkedIn" project.
  2. Ask for 3 angles and 5 hooks; pick one.
  3. Have Jay write it using your reference texts, then self-critique: "What would make someone stop reading?"
  4. You publish it yourself; the LinkedIn connector, once released, will post after your confirmation. The approved post is archived in the folder.

Workflow 5Competitive analysis

Web searchAtelier
  1. One in-depth search per competitor, in Thinking mode: offering, pricing, positioning, news. As a background task if you have five.
  2. A comparison spreadsheet on your criteria, with the source for every cell.
  3. An analysis: strengths, weaknesses, open spaces in the market.
  4. An 8-slide presentation for your team, in your brand kit, exported to PowerPoint.

Workflow 6Monthly reporting

Watched folderspreadsheetdocumentFlow
  1. The exports land in a watched folder, or Jay downloads them with a WebFlow.
  2. Jay calculates the metrics with code, in a spreadsheet with visible formulas, and compares them to the previous month.
  3. It writes the commentary in the format of your last report, with the anomalies up front.
  4. You check three numbers, adjust the commentary, and send it.

Workflow 7Processing documents in bulk

Background taskfolderspreadsheet
  1. Open the folder to Jay: invoices, contracts, resumes or forms.
  2. Give it the output template: a spreadsheet with the columns you want, plus a "to check" column.
  3. As a background task, Jay reads each document and fills in one row per file, flagging the doubtful cases.
  4. You only handle the flagged cases. From then on, the folder becomes a watched folder.

Workflow 8A code project, from requirement to pull request

Plan modeisolated copytestsForge
  1. /goal to turn the requirement into a specification, in a project session, switched to Code.
  2. Plan mode: Jay explores and proposes a plan; you approve it.
  3. Isolated copy: Jay codes on its own branch, writes the tests first, and makes them pass.
  4. You review the diff in the Code panel, /commit, then /pr writes the description and Jay opens the pull request on your forge, after confirmation.
PROMPTTurning a workflow into a system
Here's a task I do regularly: [describe the workflow step by step, with the tools and folders used].
Analyze it and propose: 1) the steps you can do on your own, 2) the ones that should stay human, 3) the best combination of project, JAY.md, Skill, connectors and Flow to set it up, 4) the permission level for each step, 5) the first step to take today.