How to use Billionaire High Performance Coach with Claude for daily agenda trigger
The Daily Agenda Engine — daily agenda trigger in Claude is a named operating pattern in the Billionaire High Performance Coach system. It applies Daily Agenda Engine, which turns goals and constraints into a daily execution stack, to daily agenda trigger in Claude.
What this page recommends
The Daily Agenda Engine — daily agenda trigger in Claude is a named operating pattern in the Billionaire High Performance Coach system.
- Next step: Buy
Daily Agenda Engine — daily agenda trigger in Claude
Long documents can sit alongside the conversation, so the rules block can be a file rather than a paste.
Stored context is a convenience. Keep a plain-text copy so the setup survives a product change.
Do this first. Put the rules in a file that sits alongside the conversation, and give the file a version marker so a behavior change can be attributed to an edit.
Do not do this. Letting the file grow. A rules document too long to read in full stops being read, and then it stops being the source of truth.
Turn constraints and goals into a plan that fits the hours that exist. It runs on one trigger: the start of the working day, before anything else is opened.
When this framework is the right one. Use it at the start of a day where you know roughly what matters but the list has no order and no fit to the hours available.
- List fixed constraints first: meetings, travel, care obligations, anything already committed. These are not negotiable inputs.
- Subtract them from the waking hours to get the real number of workable hours, then subtract a further margin for transition and overrun.
- Fill the remaining hours with named outputs in priority order, stopping when the hours run out rather than when the list runs out.
- Everything below the cut goes to the deferred list, in writing, before the day starts.
Daily agenda trigger: purpose, trigger, output
| Element | What it is here |
|---|---|
| Purpose | Turn constraints and goals into a plan that fits the hours that exist. |
| Trigger | The start of the working day, before anything else is opened. |
| Output | A short ordered list allocated only against workable hours, plus an explicit deferred list. |
| Where it stops | Organizational support only. It is not clinical, legal, or financial advice. |
Where the daily agenda trigger goes wrong
| Element | What it is here |
|---|---|
| How it usually fails | It runs after the inbox is open, at which point the queue has already set the plan. |
| What to do in the first week | Run it before opening anything else, and write the workable-hours number first. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Running this in Claude: setup and state
| Element | What it is here |
|---|---|
| Seeding the rules | Keep the rules in a short document alongside the conversation, with a version marker at the top. |
| What carries between sessions | Documents persist and drift silently. Put the review date in the document itself. |
| What to verify with the provider | Stored context is a convenience. Keep a plain-text copy so the setup survives a product change. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Common misreadings: Claude
| Element | What it is here |
|---|---|
| What it is usually mistaken for | A place to store everything. Long context makes it easy to keep material that has expired. |
| The metric that misleads | How much you have attached, which is not the same as how much of it is current. |
| What to do in the first week | Read the attached rules document in full once. If you will not, it is too long to be governing anything. |
| Where this stops | Organizational support only. It is not clinical, legal, or financial advice. |
Worked example: the daily agenda trigger in Claude
The start of the working day, before anything else is opened. Turn constraints and goals into a plan that fits the hours that exist.
Long documents can sit alongside the conversation, so the rules block can be a file rather than a paste. Keep the rules file short enough to read in full, and version it so you can tell which version produced a session.
List fixed constraints first: meetings, travel, care obligations, anything already committed. These are not negotiable inputs.
What to measure. A short ordered list allocated only against workable hours, plus an explicit deferred list.
Running Daily Agenda Engine for the daily agenda trigger
Most daily plans fail on arithmetic rather than motivation: the list assumes more hours than the calendar contains. The engine takes fixed constraints first, subtracts them, and only then allocates the remainder, so the plan you leave with is one that fits the day you actually have.
The full set of failure modes for this framework, the evidence to record, and a prompt you can paste are on its framework page. This page covers the part specific to the daily agenda trigger.
What this is not. It is not a calendar tool and it does not schedule anything for you. It produces a plan that fits, which a calendar cannot check.
What it leaves behind: a short ordered list allocated only against workable hours, plus an explicit deferred list.
Frequently asked questions
Does this depend on Claude specifically?
No. Stored context is a convenience. Keep a plain-text copy so the setup survives a product change.
What does the daily agenda trigger produce?
A short ordered list allocated only against workable hours, plus an explicit deferred list.
What should a reader do in the first week on Claude?
Read the attached rules document in full once. If you will not, it is too long to be governing anything. A place to store everything. Long context makes it easy to keep material that has expired.
How does the daily agenda trigger usually fail?
It runs after the inbox is open, at which point the queue has already set the plan. Run it before opening anything else, and write the workable-hours number first.
Does this page diagnose, treat, or replace professional advice?
No. It is educational and organizational only. It does not diagnose or treat anything, and it is not a substitute for a clinician, a lawyer, or a financial professional. If the situation involves health, safety, legal exposure, or money at stake, that is the moment to use qualified human support.
Boundaries
Billionaire High Performance Coach is educational and organizational. It is not medical, psychological, legal, financial, therapeutic, or diagnostic advice, and it does not diagnose or treat anything.
If the situation involves safety, health, legal exposure, financial decisions, or crisis-level distress, use qualified professional support. A written framework is not a substitute for a clinician, a lawyer, or a financial professional.
Where this fits in the system
Checkout is handled through Gumroad for instant digital access after purchase.
Sources and review basis
This page was reviewed against the following sources on . Third-party products change their features, terms, and pricing, so verify current details with the provider.