@winton979/task-cli 1.1.0 → 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

@@ -57,7 +57,7 @@ task --help
 
 After initialization, Task CLI creates the `.ai/` workspace and installs workflow skills into both `.claude/skills/` and `.codex/skills/`.
 
-Use `task refresh` in existing projects to remove and reinstall only the workflow skills managed by task-cli. It does not delete your `.ai` briefs, archives, or decision log.
+Use `task refresh` in existing projects to remove and reinstall only the workflow skills managed by task-cli. It does not delete your `.ai` briefs, internal archives, or decision log.
 
 Use `task doctor` to check whether the required directories exist, whether managed skills are missing or outdated, and whether the `.gitignore` rules are present.
 
@@ -70,9 +70,11 @@ Use `task doctor` to check whether the required directories exist, whether manag
 ```text
 /task-fast
     ↓
-clarify + brief + implement + validate + archive
+clarify + brief + implement + validate
     ↓
 /task-review
+    or
+/task-cancel
 ```
 
 ### Larger Requirement
@@ -84,9 +86,9 @@ TASK_READY
     ↓
 /task-implement
     ↓
-/task archived
-    ↓
 /task-review
+    or
+/task-cancel
 ```
 
 ### Bug Fix
@@ -98,9 +100,9 @@ BUG_READY
     ↓
 /bug-fix
     ↓
-/bug archived
-    ↓
 /bug-review
+    or
+/bug-cancel
 ```
 
 ---
@@ -113,12 +115,14 @@ BUG_READY
 * task-explore
 * task-implement
 * task-review
+* task-cancel
 
 ### Bug Workflow
 
 * bug-explore
 * bug-fix
 * bug-review
+* bug-cancel
 
 ### Other
 
@@ -155,27 +159,56 @@ Instead of maintaining large specifications, it focuses on:
 
 1. Clarifying requirements before coding
 2. Capturing execution context in concise briefs
-3. Executing with validation and lightweight archiving
+3. Executing with validation while archiving automatically in the background
 4. Reviewing work against acceptance criteria
 5. Keeping a lightweight decision history
 
 The goal is to improve quality without slowing down iteration speed.
 
+## Compared with OpenSpec-Style Workflows
+
+Task CLI is designed as a lightweight alternative to heavier spec-driven systems such as OpenSpec.
+
+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.
+
+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.
+
+Task CLI takes a narrower and more pragmatic approach:
+
+* 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.
 
-## Can This Be Simpler?
+## Strengths and Tradeoffs
 
-Yes. The main simplification is to collapse the old 4-step paths:
+Task CLI is optimized for execution speed and sustained adoption rather than full process coverage.
 
-* `task-explore` now includes brief generation.
-* `bug-explore` now includes bug brief generation.
-* `task-implement` and `bug-fix` now validate and archive the brief when the work is complete.
+Strengths:
 
-That leaves these practical flows:
+* 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
 
-* Explore only: `/task-explore` or `/bug-explore`
-* Execute and archive: `/task-implement` or `/bug-fix`
-* Review: `/task-review` or `/bug-review`
-* One-shot small work: `/task-fast`
+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
 
@@ -188,7 +221,7 @@ 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.
@@ -199,5 +232,9 @@ Before refreshing, you can inspect the current setup with:
 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.0",
+  "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

@@ -14,10 +14,10 @@ const GITIGNORE_BLOCK = [
 const SKILLS = {
   'task-fast': {
     name: 'task-fast',
-    description: 'Fast path for small requirements. Clarify quickly, create the brief, implement, verify, and archive.',
+    description: 'Fast path for small requirements. Clarify quickly, create the brief, implement, and verify. Archive automatically on completion.',
     content: `---
 name: task-fast
-description: Fast path for small requirements. Clarify quickly, create the brief, implement, verify, and archive.
+description: Fast path for small requirements. Clarify quickly, create the brief, implement, and verify. Archive automatically on completion.
 user-invocable: true
 ---
 
@@ -35,7 +35,7 @@ Workflow
 3. Show the brief before coding.
 4. If the user does not object, implement immediately.
 5. Verify the result against the acceptance criteria.
-6. Move the brief to:
+6. Archive the brief automatically by moving it to:
 
 .ai/tasks/archive/YYYY-MM-DD-task-name.md
 
@@ -138,10 +138,10 @@ TASK_READY
 
   'task-implement': {
     name: 'task-implement',
-    description: 'Implement the latest active task brief, validate it, and archive it when complete.',
+    description: 'Implement the latest active task brief and validate it. Archive automatically when complete.',
     content: `---
 name: task-implement
-description: Implement the latest active task brief, validate it, and archive it when complete.
+description: Implement the latest active task brief and validate it. Archive automatically when complete.
 user-invocable: true
 ---
 
@@ -158,7 +158,7 @@ Rules
 5. Avoid unnecessary refactoring.
 6. State assumptions explicitly.
 7. Validate the result before stopping.
-8. If the work is complete, move the brief to .ai/tasks/archive/.
+8. If the work is complete, archive the brief automatically by moving it to .ai/tasks/archive/.
 
 Output
 
@@ -174,18 +174,15 @@ Files modified.
 
 How acceptance criteria were satisfied.
 
-## Archive
-
-Whether the brief was archived.
 `,
   },
 
   'task-review': {
     name: 'task-review',
-    description: 'Review the latest task implementation against the active or archived task brief.',
+    description: 'Review the latest task implementation against the corresponding task brief.',
     content: `---
 name: task-review
-description: Review the latest task implementation against the active or archived task brief.
+description: Review the latest task implementation against the corresponding task brief.
 user-invocable: true
 ---
 
@@ -228,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.',
@@ -294,10 +321,10 @@ BUG_READY
 
   'bug-fix': {
     name: 'bug-fix',
-    description: 'Fix the latest active bug brief, validate the result, and archive the brief when complete.',
+    description: 'Fix the latest active bug brief and validate the result. Archive automatically when complete.',
     content: `---
 name: bug-fix
-description: Fix the latest active bug brief, validate the result, and archive the brief when complete.
+description: Fix the latest active bug brief and validate the result. Archive automatically when complete.
 user-invocable: true
 ---
 
@@ -314,7 +341,7 @@ Rules
 5. Preserve existing behavior.
 6. Explain reasoning.
 7. Validate the fix before stopping.
-8. If the bug is fixed, move the brief to .ai/bugs/archive/.
+8. If the bug is fixed, archive the brief automatically by moving it to .ai/bugs/archive/.
 
 Output
 
@@ -330,18 +357,15 @@ Changes made.
 
 Verification performed.
 
-## Archive
-
-Whether the brief was archived.
 `,
   },
 
   'bug-review': {
     name: 'bug-review',
-    description: 'Review the latest bug fix against the active or archived bug brief.',
+    description: 'Review the latest bug fix against the corresponding bug brief.',
     content: `---
 name: bug-review
-description: Review the latest bug fix against the active or archived bug brief.
+description: Review the latest bug fix against the corresponding bug brief.
 user-invocable: true
 ---
 
@@ -378,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.',
@@ -539,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`);
 }
 
@@ -573,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`);
 }