The week slash commands replaced half my typing

ARTICLEGROWTH TACTICFRIDAY (AI CHIEFOFSTAFF)

Ronsley Vaz

4/27/20262 min read

I was typing the same six requests a hundred times a day.

"Brief me on today." "Save the session and sync to my task board." "Score this draft against my voice." "Package this draft for publishing." "Help me sort what's in the inbox." "Add this to tonight's batch."

Same words, same formatting, same context. Every single time.

I'd built Friday to think. I was still making her re-listen to the same questions. That's not delegation, that's repetition with extra steps.

A good chief of staff knows your routines. You don't brief them on the brief every morning.

What shipped

Seven things.

1. A convention doc. Decided when something becomes a slash command vs a skill vs a hook. Wrote the decision tree down so future me would stop second-guessing it. Plus a validator that checks every command file has what it needs.

2. /brief. Morning briefing. Focus, calendar, inbox, landfill, nightly batch outcome, flags. Same structure, every day. I type three characters. Friday hands me the day.

3. /eod. End of day. Updates my state file, writes the day's decisions to long-term memory, syncs the task board, shows tomorrow's preview. One command, ten jobs done.

4. /voice-check. Pass it a draft path. Friday runs the linter, runs the voice review, drops a score file next to the draft. The answer to "does this sound like me?" in about three seconds.

5. /ship. Pass it a draft. Refuses anything scored below 9 out of 10. Detects which platform the draft is for. Packages it ready for the content calendar. The only way anything of mine leaves the draft folder.

6. /landfill-triage. For the stuff that lands without a clear home. Friday proposes which project it belongs to. I approve, she files.

7. /queue-add. Appends a task to the nightly batch queue. The overnight job picks it up while I sleep. I stop holding things in my head until Monday.

What it unlocked

  1. I stopped re-explaining the routine.

  2. The morning brief was a command, not a conversation. The end-of-day save was a command. The voice check, the ship, the triage, the queue: all commands. Muscle memory, not prose.

  3. I got an hour back a day.

  4. And the routines stayed consistent. When I typed /brief the structure didn't drift. When I typed /eod the sync didn't skip a step. The same thing happened the same way every time.

That's the part a chief of staff gets right that a brilliant intern never does. Not the creativity. The repetition.

Copy this if you're building your own

  • Watch yourself for a week. Every time you type something to your AI that feels familiar, write it down. By Friday you'll have a list of 5 to 10 prompts you keep re-typing.

  • Turn each one into a command. Short name, fixed arguments, fixed output format. The command shouldn't be clever. It should be boring. Boring is the goal. Boring is repeatable.

  • Then never type the long version again.

Episode 3 of 19. I'm walking through every sprint I ran to build Friday. New episode every Monday, Wednesday, and Friday through Episode 19. Next: Friday lands on my phone.

Want to start your own Friday? Grab it free at friday.amplifyais.com.