Workflow

Start of Session

Before doing any work, agents scan this places:

1. Open boards/tasks.page. Read what is in progress and what is next. This is your starting context.

2. Open history/index.page. Read the most recent entry to recall where things were left and what decisions were made.

3. Read also boards/backlog.page. There could be additional information.

After that, an agent can propose to work on a task or asks what to do. 

End of Session

Before closing, users and agents can use this actions:

1. Update History 
Log what was done, what was decided, and why. Always.

2. Update Tasks
Move completed items to Done, update in-progress items, add new ones.

3. Update Outline
When something changed at the project level: new system built, scope shifted, key decision made.

For Agents

Before starting any task, an agent must:

1. Read the overview of the guides and read more about rules that are relevant to a task.

2. Read the reference - to get short cuts for understanding the code

3. When the process of thinking takes longer than 2k tokens, try to involve the user: Comminucate it takes longer or ask whether the user can help.

The Rhythm

The workspace becomes productive when it is updated consistently. The loop is:

Read → Work → Test → Document → Repeat

Reading the workspace before starting means less time reconstructing context. Updating the workspace after finishing means the next session - whether yours or an agent's - starts with full context.

Short history entries are better than none. A rough task list is better than an empty board.