Skip to content
StellarFirmStellarFirm
Mission manual
Esc

Type a word to search every page. Try , or .

Module 02 · The CEO

Delegate work

Where and how you hand work to your assistants: the StellarFirm chat, Slack, Telegram, Discord, and Microsoft Teams, and what a good hand-off says.

View as Markdown
On this page

As the CEO you delegate outcomes, not keystrokes. You say what you want and what done looks like, the right assistant does the work, and anything risky comes back to you for Approve. This page shows where you can hand work over today, what is on the way, and how to write a hand-off that needs no follow-up questions.

Where you can hand work over#

PlaceStatusApprove or Reject there?Best for
StellarFirm chat on the web, at stellarfirm.ai/appAvailableYes, under the messageEveryday work, from any browser
StellarFirm desktop appAvailableYes, under the messageThe same chat, plus connecting your code host
Approvals pageAvailableYes, everything waiting in one listClearing requests from every chat at once
SlackComing soonYes, buttons in the threadTeams that already live in Slack
TelegramComing soonYes, buttons in the chatQuick messages from your phone
DiscordComing soonYes, buttons in the channelCommunities and small teams on Discord
Microsoft TeamsComing soonNot yetUse the StellarFirm chat meanwhile
Phone appComing soonDelegating on the move
EmailNot availablePaste the request into the StellarFirm chat

Wherever you start, the rules are the same: reads run on their own, and every step that sends, deploys, charges, publishes, or creates waits for your Approve or follows your house rules.

Before you delegate code work#

The Coder can only work where it has access. Do these once:

  1. Connect your code host. GitHub, GitLab, or Bitbucket, in the StellarFirm desktop app. Connect your code is the checklist, with every permission side by side.
  2. Give each Coder its repository. Under Settings, Coders, or name it in each message.
  3. Write your house rules. Decide the merge policy and whether the Coder may ship. Start with review only.

What a good hand-off says#

PartExample
Who"Coder," or a Coder's handle, such as @api-coder
WhereThe repository: acme/web
WhatThe outcome: "users stay signed in after a password change"
Done when"the tests pass and there is a pull request for review"
Limits"do not touch billing; no new dependencies"
Where it stops"open a pull request for review", or "merge once checks pass" if your house rules allow it
PromptHand-off template

Coder, in [repository], [the outcome you want]. Done when [how you will check it]. Do not [limits]. Open a pull request for review once I Approve, and give me a three-line summary.

A hand-off with all six parts rarely comes back with a question. If the Coder or the CEO assistant does ask, answer in one line.

Who picks it up#

  • Name an assistant at the start of the message to send the work straight there: "Coder," or @coder.
  • Name one of several Coders by its handle or name: @api-coder, or "API Coder,".
  • Name nobody and the work goes to the assistant whose job it is. With several Coders, the one whose focus or repository fits takes it, and the default Coder takes the rest.

See routing for the details.

Approving from wherever you are#

  • A request that needs you shows Approve and Reject where you asked, and also on the Approvals page.
  • Only the person who asked can decide. If two places show the same request, the first answer wins.
  • Reject sends, pushes, and creates nothing.
  • While a step waits, the rest of the job waits too. You do not have to answer right away.

Prompts#

PromptHand over a goal

CEO, I want [outcome] on [repository]. Brief the right assistant, tell me what will need my approval, and report back when it is done.

PromptSend work to one Coder

@api-coder in [repository], add [endpoint]. Run the tests and open a pull request for review once I Approve.

To split work across several Coders, send one message per Coder. They work in parallel, each in its own workspace.

PromptStatus of everything delegated

CEO, list everything my assistants are working on, what is done, and what is waiting for me, newest first.

PromptHand over a request from another tool

Coder, a customer reported this: [paste the report, no personal data]. In [repository], find the cause, fix it with a regression test, and open a pull request for review.

Next#