chore: unify and centralize agent configuration in .agent/

2 files changed, 70 insertions, 0 deletions

diff --git a/task-sync-manager/SKILL.md b/task-sync-manager/SKILL.md
new file mode 100644
index 0000000..69d9bfb
--- /dev/null
+++ b/task-sync-manager/SKILL.md
@@ -0,0 +1,29 @@
+---
+name: task-sync-manager
+description: Manage and synchronize session state with task management tools. Use when updating SESSION_STATE.md, moving tasks to Recently Completed, or creating/completing stories in claudomator.
+---
+
+# Task Sync Manager
+
+This skill formalizes the synchronization of task progress between documentation and management tools.
+
+## Workflow
+
+### 1. Update Session State
+- When a task or sub-task is completed, move it from **Current Focus** to **Recently Completed** in `SESSION_STATE.md`.
+- Be specific about what was done (e.g., "Migration 017 added, tests passing").
+- Ensure **Next Steps** are clearly defined.
+
+### 2. Claudomator Integration
+- After completing a task, verify if it corresponds to a `claudomator` story.
+- Create new stories as needed: `claudomator create "Task Name" --instructions "Detailed goals"`.
+- Use `claudomator list` to view open tasks.
+
+### 3. Maintain Documentation
+- Ensure `SESSION_STATE.md` follows the structure in [references/session-state-standard.md](references/session-state-standard.md).
+- Keep **Known Gaps** and **Remaining Items** up-to-date with findings from the current session.
+
+## Quick Start
+- "Update session state to show Task X is done" -> Move Task X to Recently Completed.
+- "Create a claudomator story for refactoring meals" -> `claudomator create "Refactor Meal Grouping" --instructions "RF-03 from REFACTOR_PLAN.md"`.
+- "Show me the next steps" -> Check `SESSION_STATE.md`.
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`).