# Ajay Prakash Playbook

> Ajay Prakash's operator playbook, distilled from his public newsletter (Ajay's Quest / Lab Notes), ajayslist.com and his LinkedIn posts. Its core is his async comms framework: flagposting plus the six labelled update types (FYI, Approval, Decision, Action, CTL, Feedback) and the what / why / so-what frame. It also covers his methods for meetings, hiring and managing teams, growth and copywriting, ideas and strategy docs, and building with AI agents. Use it whenever someone wants to write or rewrite a Slack, Teams or email update, a weekly or 1:1 update to a manager, a decision request, a status report, a complaint, or a meeting agenda, even if they never mention Ajay. Also use it when they ask how to cut meetings, write a strategy doc, hire, scale or manage a team, diagnose a conversion or growth problem, write landing page or ad copy, or set up an AI agent team, or when they mention "flagposting", "CTL", "closing the loop", "Ajay's Quest", "Ajay API" or Ajay Prakash.

- Skill: `thatsheaps/ajay-prakash-playbook` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx get-skill add thatsheaps/ajay-prakash-playbook`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thatsheaps/ajay-prakash-playbook/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: thatsheaps (https://skillmd.com/u/thatsheaps)
- Updated: 2026-11-19
- Page: https://skillmd.com/skills/thatsheaps/ajay-prakash-playbook

---


# Ajay Prakash's playbook (unofficial)

**Credit.** Every method here is Ajay Prakash's. He has written about them since 2021 in his newsletter
[Ajay's Quest](https://www.ajays.quest/), now [Lab Notes from AJI Labs](https://writing.ajilabs.org/),
and on [ajayslist.com](https://www.ajayslist.com/) and [LinkedIn](https://www.linkedin.com/in/ajayvprakash/).
Read the originals, they are better than any summary. Subscribe at [writing.ajilabs.org](https://writing.ajilabs.org/).

**Not official.** [That's Heaps](https://thatsheaps.com) built this distillation from Ajay's public writing. Ajay did not write it,
review it or endorse it. All mistakes are ours. If you want Ajay's own judgment, he sells an AI
version of himself: [Rent an Ajay](https://www.ajilabs.org/drops/rent-an-ajay).

The frameworks below are paraphrased. Each one links to the issue it came from, and quotes are short and attributed.

## How to use this skill

1. Work out what the person is doing and load the reference file that matches. Load only that one.
2. Apply the method to their real material. Rewrite their actual message or plan; do not just explain the theory.
3. Name the method you used and link its source issue, so they can read the original.

| If the task is about... | Read |
|---|---|
| A Slack/email update, decision request, complaint, meeting, intro request, strategy doc | the comms framework below, then `references/comms-and-meetings.md` |
| Hiring, managing, autonomy, culture, burnout, letting someone go, team design | `references/teams-and-leadership.md` |
| Growth, conversion, landing pages, copy, one-liners, virality, brand vs performance, B2B | `references/growth-and-copy.md` |
| Picking ideas, taste, design, goals, information diet, selling a company | `references/ideas-taste-strategy.md` |
| Building with AI, agent teams, instruction files, Claude Code, prototyping | `references/building-with-ai.md` |
| Beliefs he repeats across ten years of LinkedIn posts | `references/linkedin-themes.md` |

## The core: async comms

Source: [The Secret Art of Async Comms](https://writing.ajilabs.org/p/the-secret-art-of-async-comms) (2025-08-05)
and [Interfacing with Ajay API](https://writing.ajilabs.org/p/interfacing-with-ajay-api) (2025-01-21).

His point: most slowness in a team is unclear messages, not missing meetings. A message the reader has to
read twice, or reply to with "what do you mean?", is a meeting postponed. In his words, "A fast message that creates confusion is not a fast message."

### 1. Flagpost the message

Format it so it scans in seconds.

- Start with a label that says what kind of message it is (see the six types).
- Keep context in its own short block. Put facts or changes in bullets.
- Pull every question out of the prose into its own list, so each can be answered on its own.
- Bold the few words that carry the meaning, not whole sentences.
- Spend the extra 20 to 30 seconds formatting. It saves the back-and-forth.

### 2. Label every chunk with one of six update types

| Label | Means | Must contain |
|---|---|---|
| **FYI** | No action needed | What happened. For an event, use what / why / so what |
| **Approval** | "I plan to do X, do you approve?" | The thing, the cost or risk, a yes/no ask |
| **Decision** | "I need you to choose" | Options, whether you're open to another answer, and **your recommendation** |
| **Action** | "Please do this" | The task, the owner, the date |
| **CTL** (closing the loop) | "Here's how that thing went" | What you discussed or the intro they made, and the outcome |
| **Feedback** | "My view on one specific thing" | Specific, actionable and timely; good or bad |

**What / why / so what.** For any event, good or bad, say what happened, why it happened, and so what:
what you're doing about it and what you need from the reader, if anything.

Two rules people skip:
- **A Decision without a recommendation hands the thinking back to the reader.** Always say what you'd do. He says most
  managers reply with some version of "go with your call".
- **CTL is the one people forget, and it builds the most trust.** When someone gave you an intro, advice or a
  decision, tell them how it played out.

### 3. Send one labelled message, not many

For a regular update (a weekly 1:1, a status post), send one message with a title line and one bullet per
item, each starting with its bold label. His own example runs FYI, FYI, Approval, Decision (Option A,
Option B, "My rec"), Action, CTL, Feedback.

### Worked example (ours, fictional)

Before:

> hey so the pricing page test is kind of mixed, CVR went up a bit on mobile but desktop dropped, not sure if we should keep going or roll back, also legal still hasn't come back on the new copy and I think we need someone to chase them? oh and the agency intro you made was great btw

After:

> **Weekly update, 5 Nov**
> - **FYI - Pricing test:** Mobile conversion up 0.4 pts, desktop down 0.3 pts after 9 days. Likely cause: the new comparison table pushes the CTA below the fold on desktop.
> - **Decision - Keep or roll back the test?**
>   - Option A: Roll back everywhere.
>   - Option B: Keep it on mobile, roll back on desktop, fix the fold and retest.
>   - **My rec:** B. It keeps the mobile gain and costs one day of design.
> - **Action:** Can you nudge legal on the new copy? It has been waiting 6 days and blocks launch.
> - **CTL - The agency intro:** Great call. They're sending a proposal Friday.

### 4. Make requests easy to answer (the "Ajay API")

He wrote colleagues a doc styled as API documentation: each kind of request is an "endpoint" with required
inputs. Use it to check a request before you send it:

- **Asking for feedback:** what you want feedback on, the actual material, the focus area, when you need it.
- **Asking for an intro:** a short email they can forward, why it's worth it for both sides, and always double opt-in.
- **Asking for a meeting:** the type (decision, brainstorm, realignment, education) and an agenda. Education defaults to a recorded video.
- **Asking for a decision:** the context, whether it is reversible, the options and your recommendation. If it is reversible and the area is yours, decide it yourself.
- **Assigning a task:** the name, objective, constraints and deadline, sent in writing.
- **Giving feedback:** the specific point, no compliment sandwich.

Full detail, plus his rules on when a meeting should exist: `references/comms-and-meetings.md`.

## Applying it well

- If a Decision has no recommendation in the user's draft, don't invent one. Ask them, or leave a clear `My rec: [A or B, and why]` slot and tell them to fill it before sending.
- When items depend on each other (an Approval that only matters if Option A wins), say so on the item, for example "(only if we pick A)".
- Report problems as facts and fixes, not blame. "The ads under-spent because targeting was set up wrong; now fixed" lands better with a manager than naming who messed up.
- Fit the label set to the channel. In a quick DM, one label and two lines is enough. Never pad a message to fit the template.
- Don't use the frameworks rigidly. Ajay warns against treating frameworks as law in
  [The Framework Cargo Cult](https://writing.ajilabs.org/p/the-framework-cargo-cult).
- When you quote Ajay, quote briefly and link the issue. Don't paste his newsletters.
- Don't put words in his mouth. If none of his writing covers the question, say so and give your own view, labelled as yours.

