tododdle-mcp 3.1.0 → 3.1.1

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "tododdle",
-  "version": "3.1.0",
+  "version": "3.1.1",
   "description": "Disciplined agent workflows for projects managed in ToDoddle.",
   "author": {
     "name": "ToDoddle",

package/README.md

@@ -87,6 +87,14 @@ Restart Codex, open the Plugins Directory, select **ToDoddle**, and install the
 
 Installing the plugin does not create or expand ToDoddle credentials, scopes, or project grants. The skill declares the separately configured `tododdle` MCP server as a dependency.
 
+### Scheduled ToDoddle Workflows
+
+The distributed skill includes opt-in recipes for a morning control tower, ticket review sweep, weekly backlog hygiene, roadmap summary, Agent Connection inbox follow-up, and local release verification. Each recipe defines a suggested cadence, required scopes, mutation level, prompt, duplicate controls, and approval boundaries.
+
+Installing the plugin never creates a schedule. Ask Codex to create a named recipe, then confirm the timezone, project, cadence, and allowed mutation level. Test the prompt in a normal chat and review the first runs. Scheduled tasks can use the ToDoddle plugin and its connected MCP tools. Desktop tasks that need local files also require the project to remain available and the app to be running. See the [scheduled tasks documentation](https://learn.chatgpt.com/docs/automations).
+
+Use scheduled ToDoddle workflows for user-level checks and reports. Keep required service operations, such as notification delivery, billing reconciliation, webhook retries, and backups, in ToDoddle's server-owned queue or cron system.
+
 ### Bounded Project Context
 
 For substantial planning or implementation, load project context in a small, predictable sequence:

package/dist/compatibility.d.ts

@@ -1,9 +1,9 @@
-export declare const MCP_PACKAGE_VERSION = "3.1.0";
+export declare const MCP_PACKAGE_VERSION = "3.1.1";
 export declare const MCP_COMPATIBILITY_LEVEL = 3;
 export declare const MCP_VERSION_HEADER = "x-tododdle-mcp-version";
 export declare const MCP_COMPATIBILITY_HEADER = "x-tododdle-mcp-compatibility";
 export declare const MCP_REQUEST_HEADERS: {
-    readonly "x-tododdle-mcp-version": "3.1.0";
+    readonly "x-tododdle-mcp-version": "3.1.1";
     readonly "x-tododdle-mcp-compatibility": string;
 };
 export declare function formatMcpUpdateRequiredMessage(message: string, details: unknown): string;

package/dist/compatibility.js

@@ -1,4 +1,4 @@
-export const MCP_PACKAGE_VERSION = '3.1.0';
+export const MCP_PACKAGE_VERSION = '3.1.1';
 export const MCP_COMPATIBILITY_LEVEL = 3;
 export const MCP_VERSION_HEADER = 'x-tododdle-mcp-version';
 export const MCP_COMPATIBILITY_HEADER = 'x-tododdle-mcp-compatibility';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tododdle-mcp",
-  "version": "3.1.0",
+  "version": "3.1.1",
   "description": "Agent-first task, project context, and time tracking for ToDoddle",
   "type": "module",
   "main": "dist/index.js",

package/skills/tododdle-workflow/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: tododdle-workflow
-description: Use ToDoddle as the work ledger for project boards, lanes, tickets, implementation, status updates, blockers, comments, and time tracking. Trigger when the user asks to inspect, plan, start, update, complete, or report on work managed in ToDoddle, or when repository instructions require ToDoddle updates. Do not trigger for casual discussion that does not change or review tracked work.
+description: Use ToDoddle as the work ledger for project boards, lanes, tickets, implementation, status updates, blockers, comments, time tracking, and safe recurring checks. Trigger when the user asks to inspect, plan, start, update, complete, report on, or schedule work managed in ToDoddle, or when repository instructions require ToDoddle updates. Do not trigger for casual discussion that does not change or review tracked work.
 ---
 
 # ToDoddle Workflow
@@ -46,6 +46,16 @@ Keep list requests bounded and paginate rather than requesting an entire organiz
 
 Do not create bookkeeping churn for tiny exploratory actions. Prefer one useful checkpoint over a stream of narration.
 
+## Schedule Recurring Checks
+
+When a user asks to schedule ToDoddle work, read [scheduled-workflows.md](references/scheduled-workflows.md). Use its ready-to-create recipes and safety rules.
+
+- Create a schedule only after the user chooses a recipe, cadence, timezone, project scope, and allowed mutation level. Installing the plugin must never create or enable a schedule.
+- Test the complete prompt in a normal chat before scheduling it. Review the first runs and narrow the prompt if it reads or changes too much.
+- Default to read and report. Permit comments, ticket creation, or status changes only when the user explicitly selects that mutation level.
+- Keep destructive actions, access changes, billing changes, secrets, and completion without verification outside scheduled work.
+- Do not use a user-side scheduled task for required server operations such as notification delivery, billing reconciliation, webhook retries, or backups. Use the application's durable queue or cron system for those jobs.
+
 ## Upload Files Safely
 
 - Use `upload_project_document` or `attach_file_to_ticket` for approved files.

package/skills/tododdle-workflow/references/scheduled-workflows.md

@@ -0,0 +1,91 @@
+# Scheduled ToDoddle Workflows
+
+Use these recipes to create opt-in scheduled tasks. Do not activate a schedule during plugin installation.
+
+## Set Up a Recipe
+
+1. Confirm the user's timezone, cadence, project scope, and allowed mutation level.
+2. Confirm that the ToDoddle Agent Connection grants the required project and scopes.
+3. Replace every angle-bracket placeholder in the selected prompt.
+4. Run the prompt once in a normal chat. Fix missing access or overly broad results.
+5. Create the schedule. Review its first runs before allowing mutations.
+
+Use a task in an existing chat when later runs need that chat's context. Use a standalone task when each run should start from the saved prompt. A web task can use the connected ToDoddle plugin but cannot access a local repository. A desktop task that needs local files requires the project to remain available and the app to be running.
+
+## Safety Rules
+
+- Default to **read and report**.
+- Reuse verified project, board, and lane IDs from the saved prompt. Refresh ticket state on each run.
+- Bound every list request. Follow pagination only as far as the recipe requires. State when a report is partial.
+- Find an existing ticket before creating one. Use a stable idempotency key for any repeated additive action.
+- Write at most one useful summary comment per run. Do not narrate tool calls.
+- Do not delete or archive records, change access, change billing, expose secrets, or mark work complete without current verification.
+- Stop and report a missing scope, project grant, ambiguous project, concurrency conflict, or destructive follow-up.
+
+## Recipe: Morning Control Tower
+
+**Suggested cadence:** Weekdays at 8:30 AM local time  
+**Required scopes:** `projects:read`, `tasks:read`  
+**Mutation level:** Read and report
+
+```text
+Use $tododdle-workflow for project <project ID>. Reuse the verified project ID. Read the bounded active work queue, overdue work, and unassigned work. Summarize what needs attention today under Blocked, Overdue, Unassigned, In progress, and In review. Include stable ToDoddle links. Do not create, edit, move, complete, or archive tickets. If access is missing or a result is partial, say so clearly.
+```
+
+## Recipe: Ticket Review Sweep
+
+**Suggested cadence:** Weekdays at 10:00 AM local time  
+**Required scopes:** `projects:read`, `tasks:read`  
+**Mutation level:** Read and report
+
+This recipe covers tickets with the `REVIEW` status. Formal review-request queues require future MCP review tools.
+
+```text
+Use $tododdle-workflow for project <project ID>. List active tickets with status REVIEW. Treat a ticket as stale after <number> days without an update. Read full ticket context only for stale or ambiguous results. Report the reviewer or owner action needed and include stable ToDoddle links. Do not approve, complete, reject, or comment on a ticket.
+```
+
+## Recipe: Weekly Backlog Hygiene
+
+**Suggested cadence:** Fridays at 2:00 PM local time  
+**Required scopes:** `projects:read`, `tasks:read`  
+**Mutation level:** Read and report
+
+```text
+Use $tododdle-workflow for project <project ID>. Inspect a bounded active ticket set for likely duplicates, missing priority, missing ownership, stale in-progress work, invalid blocker state, and unclear titles. Do not change tickets. Give a short proposed-action list with stable ToDoddle links. State the page and item limits used and say when the audit is partial.
+```
+
+## Recipe: Weekly Roadmap Summary
+
+**Suggested cadence:** Fridays at 3:00 PM local time  
+**Required scopes:** `projects:read`, `tasks:read`  
+**Mutation level:** Read and report
+
+```text
+Use $tododdle-workflow for project <project ID>. Summarize meaningful ticket movement since <reporting rule, such as the last 7 days>. Group the result under Completed, Active, In review, Blocked, and New risks. Prefer counts and important changes over a full ticket dump. Include stable ToDoddle links. Do not change project state. State when bounded results make the summary partial.
+```
+
+## Recipe: Agent Inbox Follow-up
+
+**Suggested cadence:** Every two hours during working hours  
+**Required scopes:** The scopes needed to read the replied-to records  
+**Mutation level:** Read and report
+
+```text
+Use $tododdle-workflow. Read the current Agent Connection inbox for unacknowledged replies. Summarize each reply with its linked ticket or Context item and the next action. Do not acknowledge a reply, change a record, or create a ticket. If there are no replies, report no action.
+```
+
+## Recipe: Local Release Verification
+
+**Suggested cadence:** After the normal deployment window  
+**Required scopes:** `projects:read`, `tasks:read`; add `tasks:write` only for an approved evidence comment  
+**Mutation level:** Read and report, or one evidence comment when explicitly enabled
+
+Use this recipe only in a desktop task with the correct local repository available.
+
+```text
+Use $tododdle-workflow for project <project ID> and ticket <ticket ID>. Refresh the ticket and inspect the local repository. Run only the approved verification checks: <checks>. Do not deploy, push, change billing, change access, or modify production data. Report the result with immutable evidence. If mutation level permits it, add one Markdown HANDOFF comment with Outcome, Verification, and Remaining. Do not complete the ticket automatically.
+```
+
+## Do Not Schedule User-Side Server Jobs
+
+Do not use these recipes for notification delivery, email digests, subscription reconciliation, webhook retries, backups, or other required service operations. Those jobs must run in ToDoddle's server-owned queue or cron system so they do not depend on a user's computer, chat, or plugin session.