From fb4e45fc4e830f1391cb3bae56b0773cf75bc66c Mon Sep 17 00:00:00 2001 From: Paul Buetow Date: Tue, 3 Mar 2026 22:30:49 +0200 Subject: more on this --- prompts/commands/create-tasks.md | 7 ++++- prompts/commands/start-work-on-tasks.md | 56 --------------------------------- prompts/commands/work-on-tasks.md | 56 +++++++++++++++++++++++++++++++++ 3 files changed, 62 insertions(+), 57 deletions(-) delete mode 100644 prompts/commands/start-work-on-tasks.md create mode 100644 prompts/commands/work-on-tasks.md diff --git a/prompts/commands/create-tasks.md b/prompts/commands/create-tasks.md index 1292f12..a7e8c89 100644 --- a/prompts/commands/create-tasks.md +++ b/prompts/commands/create-tasks.md @@ -60,7 +60,7 @@ You are an assistant that, when invoked via `/create-tasks`, turns a high-level - For each task: - Use a concise, verb-first description (e.g., "Configure GitHub Actions workflow for tests"). - Add meaningful tags (e.g., project name, area like `dev`, `docs`, `infra`). - - Set a `project` field in Taskwarrior that reflects the goal (e.g., `timr.ci`, `blog.post_x`). + - Prefer tying tasks to the **current git project** when invoked inside a repo. Set a `project` field in Taskwarrior that reflects that project (e.g., `timr.ci`, `blog.post_x`), keeping it consistent with how `/work-on-tasks` scopes work. - Add an annotation that links back to the plan file path, for example: `"See overall plan: "`. - Use the appropriate tooling/commands to create the tasks (e.g., `task add ...`) in the user’s Taskwarrior setup. @@ -71,6 +71,11 @@ You are an assistant that, when invoked via `/create-tasks`, turns a high-level - Can be completed in a focused sitting - Avoid microscopic tasks that don’t stand alone (e.g., "open editor"). + 4.5. **Behavior expectations (alignment with `/work-on-tasks`)** + - Default to autonomous execution; do **not** ask the user to manually specify each task. + - Do not ask the user to pick or refine steps unless there is a true ambiguity or significant risk. + - Keep the task scope tied to a coherent project (ideally the current git project when applicable). + 5. **Summarize to the user** - After writing the plan and creating the tasks: - Show the plan file path. diff --git a/prompts/commands/start-work-on-tasks.md b/prompts/commands/start-work-on-tasks.md deleted file mode 100644 index 2099300..0000000 --- a/prompts/commands/start-work-on-tasks.md +++ /dev/null @@ -1,56 +0,0 @@ -# /start-work-on-tasks - -**Description:** Automatically work through Taskwarrior tasks for the current git project using the `taskwarrior-task-management` skill. The command selects the best pending task, starts it, executes it, completes it, and then auto-progresses to the next task until no actionable tasks remain. - -**Parameters:** -- strategy (optional): How to choose tasks when multiple are available (e.g., "highest-impact", "priority", "due-date", "quick-win") -- max_tasks (optional): Safety limit for how many tasks to process in one run - -**Example usage:** -- `/start-work-on-tasks` -- `/start-work-on-tasks highest-impact` -- `/start-work-on-tasks priority 5` - ---- - -## Prompt - -Use the `taskwarrior-task-management` skill for this entire workflow. - -I want you to automatically execute Taskwarrior work for the **current git project** from start to finish. - -1. **Load project-scoped tasks**: - - Detect the current project from local git context - - List pending Taskwarrior tasks for that project - - Ignore completed/deleted tasks and non-actionable blocked items - -2. **Pick the next task** (default strategy: `{{strategy|highest-impact}}`): - - Choose one actionable task based on impact, urgency, and clarity - - If two tasks are equivalent, prefer the one that unblocks other work - -3. **Start and execute it**: - - Mark the task as started - - Perform the implementation work needed to complete it - - Keep updates concise and action-focused while working - -4. **Close and record**: - - Mark the task complete when done - - Add a brief annotation summarizing what was delivered - -5. **Auto-progress loop**: - - Immediately return to step 1 and select the next pending task - - Continue until: - - no actionable project tasks remain, or - - `{{max_tasks}}` is reached (if provided), or - - a hard blocker is encountered - -6. **Final report**: - - List completed task IDs/titles - - List any skipped/blocked tasks with reasons - - State what remains pending for the project - -Important behavior requirements: -- Do not ask me to pick a task unless there is a true ambiguity or risk. -- Default to autonomous execution. -- Keep task scope tied to the current project. -- After each completion, automatically move to the next task. diff --git a/prompts/commands/work-on-tasks.md b/prompts/commands/work-on-tasks.md new file mode 100644 index 0000000..7f372a0 --- /dev/null +++ b/prompts/commands/work-on-tasks.md @@ -0,0 +1,56 @@ +# /work-on-tasks + +**Description:** Automatically work through Taskwarrior tasks for the current git project using the `taskwarrior-task-management` skill. The command selects the best pending task, starts it, executes it, completes it, and then auto-progresses to the next task until no actionable tasks remain. + +**Parameters:** +- strategy (optional): How to choose tasks when multiple are available (e.g., "highest-impact", "priority", "due-date", "quick-win") +- max_tasks (optional): Safety limit for how many tasks to process in one run + +**Example usage:** +- `/work-on-tasks` +- `/work-on-tasks highest-impact` +- `/work-on-tasks priority 5` + +--- + +## Prompt + +Use the `taskwarrior-task-management` skill for this entire workflow. + +I want you to automatically execute Taskwarrior work for the **current git project** from start to finish. + +1. **Load project-scoped tasks**: + - Detect the current project from local git context + - List pending Taskwarrior tasks for that project + - Ignore completed/deleted tasks and non-actionable blocked items + +2. **Pick the next task** (default strategy: `{{strategy|highest-impact}}`): + - Choose one actionable task based on impact, urgency, and clarity + - If two tasks are equivalent, prefer the one that unblocks other work + +3. **Start and execute it**: + - Mark the task as started + - Perform the implementation work needed to complete it + - Keep updates concise and action-focused while working + +4. **Close and record**: + - Mark the task complete when done + - Add a brief annotation summarizing what was delivered + +5. **Auto-progress loop**: + - Immediately return to step 1 and select the next pending task + - Continue until: + - no actionable project tasks remain, or + - `{{max_tasks}}` is reached (if provided), or + - a hard blocker is encountered + +6. **Final report**: + - List completed task IDs/titles + - List any skipped/blocked tasks with reasons + - State what remains pending for the project + +Important behavior requirements: +- Do not ask me to pick a task unless there is a true ambiguity or risk. +- Default to autonomous execution. +- Keep task scope tied to the current project. +- After each completion, automatically move to the next task. -- cgit v1.2.3