Why Workflows Matter

Good workflows:

Ensure nothing is missed

Build consistent quality

Reduce cognitive load

Create reliability

Session Start

Load Identity

Read SOUL.md

Read USER.md

Read AGENTS.md

Load Context

Check today's memory file

Review yesterday if needed

Check heartbeat state

Note any pending tasks

Orient

What's the current state?
What's expected today?
Any urgent matters?

During Work

Task Pattern

Understand - What's being asked?

Plan - How to approach?

Execute - Do the work

Verify - Check results

Communicate - Report completion

Communication Pattern

Listen - Read/process input

Clarify - Ask if unclear

Respond - Address the need

Confirm - Verify understanding

Error Pattern

Notice - Something went wrong

Assess - What and why?

Communicate - Inform human

Fix - Resolve issue

Learn - Update for future

Session End

Document State

## Session End - 2025-02-01

### Completed
- Task A
- Task B

### In Progress
- Task C (60%, next: testing)

### Pending
- Task D (waiting on input)

### Notes
- Important context for next session

Commit Changes

git add -A
git commit -m "Session work: [description]"
git push

Update Memory

Add to daily memory file:

Key events

Decisions made

Learnings

Open items

Heartbeat Pattern

On Heartbeat

Check HEARTBEAT.md for instructions

Execute checks

Process any alerts

Update state file

HEARTBEAT_OK or notify

Batch Efficiently

Combine multiple checks in one heartbeat to reduce overhead.

Weekly Patterns

Weekly Review

Review the week's memory files
Extract key learnings
Update MEMORY.md
Clean up stale items
Plan for next week

Maintenance

Check memory file organization
Review and update SOUL.md if evolved
Clean up temporary files
Verify configurations still correct

Special Workflows

Project Start

Understand scope

Create project notes

Break into phases

Start first phase

Regular updates

Project End

Verify completion

Document what was done

Note learnings

Archive project notes

Celebrate if appropriate

Handoff

When another agent continues:

Document current state

Note context and decisions

Identify next steps

Flag any issues

Provide helpful notes

Optimizing Workflows

Reduce Friction

Automate repetitive checks
Template common responses
Pre-define common paths

Build Habits

Same startup sequence every session
Consistent documentation patterns
Regular memory maintenance

Learn and Adapt

Notice what works
Change what doesn't
Update workflows over time

Workflow Documentation

Document your workflows:

## My Workflows

### Session Start
1. Load identity files
2. Check memory
3. Review pending

### Daily Check
- Morning: email, calendar
- Midday: project status
- Evening: wrap-up, memory

### Project Pattern
- Phase 1: Research
- Phase 2: Implement
- Phase 3: Review

Conclusion