@winton979/task-cli 1.1.1 → 1.2.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 winton979
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -73,6 +73,8 @@ Use `task doctor` to check whether the required directories exist, whether manag
 clarify + brief + implement + validate
     ↓
 /task-review
+    or
+/task-cancel
 ```
 
 ### Larger Requirement
@@ -85,6 +87,8 @@ TASK_READY
 /task-implement
     ↓
 /task-review
+    or
+/task-cancel
 ```
 
 ### Bug Fix
@@ -97,6 +101,8 @@ BUG_READY
 /bug-fix
     ↓
 /bug-review
+    or
+/bug-cancel
 ```
 
 ---
@@ -109,12 +115,14 @@ BUG_READY
 * task-explore
 * task-implement
 * task-review
+* task-cancel
 
 ### Bug Workflow
 
 * bug-explore
 * bug-fix
 * bug-review
+* bug-cancel
 
 ### Other
 
@@ -157,21 +165,50 @@ Instead of maintaining large specifications, it focuses on:
 
 The goal is to improve quality without slowing down iteration speed.
 
+## Compared with OpenSpec-Style Workflows
 
-## Can This Be Simpler?
+Task CLI is designed as a lightweight alternative to heavier spec-driven systems such as OpenSpec.
 
-Yes. The main simplification is to collapse the old 4-step paths:
+Detailed specification workflows can improve alignment, traceability, and consistency. They are often the right choice for large initiatives, cross-team programs, and environments with strong process requirements.
 
-* `task-explore` now includes brief generation.
-* `bug-explore` now includes bug brief generation.
-* `task-implement` and `bug-fix` now validate the work and archive the brief automatically when complete.
+The difficulty is that the same level of ceremony does not always fit day-to-day engineering work. For frequent bug fixes, small features, and fast iteration, the process can become heavier than the change itself. When that happens, maintenance overhead increases, documentation quality starts to drift, and teams gradually stop using the workflow as originally intended.
 
-That leaves these practical flows:
+Task CLI takes a narrower and more pragmatic approach:
 
-* Explore only: `/task-explore` or `/bug-explore`
-* Execute: `/task-implement` or `/bug-fix`
-* Review: `/task-review` or `/bug-review`
-* One-shot small work: `/task-fast`
+* clarify the requirement
+* capture only the minimum useful brief
+* execute against acceptance criteria
+* review the result
+* keep a lightweight decision trail
+
+The goal is not to replace specification systems in every context. It is to provide a workflow that people will actually keep using during day-to-day engineering work.
+
+## Strengths and Tradeoffs
+
+Task CLI is optimized for execution speed and sustained adoption rather than full process coverage.
+
+Strengths:
+
+* much lower process overhead for bugs, small features, and short iterations
+* easier to adopt in mature codebases where engineers already know the product context
+* encourages real usage because the workflow is short enough to sustain
+* keeps enough structure to improve clarity without forcing large documents
+
+Tradeoffs:
+
+* less suitable for large cross-team initiatives that need formal design traceability
+* relies more on engineer judgment and review quality than a full specification process
+* stores less long-form historical context than a dedicated spec repository
+
+## Recommended Workflow Model
+
+Task CLI keeps the user-facing flow short:
+
+* `task-fast`
+* `task-explore -> task-implement -> task-review` or `task-cancel`
+* `bug-explore -> bug-fix -> bug-review` or `bug-cancel`
+
+The `archive/` directories remain as internal storage. They are not separate user steps in the recommended workflow.
 
 ## Upgrading Existing Projects
 
@@ -184,18 +221,20 @@ task refresh
 This will:
 
 * keep `.ai/tasks`, `.ai/bugs`, and `.ai/decisions`
-* remove only these managed skills from `.claude/skills/` and `.codex/skills/`: `task-fast`, `task-explore`, `task-implement`, `task-review`, `bug-explore`, `bug-fix`, `bug-review`, `decision-log`
+* remove only these managed skills from `.claude/skills/` and `.codex/skills/`: `task-fast`, `task-explore`, `task-implement`, `task-review`, `task-cancel`, `bug-explore`, `bug-fix`, `bug-review`, `bug-cancel`, `decision-log`
 * reinstall the latest versions of those skills
 
 This avoids touching unrelated custom skills in the same project.
 
-The `archive/` directories remain as internal storage. They are not separate user steps in the recommended workflow.
-
 Before refreshing, you can inspect the current setup with:
 
 ```bash
 task doctor
 ```
 
+## License
+
+MIT
+
 > Task CLI does not install Grill Me automatically.
 > Users remain free to choose any Grill Me compatible implementation.

package/package.json

@@ -1,7 +1,8 @@
 {
   "name": "@winton979/task-cli",
-  "version": "1.1.1",
+  "version": "1.2.0",
   "description": "Lightweight task workflow CLI for AI-assisted development",
+  "license": "MIT",
   "type": "module",
   "bin": {
     "task": "./bin/task.js"

package/src/cli.js

@@ -26,8 +26,8 @@ Usage:
 
 Recommended flows after init:
   fast: task-fast
-  task: task-explore -> task-implement -> task-review
-  bug:  bug-explore -> bug-fix -> bug-review`);
+  task: task-explore -> task-implement -> task-review | task-cancel
+  bug:  bug-explore -> bug-fix -> bug-review | bug-cancel`);
 }
 
 switch (cmd) {

package/src/init.js

@@ -225,6 +225,36 @@ Anything not fully implemented.
 `,
   },
 
+  'task-cancel': {
+    name: 'task-cancel',
+    description: 'Discard the current task analysis output and implementation changes for this attempt.',
+    content: `---
+name: task-cancel
+description: Discard the current task analysis output and implementation changes for this attempt.
+user-invocable: true
+---
+
+Purpose
+
+Abandon the current task attempt completely.
+
+Rules
+
+1. Target only the current task attempt.
+2. Discard the current task brief and any analysis artifacts created for this attempt.
+3. Discard code changes made for this attempt.
+4. Do not archive the task brief.
+5. Do not keep partial implementation.
+6. Do not preserve temporary conclusions from this attempt as accepted decisions.
+7. Do not touch unrelated historical archives, other active briefs, or user-authored changes outside this attempt.
+8. If the exact changed files are uncertain, stop and ask for confirmation before deleting or reverting anything.
+
+Output
+
+TASK_CANCELLED
+`,
+  },
+
   'bug-explore': {
     name: 'bug-explore',
     description: 'Investigate a bug and generate a fix brief in one step, without writing code.',
@@ -372,6 +402,36 @@ Further improvements.
 `,
   },
 
+  'bug-cancel': {
+    name: 'bug-cancel',
+    description: 'Discard the current bug analysis output and code changes for this attempt.',
+    content: `---
+name: bug-cancel
+description: Discard the current bug analysis output and code changes for this attempt.
+user-invocable: true
+---
+
+Purpose
+
+Abandon the current bug-fix attempt completely.
+
+Rules
+
+1. Target only the current bug-fix attempt.
+2. Discard the current bug brief and any analysis artifacts created for this attempt.
+3. Discard code changes made for this attempt.
+4. Do not archive the bug brief.
+5. Do not keep partial fixes.
+6. Do not preserve temporary conclusions from this attempt as accepted decisions.
+7. Do not touch unrelated historical archives, other active briefs, or user-authored changes outside this attempt.
+8. If the exact changed files are uncertain, stop and ask for confirmation before deleting or reverting anything.
+
+Output
+
+BUG_CANCELLED
+`,
+  },
+
   'decision-log': {
     name: 'decision-log',
     description: 'Record implementation decisions to .ai/decisions/decisions.md. Append-only, max 10 lines per entry.',
@@ -533,8 +593,8 @@ export function init(cwd, { fs, path, log }) {
 
   log.info(`\nTask workflow initialized. Recommended flows:
   fast:  task-fast
-  task:  task-explore -> task-implement -> task-review
-  bug:   bug-explore -> bug-fix -> bug-review
+  task:  task-explore -> task-implement -> task-review | task-cancel
+  bug:   bug-explore -> bug-fix -> bug-review | bug-cancel
   other: decision-log`);
 }
 
@@ -567,8 +627,8 @@ export function refresh(cwd, { fs, path, log }) {
 
   log.info(`\nTask workflow refreshed. Managed skills reinstalled:
   fast:  task-fast
-  task:  task-explore -> task-implement -> task-review
-  bug:   bug-explore -> bug-fix -> bug-review
+  task:  task-explore -> task-implement -> task-review | task-cancel
+  bug:   bug-explore -> bug-fix -> bug-review | bug-cancel
   other: decision-log`);
 }