# Keep a schedule of posts

> Put a blog post kept in Zeus Mode on your team's schedule, give it the day it goes out, tick its parts as they are done, write where the work stopped, and print the list with zeus schedule — and what an agent may and may not do with a row.

*You write blog posts with your team, and you want one list of what is still
to go out: which post goes out on which day, what is done, and what is
missing. Zeus Mode for Claude Code and Codex keeps that list for your
workspace. Every teammate sees the same list, and you print it with one
command, `zeus schedule list`.*

*Checked on 18 November 2026, on macOS 27.0.1. The schedule is not in Zeus
Mode 0.43.0; it comes in the release after it. Every `zeus schedule` command
below was run on a build of that release's work, in a test workspace whose
GitHub repository was a folder on the Mac, and the schedule tool was called
the same way. The outputs are copied from those runs. Where a line shows `your
name`, the run showed the name of the person who ran it. Where it shows `…`,
an agent wrote the line (see [What an agent may do](#what-an-agent-may-do)).*

## What the schedule is

The schedule is a list of **rows**. Each row is for one **post**: a blog post
in progress, kept in your workspace's document store (see
[Keep a page for your team](/docs/documents/)). A row holds only four things:

- the **day** the post goes out, or no day yet;
- which of its **parts** are done — each part is ticked when it is done;
- **where the work stopped**: one short line, so anyone can pick it up later;
- whether the post is **put aside** for later.

A row holds no words and no pictures. Those stay in the post itself.

A blog post has six parts. When a part is done, you **tick** it: you mark it
as done. You name a part by its **key**, the short word in the first column:

| Key | The part | When |
|---|---|---|
| `words-approved` | Words approved | before the day |
| `title-summary` | Title and summary set | before the day |
| `pictures` | Pictures in place | before the day |
| `links-checked` | Links checked | before the day |
| `site-build` | Builds for the site | before the day |
| `follow-up` | Follow-up posted | after the post is live |

The list counts the five parts due before the day, so a new row shows
`0 of 5`. When all five are ticked, it shows `ready`.

The rows are kept in the workspace's **instructions home** — the private
GitHub repository that also keeps your team's documents and todo list — in a
folder named `schedule/`. Each change is one commit there. Nobody needs to
review or merge anything.

The app does not show the schedule yet. You read it in a terminal, or a
session reads it for you.

## Before you start

You need three things:

1. **Zeus Mode, new enough to keep a schedule.** To check, run:

   ```
   zeus schedule --help
   ```

   Its first line starts with `zeus schedule — the posts still to go out`. If
   it says `zeus: unknown command "schedule"`, your Zeus Mode is older than
   the schedule: see
   [Keep Zeus Mode up to date](/docs/getting-started/#keep-zeus-mode-up-to-date).
2. **An instructions home for the workspace**, and write access to it on
   GitHub. If you already keep documents, you have one. If not, see
   [Before you start](/docs/documents/#before-you-start) in the documents
   guide.
3. **A post in the store.** A row can only be made for a post that is
   already kept. To make an empty one with its title, run this inside a
   repository of the workspace:

   ```
   zeus doc post --title "Why small teams ship faster" --words "make a post called Why small teams ship faster"
   ```

   Zeus Mode answers:

   ```
   Made the post why-small-teams-ship-faster in github.com/acme/zeus-instructions, commit 7ccd6b20f91085a2503810e1e1465d9cab7179b8: post.md, empty, started new. zeus doc edit why-small-teams-ship-faster hands out its working copy.
   ```

   `why-small-teams-ship-faster` is the post's **name**. Every `zeus schedule`
   command uses this name. You can also make a post from a document you kept,
   with **Make a post from this document** in the app
   ([how](/docs/documents/#make-a-post-from-this-document)). `zeus doc list`
   shows the names of all the posts.

Run `zeus schedule` inside a repository of the workspace. If that repository
is in more than one workspace, or you are in a folder of no workspace, add
`--workspace` and the workspace's name, for example `--workspace "Try Team"`.

**Where you run the commands that change a row.** Every `zeus schedule`
command except `list` first checks that it comes from you, not from a Claude
Code or Codex session. If a session is working in the same folder, or in a
folder above it, Zeus Mode cannot tell your terminal from that session, and
refuses:

```
Zeus cannot tell this terminal from a session: a session is working in this folder. Run the same line from another folder.
```

Most people keep a session open in their repository. Then run these
commands from a folder where no session works, and name the workspace:

```
cd ~
zeus schedule date why-small-teams-ship-faster 2026-11-30 --workspace "Try Team"
```

If you started a session in your home folder, use another folder, such as
`/tmp`.

## Put a post on the schedule

```
zeus schedule add why-small-teams-ship-faster
```

```
Added the row for why-small-teams-ship-faster in github.com/acme/zeus-instructions, commit 0e11cd3f8b23a9daa1e6993ba38fefc86918da51.
```

The post now has a row, with no day and no part ticked.

## Print the schedule

```
zeus schedule list
```

```
Schedule · Try Team · 1 post waiting · kept in github.com/acme/zeus-instructions
  no date   why-small-teams-ship-faster   0 of 5
```

The first line names the workspace, how many posts are **waiting** (not yet
live), and the repository the rows are kept in. Then there is one line for
each waiting post: its day (or `no date`), its name, and how many parts are
ticked. After that, the line may say `later` if the post is put aside, and
where the work stopped, with who wrote it and on which day.

The list reads the rows from GitHub each time, so a row a teammate changed a
moment ago shows at once.

## Set the day it goes out

The day is written year-month-day:

```
zeus schedule date why-small-teams-ship-faster 2026-11-30
```

```
Set why-small-teams-ship-faster to go out on 2026-11-30 in github.com/acme/zeus-instructions, commit 0c80faac0b4809270fae5b53b709b53d3bdc98f7.
```

The list now shows the day:

```
Schedule · Try Team · 1 post waiting · kept in github.com/acme/zeus-instructions
  Mon 30 Nov   why-small-teams-ship-faster   0 of 5
```

To change the day, run the same command with the new day. To take the day
off, use `--none`:

```
zeus schedule date why-small-teams-ship-faster --none
```

```
Took the date off why-small-teams-ship-faster in github.com/acme/zeus-instructions, commit 59ff497b12e886f6e32d9c0ab6bef7dfa1d73089.
```

Zeus Mode does not check that the day is still to come: a day in the past is
accepted, and a day in another year is listed with its year, such as
`Wed 1 Jan 2020`. Only a person sets a day (see
[What an agent may do](#what-an-agent-may-do)). Setting a day does not
publish anything: the post goes out when you publish it.

## Tick its parts

Tick a part with its key, from the table above:

```
zeus schedule tick why-small-teams-ship-faster words-approved
```

```
Ticked words-approved on why-small-teams-ship-faster in github.com/acme/zeus-instructions, commit 3c3c86f01ad81319668632074cfa64996c3ddd88.
```

You can say where the work stopped in the same command, with `--stopped`:

```
zeus schedule tick why-small-teams-ship-faster title-summary --stopped "pictures next"
```

Ticking a part that is already ticked changes nothing, and says so:

```
why-small-teams-ship-faster's row in github.com/acme/zeus-instructions already says so; nothing changed.
```

## Write where the work stopped

When you stop working on a post, write one line that says where you are, so
you — or a teammate — can pick it up later:

```
zeus schedule stopped why-small-teams-ship-faster "two pictures drawn, one to go"
```

```
Wrote where why-small-teams-ship-faster stopped in github.com/acme/zeus-instructions, commit ec0d132e07c4f8bbad0a8b531332aef76f6913cc.
```

The line is at most 160 characters, and it replaces the line before. The
list shows it with who wrote it and when:

```
Schedule · Try Team · 1 post waiting · kept in github.com/acme/zeus-instructions
  Mon 30 Nov   why-small-teams-ship-faster   2 of 5 · two pictures drawn, one to go (your name, 18 Nov)
```

## Untick a part

A part ticked by mistake is unticked, by a person:

```
zeus schedule untick why-small-teams-ship-faster title-summary
```

```
Unticked title-summary on why-small-teams-ship-faster in github.com/acme/zeus-instructions, commit 586ed7787d36c287e437b5c64dd43f3571dce116.
```

Tick it again when it is really done.

## When every part is done

Tick the other parts as they are done:

```
zeus schedule tick why-small-teams-ship-faster title-summary
zeus schedule tick why-small-teams-ship-faster pictures
zeus schedule tick why-small-teams-ship-faster links-checked
zeus schedule tick why-small-teams-ship-faster site-build
```

When all five parts before the day are ticked, the count becomes `ready`:

```
Schedule · Try Team · 1 post waiting · kept in github.com/acme/zeus-instructions
  Mon 30 Nov   why-small-teams-ship-faster   ready · two pictures drawn, one to go (your name, 18 Nov)
```

## What an agent may do

A Claude Code or Codex session reaches the schedule through Zeus Mode's
`schedule` tool, or through the same `zeus schedule` command. An **agent** —
the assistant working in that session — may do only some things with a row.
The others are yours, and you do them in your own terminal.

| | An agent in a session | You, in your own terminal |
|---|---|---|
| Print the list | yes | yes |
| Add a row | only with your own words approving the post's topic | yes |
| Tick a part | yes, except **Words approved** | yes |
| Write where the work stopped | yes | yes |
| Set or take off the day | no | yes |
| Untick a part | no | yes |
| Put a post aside, or resume it | no | yes |
| Remove a row | no | yes |

For the examples below there is a second post, made the same way as the
first:

```
zeus doc post --title "What a review costs" --words "make a post called What a review costs"
```

**Adding a row.** An agent adds a row only when it sends your own words, as
you said them, that approve the post's topic. Without them, Zeus Mode
refuses:

```
zeus schedule add: A session adds a row only with the owner's own words approving the post's topic: send them in words, as he said them. Nothing changed.
```

With them, for example `--words "yes, write the one about what a review
costs"`, the row is added, and your words are kept on the row as the reason
it was added:

```
Added the row for what-a-review-costs in github.com/acme/zeus-instructions, commit a66eabf14396831edde3a5b5f7654aa4db412ef1.
```

**Ticking and where it stopped.** In the run, the agent then ticked
`title-summary` and wrote `outline agreed, draft next`. The list shows that
line with the agent's name, when the session has named its agent to Zeus
Mode. A session that has not shows `session:` and the session's id, and the
test run showed `session:unknown`. The examples below show `…` there.

**Words approved.** Only you tick this part, because only you approve the
words. Zeus Mode cannot yet take the tick off if the words change later, so an
agent is refused:

```
zeus schedule tick: Words approved is ticked by a person in their own terminal until Zeus can take the tick off when the words change. Ask the person to run, in their own terminal:
  zeus schedule tick what-a-review-costs words-approved
```

**Everything in the "no" rows.** Zeus Mode refuses the agent and gives it the
line for you to run. For example, for a day:

```
zeus schedule date: A date is set by a person in their own terminal, never from a Claude Code or Codex session. Ask the person to run, in their own terminal:
  zeus schedule date what-a-review-costs 2026-12-07
```

Through the `schedule` tool, the line has `<day>` in place of the day, and
the agent fills in the day you asked for. The agent should show you the line.
Run it in a terminal of your own, from a folder where no session works (see
[Before you start](#before-you-start)). Nothing changes until you do.

## Put a post aside

To keep a post for later without losing its row:

```
zeus schedule later what-a-review-costs
```

```
Put what-a-review-costs aside in github.com/acme/zeus-instructions, commit bcfe2edab0c314c00e1fc77c706d434825fe35dc.
```

The list then says `later` on its line:

```
Schedule · Try Team · 2 posts waiting · kept in github.com/acme/zeus-instructions
  Mon 30 Nov   why-small-teams-ship-faster   ready · two pictures drawn, one to go (your name, 18 Nov)
  no date      what-a-review-costs           1 of 5 · later · outline agreed, draft next (…, 18 Nov)
```

To take `later` off again:

```
zeus schedule resume what-a-review-costs
```

```
Resumed what-a-review-costs in github.com/acme/zeus-instructions, commit 12a991832bf2f70df018d5f7c74bb6c06b239fd3.
```

## When the post is live

You do not remove a row when its post is published. Record the post's live
address on the post, as the documents guide says
([Copy: publish this post](/docs/documents/#copy-publish-this-post)):

```
zeus doc live why-small-teams-ship-faster --url https://example.com/blog/why-small-teams-ship-faster/ --words "it is live at https://example.com/blog/why-small-teams-ship-faster/"
```

From then on the post is no longer waiting. Until its follow-up part is
ticked, the list shows it under **Live, still to do**:

```
Schedule · Try Team · 1 post waiting · kept in github.com/acme/zeus-instructions
  no date      what-a-review-costs           1 of 5 · outline agreed, draft next (…, 18 Nov)
Live, still to do
  Mon 30 Nov   why-small-teams-ship-faster   follow-up posted
```

When you have posted the follow-up, tick it:

```
zeus schedule tick why-small-teams-ship-faster follow-up
```

and the post leaves the list. To see every live post too, add `--all`:

```
zeus schedule list --all
```

```
Schedule · Try Team · 1 post waiting · kept in github.com/acme/zeus-instructions
  no date      what-a-review-costs           1 of 5 · outline agreed, draft next (…, 18 Nov)
Live
  Mon 30 Nov   why-small-teams-ship-faster   live
```

## Take a row out

To take a row out of the schedule completely, for a post you will not
publish:

```
zeus schedule remove what-a-review-costs
```

```
Removed the row for what-a-review-costs in github.com/acme/zeus-instructions, commit dc0f60a6908c04af176e7072582447e2447b3df4.
```

This takes out only the row. The post itself stays in the store, and
`zeus doc list` still shows it.

## When something goes wrong

**"Zeus cannot tell this terminal from a session: a session is working in
this folder. Run the same line from another folder."** — a Claude Code or
Codex session is working in this folder, or in a folder above it. Run the
same line from a folder where no session works, with `--workspace` (see
[Before you start](#before-you-start)).

**"This terminal still names a session that has ended"** — the terminal was
opened by a session that has now ended. Open a new terminal window and run
the same line there.

**"… is not a day: write it 2026-11-30."** — write the day as
year-month-day, with two digits for the month and the day.

**"… is not a part of a blog post: words-approved, title-summary, pictures,
links-checked, site-build, follow-up."** — use one of the keys the message
lists.

**"… has no row; zeus schedule add … makes one."** — the post has no row yet,
or the name is spelled differently. `zeus schedule list` names the rows, and
`zeus doc list` names the posts.

**"… already has a row; zeus schedule list shows it."** — the post is on the
schedule already. Nothing changed.

**"There is no post named … in the store"** — make the post first, with
`zeus doc post`, then add its row.

**"This folder is in no workspace with an instructions home"** — you are
outside the workspace's repositories. Add `--workspace` and the workspace's
name. The message also names the command that makes an instructions home:
you need it only if your workspace has none yet (see
[Before you start](/docs/documents/#before-you-start) in the documents guide).

**"Changing the parts list is not built yet"** — `zeus schedule parts` is
listed in the help, but every post uses the six parts above for now.
