@winton979/task-cli 1.1.0 → 1.1.1

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,7 +70,7 @@ 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
 ```
@@ -84,8 +84,6 @@ TASK_READY
     ↓
 /task-implement
     ↓
-/task archived
-    ↓
 /task-review
 ```
 
@@ -98,8 +96,6 @@ BUG_READY
     ↓
 /bug-fix
     ↓
-/bug archived
-    ↓
 /bug-review
 ```
 
@@ -155,7 +151,7 @@ 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
 
@@ -168,12 +164,12 @@ Yes. The main simplification is to collapse the old 4-step paths:
 
 * `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.
+* `task-implement` and `bug-fix` now validate the work and archive the brief automatically when complete.
 
 That leaves these practical flows:
 
 * Explore only: `/task-explore` or `/bug-explore`
-* Execute and archive: `/task-implement` or `/bug-fix`
+* Execute: `/task-implement` or `/bug-fix`
 * Review: `/task-review` or `/bug-review`
 * One-shot small work: `/task-fast`
 
@@ -193,6 +189,8 @@ This will:
 
 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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@winton979/task-cli",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Lightweight task workflow CLI for AI-assisted development",
   "type": "module",
   "bin": {

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
 ---
 
@@ -294,10 +291,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 +311,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 +327,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
 ---