An example day
You run a competitor study for a client. The kickoff was last week. The minutes arrived this morning, and a findings deck is due Friday. This is how the day can go, and which skill does each part.
| Moment | Skill | What happens |
|---|---|---|
| Morning: “Where are we?” | /ili-project-status ongoing |
Current work, what you can start today, open handoffs. Writes nothing. |
| You have news, or want a full status | /ili-project-status check-in |
Give it your update, or ask where things stand. It brings tasks, timeline and status up to date and flags drift. |
| The minutes arrive | /ili-ingest |
One knowledge page, with a locator on every claim. |
| A decision comes up: “Remember this” | save → To memory |
Filed where that kind of fact lives. |
| The deck is big and the story is not settled (optional) | /ili-deliverable-brief |
Message, audience, key points and outline, agreed and locked before anything is built. |
| Build the deck | /ili-draft-document deck |
Built from the brief if there is one, or from what you tell it. Checked and saved as a new version. |
| The team returns a Word file with comments | /ili-draft-document review |
Tracked changes and comment replies. |
| Too much to do | /ili-project-status triage |
Work you can start, sorted by effort or urgency. Writes nothing. In the fleet hub, /ili-fleet tasks does the same across all your projects. |
| You need an outside fact | /ili-online-research |
An answer with citations. Saves nothing unless you ask. |
| You stop in the middle of a task | /ili-handoff |
A handoff that a later session continues from. |
| End of day: “Save progress” | save → Save progress |
Brings every open thread up to date before you stop. |