From 8abc63efdbc0bb96cd6c9aa99d6e9166e0bcabae Mon Sep 17 00:00:00 2001 From: Peter Stone Date: Sun, 22 Mar 2026 23:45:19 +0000 Subject: chore: unify and centralize agent configuration in .agent/ --- .../references/session-state-standard.md | 41 ++++++++++++++++++++++ 1 file changed, 41 insertions(+) create mode 100644 task-sync-manager/references/session-state-standard.md (limited to 'task-sync-manager/references') diff --git a/task-sync-manager/references/session-state-standard.md b/task-sync-manager/references/session-state-standard.md new file mode 100644 index 0000000..d5149f2 --- /dev/null +++ b/task-sync-manager/references/session-state-standard.md @@ -0,0 +1,41 @@ +# Session State Standard + +This reference defines the expected structure and format for `SESSION_STATE.md` in the `doot` project. + +## Required Sections + +### 1. Current Focus +- A single sentence or a few bullet points describing the primary task for the current session. +- Only one focus should be active at a time. + +### 2. Recently Completed +- A list of tasks completed in the current or most recent sessions. +- Use a bulleted list with a summary of the work (e.g., "Migration 016, Store methods..."). +- Include tests written and verified. + +### 3. Previously Completed +- A historical list of completed tasks, grouped by milestone or theme. +- This section can be moved to a `HISTORY.md` if it grows too large. + +### 4. Known Gaps +- A list of outstanding bugs, missing tests, or implementation details that need future attention. + +### 5. Remaining Items (Feature Requests) +- A list of features that have been discussed but not yet implemented. +- These should often correspond to `claudomator` stories. + +### 6. Next Steps +- A numbered list of the very next actions to take. +- Use this to maintain momentum across sessions. + +## Claudomator Integration +Whenever a task is completed: +1. Move it from "Current Focus" to "Recently Completed". +2. Run `claudomator finish ` (if using ID-based stories). +3. Update "Next Steps" with the next `claudomator` story or sub-task. +4. If a new task is identified, run `claudomator create "Name" --instructions "Goals"`. + +## Formatting +- Use standard GitHub Flavored Markdown. +- Keep the file concise; avoid deep nesting. +- Ensure the date and baseline commit are mentioned in related plans (e.g., `REFACTOR_PLAN.md`). -- cgit v1.2.3