@mthanhlm/autodev 0.3.1 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -8,8 +8,8 @@
8
8
  - Keeps project state in `.autodev/`
9
9
  - Uses `/autodev` as the main command
10
10
  - Organizes work as `project -> track -> phase -> tasks`
11
- - Maps brownfield repos with four parallel codebase agents
12
- - Runs a four-agent review pass after execution
11
+ - Maps brownfield repos with parallel codebase agents when the environment supports them
12
+ - Runs a multi-lens review pass, using parallel review agents when the environment supports them
13
13
  - Ships manual commands when you want direct control:
14
14
  - `/autodev-help`
15
15
  - `/autodev-new-project`
@@ -93,10 +93,11 @@ project -> track -> phase -> tasks
93
93
  - `/autodev` remains the single entrypoint
94
94
  - A phase is planned into one phase overview plus multiple task files
95
95
  - The phase keeps one user-facing orchestration session
96
- - Each task is executed by a fresh worker agent in the background
96
+ - Each task is preferably executed by a fresh worker agent in the background
97
97
  - After each task, the worker reports back with files changed, verification, and blockers
98
98
  - No waves by default
99
99
  - No parallel execution unless the user explicitly asks for it later
100
+ - If specialized agents are unavailable in the current Claude Code environment, the workflow falls back cleanly to current-session execution instead of stopping on platform wording
100
101
 
101
102
  ## Git Policy
102
103
 
@@ -13,6 +13,7 @@ Execute one assigned task inside the current phase and report back to the main p
13
13
 
14
14
  - You are not alone in the codebase.
15
15
  - Stay inside the assigned task scope.
16
+ - The main phase session should stay orchestration-focused while you own this task.
16
17
  - Do not run git write commands.
17
18
  - Do not silently expand into the next task.
18
19
  - If blocked, say so clearly and write the blocker into the task summary.
@@ -21,6 +22,7 @@ Execute one assigned task inside the current phase and report back to the main p
21
22
 
22
23
  - Update the repository code for the assigned task only.
23
24
  - Write only the assigned `TASK-NN-SUMMARY.md`.
25
+ - Do not edit project-level or track-level state files.
24
26
  - Return a concise report:
25
27
  - task id
26
28
  - files changed
@@ -23,7 +23,7 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" status
23
23
  - `init_project`: perform the new-project workflow.
24
24
  - `explore_codebase`: perform the explore-codebase workflow.
25
25
  - `plan_phase`: perform the plan-phase workflow.
26
- - `execute_phase`: perform the execute-phase workflow, which should advance one task-sized unit in the current phase session.
26
+ - `execute_phase`: perform the execute-phase workflow, which should advance one task-sized unit in the current phase session by trying a fresh task worker first and falling back cleanly when delegation is unavailable.
27
27
  - `review_phase`: perform the review-phase workflow.
28
28
  - `verify_phase`: perform the verify-work workflow.
29
29
 
@@ -8,7 +8,11 @@ Execute an active-track phase through task-sized worker runs, keep the main sess
8
8
  - Stay within the current phase. Do not silently expand scope.
9
9
  - Execute one task at a time by default.
10
10
  - Do not use waves.
11
- - Use a fresh background worker for each task so the phase session does not bloat.
11
+ - Prefer a fresh background worker for each task so the phase session does not bloat.
12
+ - If the `Task` tool is available and specialized agents are supported in this environment, delegate task implementation.
13
+ - If a delegation attempt fails with an environment limitation like `specialized agents aren't available`, treat delegation as unavailable for this run and continue cleanly.
14
+ - The main phase session should remain orchestration-focused whenever delegation works.
15
+ - The main phase session may update `.autodev/` state and aggregate phase artifacts.
12
16
  </rules>
13
17
 
14
18
  <process>
@@ -44,20 +48,29 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init execute-phase "$ARGUMENT
44
48
  - verification plan
45
49
  - any dependency note
46
50
 
47
- 7. Spawn one fresh background worker using `autodev-task-worker` for the selected task.
51
+ 7. If the `Task` tool is available, first try to spawn one fresh background worker using `autodev-task-worker` for the selected task.
48
52
  Tell it:
49
53
  - phase path
50
54
  - task path
51
55
  - summary path to write
52
56
  - required context files to read first
57
+ - that it owns the task implementation and the task summary
58
+ - that the main session should stay orchestration-focused
53
59
  - to return a concise outcome only
54
60
 
55
- 8. After the worker returns:
61
+ 8. If worker delegation is unavailable, do not stop on the raw platform message.
62
+ Treat messages like `specialized agents aren't available` as a capability limitation, then:
63
+ - tell the user plainly that background task workers are unavailable in this environment
64
+ - continue with the same task in the current session
65
+ - keep the same task boundaries
66
+ - still write the task summary before moving on
67
+
68
+ 9. After the worker returns, or after the current-session fallback completes:
56
69
  - confirm `TASK-NN-SUMMARY.md` exists
57
70
  - inspect whether the task is done or blocked
58
71
  - report the result to the user
59
72
 
60
- 9. If more tasks remain:
73
+ 10. If more tasks remain:
61
74
  - update project and track state to:
62
75
  - `Current Step: execution`
63
76
  - `Current Task: <next-task>`
@@ -65,7 +78,7 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init execute-phase "$ARGUMENT
65
78
  - `Next Command: /autodev`
66
79
  - end by telling the user `/autodev` will continue with the next task
67
80
 
68
- 10. If all tasks are done:
81
+ 11. If all tasks are done:
69
82
  - write or update `NN-SUMMARY.md` from the template with:
70
83
  - completed tasks
71
84
  - aggregate files changed
@@ -73,7 +86,7 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init execute-phase "$ARGUMENT
73
86
  - remaining risks
74
87
  - next step
75
88
 
76
- 11. Update the active track `STATE.md` so it points to:
89
+ 12. Update the active track `STATE.md` so it points to:
77
90
  - `Current Phase: N`
78
91
  - `Current Phase Type: <type>`
79
92
  - `Current Step: review`
@@ -82,7 +95,7 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init execute-phase "$ARGUMENT
82
95
  - `Next Command: /autodev`
83
96
  - current ISO timestamp
84
97
 
85
- 12. Update `.autodev/STATE.md` so it points to:
98
+ 13. Update `.autodev/STATE.md` so it points to:
86
99
  - `Active Track: <slug>`
87
100
  - `Current Step: review`
88
101
  - `Current Task: none`
@@ -90,12 +103,12 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init execute-phase "$ARGUMENT
90
103
  - `Next Command: /autodev`
91
104
  - current ISO timestamp
92
105
 
93
- 13. If the current task is blocked or incomplete:
106
+ 14. If the current task is blocked or incomplete:
94
107
  - say so clearly in the task summary
95
108
  - set both state files to `Current Step: execution`
96
109
  - set `Current Task: <same-task>`
97
110
  - set `Current Task Status: blocked`
98
111
  - keep `Next Command: /autodev`
99
112
 
100
- 14. End with a short outcome summary and the next recommended command. Mention that the automatic review bundle is the next routed step only when the whole phase is complete.
113
+ 15. End with a short outcome summary and the next recommended command. Mention that the automatic review bundle is the next routed step only when the whole phase is complete.
101
114
  </process>
@@ -1,9 +1,9 @@
1
1
  <purpose>
2
- Map a brownfield repository quickly and use four parallel agents to produce a usable codebase brief without drifting into over-analysis.
2
+ Map a brownfield repository quickly and produce a usable codebase brief without drifting into over-analysis.
3
3
  </purpose>
4
4
 
5
5
  <rules>
6
- - Always spawn four agents in parallel for this workflow.
6
+ - Prefer four parallel agents for this workflow when specialized agents are available.
7
7
  - Give each agent a disjoint write target.
8
8
  - Use read-only investigation only. No git writes.
9
9
  - Focus on information that will improve planning and execution for the active track.
@@ -25,7 +25,7 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init explore-codebase
25
25
  - the active track docs if they exist
26
26
  - representative repo files needed to orient the exploration
27
27
 
28
- 4. Spawn four parallel agents with these owned outputs:
28
+ 4. If specialized agents are available, spawn four parallel agents with these owned outputs:
29
29
  - `autodev-codebase-structure` owns `.autodev/codebase/structure.md`
30
30
  - `autodev-codebase-domain` owns `.autodev/codebase/domain.md`
31
31
  - `autodev-codebase-runtime` owns `.autodev/codebase/runtime.md`
@@ -37,19 +37,22 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init explore-codebase
37
37
  - it should stay read-only except for its owned output file
38
38
  - it should prefer concise, decision-useful findings over exhaustive listing
39
39
 
40
- 6. After the four agent outputs are written, review them and synthesize `.autodev/codebase/summary.md` with:
40
+ 6. If agent delegation is unavailable, do not stop on the raw platform message.
41
+ Treat messages like `specialized agents aren't available` as an environment limitation, tell the user exploration will continue in the current session, and write the four owned output files directly.
42
+
43
+ 7. After the four agent outputs are written, or after the current-session fallback writes them, review them and synthesize `.autodev/codebase/summary.md` with:
41
44
  - architectural overview
42
45
  - major constraints
43
46
  - current track implications
44
47
  - hotspots and likely safe change points
45
48
  - the next planning risks to watch
46
49
 
47
- 7. Update `.autodev/STATE.md` and the active track `STATE.md` so they reflect:
50
+ 8. Update `.autodev/STATE.md` and the active track `STATE.md` so they reflect:
48
51
  - `Current Step: planning`
49
52
  - `Next Command: /autodev`
50
53
  - refreshed ISO timestamp
51
54
 
52
- 8. End with:
55
+ 9. End with:
53
56
  - the biggest structural insight
54
57
  - the biggest risk
55
58
  - `/autodev` as the next command
@@ -14,13 +14,13 @@ Lean Claude Code workflow. No automatic commits. No branches. No worktrees. Git
14
14
  - `/autodev-new-project`
15
15
  Creates project state in `.autodev/` and the first active track under `.autodev/tracks/<track>/`.
16
16
  - `/autodev-explore-codebase`
17
- Spawns four parallel agents to map a brownfield repo into `.autodev/codebase/`.
17
+ Uses four parallel agents when available to map a brownfield repo into `.autodev/codebase/`.
18
18
  - `/autodev-plan-phase [phase]`
19
19
  Creates or revises one phase plan plus task files in `.autodev/tracks/<track>/phases/NN-type-name/`.
20
20
  - `/autodev-execute-phase [phase]`
21
- Orchestrates one phase task-by-task and writes `TASK-NN-SUMMARY.md` plus the final `NN-SUMMARY.md`.
21
+ Orchestrates one phase task-by-task, preferring a fresh worker per task, and writes `TASK-NN-SUMMARY.md` plus the final `NN-SUMMARY.md`.
22
22
  - `/autodev-review-phase [phase]`
23
- Spawns four review agents for code quality, security, integration, and polish, then writes `NN-REVIEW.md`.
23
+ Uses four review agents when available for code quality, security, integration, and polish, then writes `NN-REVIEW.md`.
24
24
  - `/autodev-verify-work [phase]`
25
25
  Records manual verification in `NN-UAT.md` and captures fix-return gaps when verification fails.
26
26
  - `/autodev-progress`
@@ -3,7 +3,7 @@ Run the automatic review bundle after execution so the user sees code quality, s
3
3
  </purpose>
4
4
 
5
5
  <rules>
6
- - Always spawn four review agents in parallel.
6
+ - Prefer four review agents in parallel when specialized agents are available.
7
7
  - Review findings should be concrete and evidence-based.
8
8
  - Do not edit repository code in this step unless the user explicitly asks for fixes.
9
9
  - Write one consolidated review artifact for the phase.
@@ -27,7 +27,7 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init review-phase "$ARGUMENTS
27
27
  - `NN-SUMMARY.md`
28
28
  - relevant source files and tests
29
29
 
30
- 4. Spawn four parallel review agents:
30
+ 4. If specialized agents are available, spawn four parallel review agents:
31
31
  - `autodev-review-quality`
32
32
  - `autodev-review-security`
33
33
  - `autodev-review-integration`
@@ -39,22 +39,29 @@ node "$HOME/.claude/autodev/bin/autodev-tools.cjs" init review-phase "$ARGUMENTS
39
39
  - it should focus on clear issues, not generic commentary
40
40
  - it should report severity, evidence, and suggested action
41
41
 
42
- 6. Synthesize the four agent responses into `NN-REVIEW.md` from the template with:
42
+ 6. If agent delegation is unavailable, do not stop on the raw platform message.
43
+ Treat messages like `specialized agents aren't available` as an environment limitation, tell the user review will continue in the current session, and perform the same review pass directly using the four lenses:
44
+ - quality
45
+ - security
46
+ - integration
47
+ - product polish
48
+
49
+ 7. Synthesize the four agent responses, or the current-session four-lens review, into `NN-REVIEW.md` from the template with:
43
50
  - grouped findings
44
51
  - blockers vs non-blockers
45
52
  - what looks solid
46
53
  - a final recommendation
47
54
 
48
- 7. If blockers are found:
55
+ 8. If blockers are found:
49
56
  - set project and track state back to `Current Step: execution`
50
57
  - keep `Next Command: /autodev`
51
58
  - make the recommendation point back to the same phase
52
59
 
53
- 8. If blockers are not found:
60
+ 9. If blockers are not found:
54
61
  - set project and track state to `Current Step: verification`
55
62
  - keep `Next Command: /autodev`
56
63
 
57
- 9. End with a short review result:
64
+ 10. End with a short review result:
58
65
  - ready for verification, or
59
66
  - return to execution
60
67
  - include the manual shortcut command
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: autodev:execute-phase
3
- description: Execute an active-track phase task by task with fresh background workers and no git writes
3
+ description: Execute an active-track phase task by task, preferring fresh background workers with clean fallback when unavailable
4
4
  argument-hint: "[phase-number]"
5
5
  allowed-tools:
6
6
  - Read
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: autodev:explore-codebase
3
- description: Map an existing codebase with four parallel agents and synthesize the result
3
+ description: Map an existing codebase, preferring parallel agents with clean fallback when unavailable
4
4
  allowed-tools:
5
5
  - Read
6
6
  - Write
@@ -12,7 +12,7 @@ allowed-tools:
12
12
  - Task
13
13
  ---
14
14
  <objective>
15
- Explore the current repository, spawn four parallel codebase agents, and write the brownfield map into `.autodev/codebase/`.
15
+ Explore the current repository, use parallel codebase agents when available, and write the brownfield map into `.autodev/codebase/`.
16
16
  </objective>
17
17
 
18
18
  <execution_context>
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: autodev:review-phase
3
- description: Run a four-agent review pass for code quality, security, integration, and product polish
3
+ description: Run a review pass for code quality, security, integration, and product polish, preferring parallel agents when available
4
4
  argument-hint: "[phase-number]"
5
5
  allowed-tools:
6
6
  - Read
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mthanhlm/autodev",
3
- "version": "0.3.1",
3
+ "version": "0.3.2",
4
4
  "description": "A lean Claude Code workflow system with a single entrypoint, task-based phase execution, and read-only git.",
5
5
  "bin": {
6
6
  "autodev": "bin/install.js"