@joshski/dust 0.1.39 → 0.1.40

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@joshski/dust",
-  "version": "0.1.39",
+  "version": "0.1.40",
   "description": "Flow state for AI coding agents",
   "type": "module",
   "bin": {
@@ -32,7 +32,7 @@
   "author": "joshski",
   "license": "MIT",
   "scripts": {
-    "build": "bun build lib/cli/run.ts --target node --outfile dist/dust.js && printf '%s\\n%s' '#!/usr/bin/env node' \"$(cat dist/dust.js)\" > dist/dust.js && bun build lib/workflow-tasks.ts --target node --outfile dist/workflow-tasks.js && bunx tsc --project tsconfig.build.json && cp -r lib/templates templates",
+    "build": "bun build lib/cli/run.ts --target node --outfile dist/dust.js && printf '%s\\n%s' '#!/usr/bin/env node' \"$(cat dist/dust.js)\" > dist/dust.js && bun build lib/workflow-tasks.ts --target node --outfile dist/workflow-tasks.js && bunx tsc --project tsconfig.build.json && rm -rf templates && cp -r lib/templates templates",
     "test": "vitest run",
     "test:coverage": "vitest run --coverage",
     "eval": "bun run ./evals/run.ts"

package/templates/agent-new-task.txt

@@ -18,7 +18,6 @@ Use a todo list to track your progress through these steps.
 4. Create a new markdown file in `.dust/tasks/` with a descriptive kebab-case name (e.g., `add-user-authentication.md`)
 5. Add a title as the first line using an H1 heading (e.g., `# Add user authentication`)
 6. Write a comprehensive description starting with an imperative opening sentence (e.g., "Add caching to the API layer." not "This task adds caching."). Include technical details and references to relevant files.
-   - Scope the task as a **vertical slice**: a thin but complete path through the system that can be tested and built upon, rather than an isolated component or layer.
 7. Add a `## Goals` section with links to relevant goals this task supports (e.g., `- [Goal Name](../goals/goal-name.md)`)
 8. Add a `## Blocked By` section listing any tasks that must complete first, or `(none)` if there are no blockers
 9. Add a `## Definition of Done` section with a checklist of completion criteria using `- [ ]` for each item

package/templates/templates/agent-new-task.txt

@@ -1,29 +0,0 @@
-## Adding a New Task
-
-{{#if isClaudeCodeWeb}}Follow these steps to create the task definition, then spawn a sub-agent for implementation.
-
-Use a todo list to track your progress through these steps.
-{{/if}}{{#unless isClaudeCodeWeb}}Follow these steps:
-{{/unless}}
-1. Run `{{bin}} ideas` to see all existing ideas
-2. Determine which ideas (if any) should be:
-   - **Deleted** - if the new task fully covers the idea
-   - **Updated** - if the idea's scope changes as a result of the task
-3. Research thoroughly to ensure the task will be clearly defined:
-   - Explore the codebase to understand existing patterns and relevant files
-   - Identify exactly which files need to change and how
-   - Resolve any ambiguities in the requirements before writing the task
-   - Gather specific technical details (function names, file paths, data structures)
-   - The goal is a task description with minimal ambiguity at implementation time
-4. Create a new markdown file in `.dust/tasks/` with a descriptive kebab-case name (e.g., `add-user-authentication.md`)
-5. Add a title as the first line using an H1 heading (e.g., `# Add user authentication`)
-6. Write a comprehensive description starting with an imperative opening sentence (e.g., "Add caching to the API layer." not "This task adds caching."). Include technical details and references to relevant files.
-7. Add a `## Goals` section with links to relevant goals this task supports (e.g., `- [Goal Name](../goals/goal-name.md)`)
-8. Add a `## Blocked By` section listing any tasks that must complete first, or `(none)` if there are no blockers
-9. Add a `## Definition of Done` section with a checklist of completion criteria using `- [ ]` for each item
-10. Run `{{bin}} lint markdown` to catch any issues with the task format
-11. Create a single atomic commit with a message in the format "Add task: <title>" that includes:
-    - The new task file
-    - Deletion of the idea file that spawned this task (if remaining scope exists, create new ideas for it)
-{{#unless isClaudeCodeWeb}}12. Push your commit to the remote repository
-{{/unless}}{{#if isClaudeCodeWeb}}12. **Start a sub-agent** to implement the task: "Run `{{bin}} implement task` and implement the task in `.dust/tasks/[task-file].md`"{{/if}}