@mthanhlm/autodev 0.4.3 → 0.4.4

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "autodev",
   "description": "A lean Claude Code workflow system with a single entrypoint, task-based phase execution, and read-only git.",
-  "version": "0.4.3",
+  "version": "0.4.4",
   "author": {
     "name": "mthanhlm"
   },

package/README.md

@@ -7,6 +7,7 @@
 - Installs a standalone Claude Code workflow under `~/.claude/` or `./.claude/`
 - Keeps project state in `.autodev/`
 - Uses `/autodev` as the main command
+- Adds `/autodev-auto` as the explicit opt-in continuous mode
 - Organizes work as `project -> track -> phase -> tasks`
 - Starts new projects and new tracks with a short discovery pass so requirements are based on the user's actual goal
 - Resolves `.autodev/` state from the repo root even when Claude is started in a nested subdirectory
@@ -14,6 +15,7 @@
 - Runs a multi-lens review pass, using foreground review agents when the environment supports them
 - Can auto-format edited code after Claude writes files when a local formatter is available
 - Ships manual commands when you want direct control:
+  - `/autodev-auto`
   - `/autodev-help`
   - `/autodev-new-project`
   - `/autodev-explore-codebase`
@@ -30,6 +32,7 @@
 
 Primary supported usage is the standalone `npx` installer.
 The repo also carries Claude Code plugin metadata for validation and local development, but the supported end-user runtime remains the installed `.claude/` workflow.
+Supported runtime is Claude Code with Node plus `sh`/`bash` available.
 
 ```bash
 npx @mthanhlm/autodev@latest --global
@@ -62,10 +65,18 @@ npx @mthanhlm/autodev@latest --local --uninstall
 
 ## Default Flow
 
+Checkpointed:
+
 ```text
 /autodev
 ```
 
+Continuous until blocked or done:
+
+```text
+/autodev-auto
+```
+
 Typical brownfield route:
 
 ```text
@@ -107,6 +118,7 @@ project -> track -> phase -> tasks
 ### Execution Model
 
 - `/autodev` remains the single entrypoint
+- `/autodev-auto` is the explicit continuous runner and never enables git writes
 - Project and track setup should clarify what the user wants to build, for whom, and what done looks like before writing state files
 - A phase is planned into one phase overview plus multiple task files
 - `/autodev` stops after planning so the user can review the phase before any execution starts
@@ -114,6 +126,7 @@ project -> track -> phase -> tasks
 - Each task is preferably executed by a fresh foreground delegated agent
 - After each task, the delegated agent reports back with files changed, verification, and blockers
 - `/autodev` stops after each completed task and reopens a task review checkpoint before any further execution
+- `/autodev-auto` keeps going until the active track is done or a real stop condition appears, such as missing intent, dependency deadlock, or manual verification
 - If review or verification finds blockers, the same phase stays open and autodev should append remediation task(s) to that phase instead of replacing it or creating a follow-up phase by default
 - No waves by default
 - No automatic parallel execution