summaryrefslogtreecommitdiff
path: root/task-sync-manager/references/session-state-standard.md
diff options
context:
space:
mode:
Diffstat (limited to 'task-sync-manager/references/session-state-standard.md')
-rw-r--r--task-sync-manager/references/session-state-standard.md41
1 files changed, 41 insertions, 0 deletions
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 <story_id>` (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`).