diff options
| author | Paul Buetow <paul@buetow.org> | 2026-03-03 22:30:49 +0200 |
|---|---|---|
| committer | Paul Buetow <paul@buetow.org> | 2026-03-03 22:30:49 +0200 |
| commit | fb4e45fc4e830f1391cb3bae56b0773cf75bc66c (patch) | |
| tree | 7417528ada4ca592497cf21b13cf4415802bc0e5 /prompts/commands | |
| parent | 0b1adf6136aa8866ecfbeab844747b24b9bf566e (diff) | |
more on this
Diffstat (limited to 'prompts/commands')
| -rw-r--r-- | prompts/commands/create-tasks.md | 7 | ||||
| -rw-r--r-- | prompts/commands/work-on-tasks.md (renamed from prompts/commands/start-work-on-tasks.md) | 8 |
2 files changed, 10 insertions, 5 deletions
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: <relative/or/absolute/path/to/plan.md>"`. - 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/work-on-tasks.md index 2099300..7f372a0 100644 --- a/prompts/commands/start-work-on-tasks.md +++ b/prompts/commands/work-on-tasks.md @@ -1,4 +1,4 @@ -# /start-work-on-tasks +# /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. @@ -7,9 +7,9 @@ - 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` +- `/work-on-tasks` +- `/work-on-tasks highest-impact` +- `/work-on-tasks priority 5` --- |