@mthanhlm/autodev 0.4.4 → 0.5.0

package/autodev/templates/project-state.md

@@ -1,15 +0,0 @@
-# Project State
-
-Project Type: [greenfield or brownfield]
-Active Track: [slug]
-Current Step: initialized
-Current Task: none
-Current Task Status: idle
-Status: active
-Run Mode: checkpointed
-Auto Retry Count: 0
-Next Command: /autodev
-Last Updated: [ISO timestamp]
-
-## Notes
-- Project initialized.

package/autodev/templates/project.md

@@ -1,24 +0,0 @@
-# Project
-
-## One-Line Summary
-[Describe the product in one sentence.]
-
-## Project Type
-[greenfield or brownfield]
-
-## Problem
-[What pain are you solving?]
-
-## Users
-[Who is this for?]
-
-## Success Criteria
-- [Primary outcome]
-- [Primary quality bar]
-
-## Constraints
-- [Technical constraints]
-- [Business or time constraints]
-
-## Non-Goals
-- [Out of scope]

package/autodev/templates/requirements.md

@@ -1,14 +0,0 @@
-# Requirements
-
-Track: [Name]
-
-## Must Have
-1. REQ-01: [Requirement]
-   Acceptance:
-   - [Observable outcome]
-
-## Nice to Have
-1. NICE-01: [Optional enhancement]
-
-## Non-Goals
-- [Explicitly excluded work]

package/autodev/templates/review.md

@@ -1,27 +0,0 @@
-# Phase [N] Review: [Name]
-
-Status: pending
-
-## Code Quality
-- [Finding or "no blocking findings"]
-
-## Security
-- [Finding or "no blocking findings"]
-
-## Integration And Regression
-- [Finding or "no blocking findings"]
-
-## Product Polish And AI-Look
-- [Finding or "no blocking findings"]
-
-## Blockers
-- [Blocker or "none"]
-
-## Strengths
-- [What looks solid]
-
-## Recommendation
-- [Return to execution or continue to verification]
-
-## Remediation Direction
-- [If blocked, append fix task(s) to the same phase and preserve completed task history]

package/autodev/templates/roadmap.md

@@ -1,17 +0,0 @@
-# Track Roadmap
-
-## Phase 1 [feature]: [Name]
-Status: pending
-Goal: [What this phase achieves]
-Deliverables:
-- [Deliverable]
-Risks:
-- [Risk]
-
-## Phase 2 [feature]: [Name]
-Status: pending
-Goal: [What this phase achieves]
-Deliverables:
-- [Deliverable]
-Risks:
-- [Risk]

package/autodev/templates/state.md

@@ -1,15 +0,0 @@
-# Project State
-
-Project Type: [greenfield or brownfield]
-Active Track: [slug]
-Current Step: initialized
-Current Task: none
-Current Task Status: idle
-Status: active
-Run Mode: checkpointed
-Auto Retry Count: 0
-Next Command: /autodev
-Last Updated: [ISO timestamp]
-
-## Notes
-- Project initialized.

package/autodev/templates/summary.md

@@ -1,22 +0,0 @@
-# Phase [N] Summary: [Name]
-
-Type: [feature|bugfix|refactor|research|polish]
-
-## Tasks Completed
-- Task 01 - [Outcome]
-- Task 02 - [Outcome]
-
-## Phase Outcome
-- [What shipped]
-
-## Files Changed
-- [path]
-
-## Verification
-- [Command and result]
-
-## Remaining Risks
-- [Known gap]
-
-## Next Step
-- Run `/autodev`

package/autodev/templates/task-summary.md

@@ -1,18 +0,0 @@
-# Task [NN] Summary: [Name]
-
-Status: done
-
-## Completed
-- [What changed]
-
-## Files Changed
-- [path]
-
-## Verification
-- [Command and result]
-
-## Risks Or Follow-Up
-- [Risk or none]
-
-## Recommended Next Step
-- Return to `/autodev`

package/autodev/templates/task.md

@@ -1,23 +0,0 @@
-# Task [NN]: [Name]
-
-Status: pending
-Depends On: none
-
-## Goal
-[What this task accomplishes]
-
-## Why This Task Exists
-- [Why this should be a separate unit]
-
-## Files Likely To Change
-- [path]
-
-## Implementation Notes
-- [Concrete implementation guidance]
-
-## Verification
-- [Command]
-- [Manual check]
-
-## Done Looks Like
-- [Observable completion signal]

package/autodev/templates/track-state.md

@@ -1,16 +0,0 @@
-# Track State
-
-Track: [Name]
-Current Phase: 1
-Current Phase Type: [feature]
-Current Step: planning
-Current Task: none
-Current Task Status: idle
-Status: active
-Run Mode: checkpointed
-Auto Retry Count: 0
-Next Command: /autodev
-Last Updated: [ISO timestamp]
-
-## Notes
-- Track ready.

package/autodev/templates/track.md

@@ -1,24 +0,0 @@
-# Track: [Name]
-
-Type: [feature|bugfix|refactor|research|polish]
-Status: active
-
-## Why This Track
-[Why this work matters right now.]
-
-## Outcome
-[What changes for the user or operator when this track is done.]
-
-## Success Signals
-- [Observable user or operator outcome]
-- [Verification or quality bar]
-
-## Scope Boundaries
-- [What is in scope]
-- [What is explicitly out of scope]
-
-## Dependencies
-- [Team, system, or technical dependency]
-
-## Existing Code Notes
-- [Important brownfield context or leave none]

package/autodev/templates/uat.md

@@ -1,18 +0,0 @@
-# Phase [N] UAT: [Name]
-
-Status: pending
-
-## Test Cases
-- [ ] [Behavior to verify]
-
-## Results
-- [Pass or fail notes]
-
-## Bugs Or Follow-Up
-- [Issue or none]
-
-## Fix Return
-- [Only add when verification fails]
-
-## Recommended Next Step
-- `/autodev`

package/autodev/workflows/autodev-auto.md

@@ -1,62 +0,0 @@
-<purpose>
-Use `/autodev-auto` as the explicit opt-in continuous entrypoint. Route automatically, keep git read-only, and continue until the track is done or a real stop condition requires the user.
-</purpose>
-
-<rules>
-- `/autodev-auto` is opt-in. `/autodev` remains the safer checkpointed default.
-- Never run git write commands.
-- Never use background execution or waves.
-- Use `--auto` when reading autodev router/init/progress payloads.
-- Skip checkpoint-only review stops when the next step is mechanically clear.
-- Stop immediately when `pause_reason` is one of:
-  - `missing_intent`
-  - `track_selection`
-  - `dependency_deadlock`
-  - `needs_manual_verification`
-  - `cleanup_confirmation`
-  - `auto_retry_limit`
-- Review or verification blockers should stay in the same phase. Append remediation work to that phase instead of creating a replacement phase.
-</rules>
-
-<process>
-1. Run:
-
-```bash
-AUTODEV_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}"
-node "$AUTODEV_ROOT/autodev/bin/autodev-tools.cjs" status --auto
-```
-
-2. Inspect `route.kind`, `route.run_mode`, `route.auto_continuable`, `route.pause_reason`, and the active track data.
-
-3. Handle stop conditions first:
-   - If `route.kind` is `init_project` and the current prompt still does not clearly define the project and first track, stop for `missing_intent`.
-   - If `route.kind` is `init_project` but the current prompt already gives clear project and track intent, treat that pause as resolved and continue into new-project.
-   - If `route.pause_reason` is `track_selection`, stop and ask the user which track to continue or whether to create a new one.
-   - If `route.pause_reason` is `dependency_deadlock`, stop and tell the user the current phase plan must be repaired before more auto execution can continue.
-   - If `route.pause_reason` is `auto_retry_limit`, stop and tell the user the same phase has already auto-replanned twice.
-   - If `route.pause_reason` is `cleanup_confirmation`, stop and require the user to start cleanup explicitly.
-
-4. Route as follows:
-   - `init_project`: load and perform the new-project workflow in auto mode.
-   - `explore_codebase`: load and perform the explore-codebase workflow in auto mode.
-   - `plan_phase`: load and perform the plan-phase workflow in auto mode.
-   - `execute_phase`: load and perform the execute-phase workflow in auto mode.
-   - `review_phase`: load and perform the review-phase workflow in auto mode.
-   - `verify_phase`: load and perform the verify-work workflow in auto mode.
-
-5. Do not load `review-plan` or `review-task` in auto mode. The router already skips those checkpoint-only stops when it is safe to continue.
-
-6. After each completed routed step, re-run the auto status command in the same turn and continue if the next route is still auto-continuable.
-
-7. Keep both project-level and track-level state aligned after every step:
-   - `Run Mode: auto`
-   - `Next Command: /autodev-auto`
-   - `Auto Retry Count: 0` after a clean plan or successful review/verification
-   - increment `Auto Retry Count` only when auto mode reopens the same phase after review or verification blockers
-
-8. End only when the track is complete or a real pause reason remains. Report:
-   - what step just completed
-   - why execution stopped or completed
-   - `/autodev-auto` as the default next command when more auto work remains
-   - `/autodev` only as the manual fallback
-</process>

package/autodev/workflows/autodev.md

@@ -1,83 +0,0 @@
-<purpose>
-Use `/autodev` as the single entrypoint for the normal workflow. Route automatically, keep git read-only, and move the project forward in the same turn whenever possible.
-</purpose>
-
-<rules>
-- Prefer `/autodev` over telling the user to run a different command manually.
-- `/autodev` is the checkpointed mode. Use `/autodev-auto` only when the user explicitly asked for continuous execution.
-- Manual commands remain valid escape hatches. Mention them only as shortcuts.
-- Keep the model `project -> track -> phase -> tasks`.
-- Brownfield repositories should be mapped before detailed phase planning.
-- Never run git write commands.
-- Keep router context small. Do not preload workflow files that are not selected by the current route.
-</rules>
-
-<process>
-1. Run:
-
-```bash
-AUTODEV_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}"
-node "$AUTODEV_ROOT/autodev/bin/autodev-tools.cjs" status
-```
-
-2. Inspect the returned `route.kind`, `project_type`, `tracks`, and active track data.
-
-3. Route as follows:
-   - `init_project`: load and perform the new-project workflow.
-   - `explore_codebase`: load and perform the explore-codebase workflow.
-   - `plan_phase`: load and perform the plan-phase workflow.
-   - `plan_review`: load and perform the review-plan workflow so the user can review the phase plan before any execution starts.
-   - `execute_phase`: load and perform the execute-phase workflow, which should advance one task-sized unit in the current phase session by trying a fresh foreground agent first and falling back cleanly when agent delegation is unavailable.
-   - `task_review`: load and perform the review-task workflow so the user can review one completed task before any further execution starts.
-   - `review_phase`: load and perform the review-phase workflow.
-   - `verify_phase`: load and perform the verify-work workflow.
-
-4. Read only the workflow file needed for the selected route. Do not load the others "just in case".
-
-5. Do not stop after identifying a brownfield codebase route. If the route is `explore_codebase`, perform the exploration as part of the same `/autodev` run instead of telling the user to switch commands.
-
-6. If the route is `track_select` or `track_setup`, handle it directly:
-   - If tracks exist, ask whether to continue one of them or create a new track.
-   - When creating or repairing a track, do a short track-discovery pass before writing files.
-   - Ask for:
-     - the initiative name
-     - what the user wants to ship or change in this track
-     - what done looks like
-     - scope boundaries and explicit non-goals
-     - dependencies or constraints only if they affect planning
-   - If the request is vague, summarize the understanding in a few bullets and resolve ambiguity before writing.
-   - If no tracks exist, do not jump straight to phase types before the track goal is clear.
-   - Create or repair:
-     - `.autodev/ACTIVE_TRACK`
-     - `.autodev/tracks/<slug>/TRACK.md`
-     - `.autodev/tracks/<slug>/REQUIREMENTS.md`
-     - `.autodev/tracks/<slug>/ROADMAP.md`
-     - `.autodev/tracks/<slug>/STATE.md`
-   - Fill the track and requirements docs from the clarified intent, not generic placeholders.
-   - Use a lowercase hyphenated slug.
-   - Use roadmap headings in this format:
-
-```text
-## Phase N [type]: Name
-```
-
-   - After track setup, continue in the same turn by re-running the route logic mentally and executing the next step.
-
-7. If the route is `track_complete`, ask whether the user wants to:
-   - start a new track
-   - run cleanup
-   - stop here
-
-8. When the user chooses a new track at step 7, create it immediately and continue routing in the same turn.
-
-9. Every time you finish a routed step, keep both project-level and track-level state aligned. Default the state files to:
-   - `Run Mode: checkpointed`
-   - `Auto Retry Count: 0` unless a blocked phase is being actively recovered
-   - `Next Command: /autodev`
-
-10. End with:
-   - what step you completed
-   - the current route reason in plain language
-   - `/autodev` as the default next command
-   - the matching manual shortcut only as an optional escape hatch
-</process>

package/autodev/workflows/cleanup.md

@@ -1,51 +0,0 @@
-<purpose>
-Clean or archive autodev state without flags. Prefer preserving useful project context over deleting it.
-</purpose>
-
-<rules>
-- Ask the user which cleanup action to take. Do not rely on flags.
-- Archive before delete when a safe archive path makes sense.
-- Require a second explicit `AskUserQuestion` confirmation before deleting all `.autodev/` state.
-- Never touch repository code outside `.autodev/`.
-</rules>
-
-<process>
-1. Run:
-
-```bash
-AUTODEV_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}"
-node "$AUTODEV_ROOT/autodev/bin/autodev-tools.cjs" cleanup
-```
-
-2. If no `.autodev/` project exists, stop and say there is nothing to clean.
-
-3. Use the `AskUserQuestion` tool for the choice below. Do not ask this in plain assistant text.
-   Ask the user to choose one action:
-   - archive completed phase artifacts only
-   - archive the current track and clear the active selection
-   - delete all `.autodev/` state
-
-4. For `archive completed phase artifacts only`:
-   - create `.autodev/archive/<track-slug>/phases/` if needed
-   - move only verified phase directories there
-   - leave project docs, codebase docs, active track, and unfinished phases in place
-   - update project and track state to `Next Command: /autodev`
-
-5. For `archive the current track and clear the active selection`:
-   - move `.autodev/tracks/<slug>/` to `.autodev/archive/tracks/<slug>-<timestamp>/`
-   - remove `.autodev/ACTIVE_TRACK`
-   - update `.autodev/STATE.md` to `Current Step: track-selection` and `Next Command: /autodev`
-
-6. For `delete all .autodev state`:
-   - use the `AskUserQuestion` tool to ask for one more confirmation
-   - the confirmation should clearly say this removes the entire `.autodev/` directory and cannot be undone by the workflow
-   - offer only:
-     - delete all `.autodev/` state
-     - cancel cleanup
-   - only remove `.autodev/` if the user confirms the delete option
-
-7. End with:
-   - what was archived or deleted
-   - what project context remains
-   - the next recommended route
-</process>

package/autodev/workflows/execute-phase.md

@@ -1,144 +0,0 @@
-<purpose>
-Execute an active-track phase through task-sized delegated runs, keep the main session orchestration-focused, and capture both task summaries and the final phase summary.
-</purpose>
-
-<rules>
-- Never run git write commands.
-- Do not create commits, branches, merges, or worktrees.
-- Stay within the current phase. Do not silently expand scope.
-- Execute one task at a time by default.
-- Do not use waves.
-- Prefer a fresh foreground agent for each task so the phase session does not bloat.
-- If agent delegation is available in this environment, delegate task implementation.
-- If a delegation attempt fails with an environment limitation like `specialized agents aren't available`, treat agent delegation as unavailable for this run and continue cleanly.
-- The main phase session should remain orchestration-focused whenever delegation works.
-- The main phase session may update `.autodev/` state and aggregate phase artifacts.
-- Do not run autodev subagents as background tasks.
-- In `/autodev-auto`, keep executing ready tasks in the same phase until the phase is complete or a real blocker appears.
-</rules>
-
-<process>
-1. Run:
-
-```bash
-AUTODEV_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}"
-node "$AUTODEV_ROOT/autodev/bin/autodev-tools.cjs" init execute-phase "$ARGUMENTS"
-```
-
-If this run came from `/autodev-auto`, append `--auto` to the same command.
-
-2. If no phase is found or the plan file is missing, stop and direct the user to `/autodev-plan-phase`.
-
-3. Read:
-   - `.autodev/STATE.md`
-   - `.autodev/tracks/<active-track>/STATE.md`
-   - `.autodev/codebase/summary.md` if it exists
-   - the target `NN-PLAN.md`
-   - all `TASK-*.md`
-   - all existing `TASK-*-SUMMARY.md`
-
-4. If the phase has no `TASK-*.md` files:
-   - create `TASK-01.md` as a compatibility bridge from the current phase plan
-   - keep it narrow and explicit
-   - then continue
-
-5. Determine the next executable task:
-   - prefer the first task without a summary whose dependencies are already done
-   - if no executable task remains and all task summaries exist, move to phase aggregation
-   - if `dependency_deadlock` is true, stop before execution, set both state files to `Current Step: planning`, set `Current Task: none`, set `Current Task Status: blocked_dependencies`, keep `Run Mode` aligned to the current command, keep `Next Command` aligned to the current command, and ask the user how to repair the plan
-
-6. Before running a task, show the user:
-   - task id and title
-   - likely files to touch
-   - verification plan
-   - any dependency note
-
-7. If agent delegation is available, explicitly call the `Agent` tool and select the installed task-worker subagent for the selected task.
-   Use:
-   - `autodev-task-worker` when autodev is installed into `.claude/`
-   - `autodev:autodev-task-worker` only when this workflow is being run directly from a plugin directory
-
-   Run it in the foreground as part of the current workflow step.
-
-   Tell the subagent:
-   - phase path
-   - task path
-   - summary path to write
-   - required context files to read first
-   - that it owns the task implementation and the task summary
-   - that the main session should stay orchestration-focused
-   - to return a concise outcome only
-
-8. If worker delegation is unavailable, do not stop on the raw platform message.
-   Treat messages like `specialized agents aren't available` as a capability limitation, then:
-   - tell the user plainly that delegated-agent execution is unavailable in this environment
-   - continue with the same task in the current session
-   - keep the same task boundaries
-   - still write the task summary before stopping
-
-9. After the delegated agent returns, or after the current-session fallback completes:
-   - confirm `TASK-NN-SUMMARY.md` exists
-   - inspect whether the task is done or blocked
-   - report the result to the user
-
-10. If more tasks remain in checkpointed mode:
-   - update project and track state to:
-     - `Current Step: task_review`
-     - `Current Task: <current-task>`
-     - `Current Task Status: complete`
-     - `Run Mode: checkpointed`
-     - `Next Command: /autodev`
-   - stop after this task
-   - end by telling the user `/autodev` will open the task review checkpoint before any next-task execution
-
-11. If more tasks remain in auto mode:
-   - update project and track state to:
-     - `Current Step: execution`
-     - `Current Task: <next-ready-task>`
-     - `Current Task Status: ready`
-     - `Run Mode: auto`
-     - `Next Command: /autodev-auto`
-   - continue to the next ready task in the same run
-   - stop only if a new blocker appears
-12. If all tasks are done:
-   - write or update `NN-SUMMARY.md` from the template with:
-     - completed tasks
-     - aggregate files changed
-     - overall verification results
-     - remaining risks
-     - next step
-
-13. Update the active track `STATE.md` so it points to:
-   - `Current Phase: N`
-   - `Current Phase Type: <type>`
-   - `Current Step: task_review` in checkpointed mode, or `Current Step: review` in auto mode
-   - `Current Task: <current-task>`
-   - `Current Task Status: complete`
-   - `Run Mode: checkpointed` for `/autodev`, or `Run Mode: auto` for `/autodev-auto`
-   - `Next Command: /autodev` for checkpointed mode, or `/autodev-auto` for auto mode
-   - current ISO timestamp
-
-14. Update `.autodev/STATE.md` so it points to:
-   - `Active Track: <slug>`
-   - `Current Step: task_review` in checkpointed mode, or `Current Step: review` in auto mode
-   - `Current Task: <current-task>`
-   - `Current Task Status: complete`
-   - `Run Mode: checkpointed` for `/autodev`, or `Run Mode: auto` for `/autodev-auto`
-   - `Next Command: /autodev` for checkpointed mode, or `/autodev-auto` for auto mode
-   - current ISO timestamp
-
-15. If the current task is blocked or incomplete:
-   - say so clearly in the task summary
-   - set both state files to `Current Step: planning`
-   - set `Current Task: <same-task>`
-   - set `Current Task Status: blocked`
-   - keep `Run Mode` aligned to the current command
-   - keep `Next Command` aligned to the current command
-   - tell the user the phase should be revised before more execution
-
-16. End with a short outcome summary and the next recommended command.
-   - In checkpointed mode, never execute a second task in the same run.
-   - In checkpointed mode, if all tasks are now done, say `/autodev` will open the phase-review checkpoint next.
-   - In checkpointed mode, otherwise say `/autodev` will open the task-review checkpoint for the completed task.
-   - In auto mode, keep going until the phase completes or a real blocker stops execution.
-</process>

package/autodev/workflows/explore-codebase.md

@@ -1,70 +0,0 @@
-<purpose>
-Map a brownfield repository quickly and produce a usable codebase brief without drifting into over-analysis.
-</purpose>
-
-<rules>
-- The main `/autodev` session owns this workflow and the final synthesis.
-- Specialized codebase agents are optional implementation helpers, not a separate user-facing mode.
-- Prefer a small set of foreground codebase agents, run one at a time, only when agent delegation is clearly available.
-- Give each agent a disjoint write target.
-- If agent delegation is unavailable or unclear, continue inline without surfacing platform confusion.
-- Use read-only investigation only. No git writes.
-- Focus on information that will improve planning and execution for the active track.
-</rules>
-
-<process>
-1. Run:
-
-```bash
-AUTODEV_ROOT="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude}"
-node "$AUTODEV_ROOT/autodev/bin/autodev-tools.cjs" init explore-codebase
-```
-
-If this run came from `/autodev-auto`, append `--auto` to the same command.
-
-2. If no project exists, stop and tell the user to use `/autodev` or `/autodev-new-project`.
-
-3. Read:
-   - `.autodev/PROJECT.md`
-   - `.autodev/STATE.md`
-   - `.autodev/ACTIVE_TRACK`
-   - the active track docs if they exist
-   - representative repo files needed to orient the exploration
-
-4. Do a small amount of direct repo reading first so the current session understands the workspace before deciding whether helper agents are useful.
-
-5. If agent delegation is clearly available, explicitly call the `Agent` tool for these subagents, one at a time in the foreground, with owned outputs:
-   - `autodev-codebase-structure` for standalone installs, or `autodev:autodev-codebase-structure` in direct plugin runs, owns `.autodev/codebase/structure.md`
-   - `autodev-codebase-domain` for standalone installs, or `autodev:autodev-codebase-domain` in direct plugin runs, owns `.autodev/codebase/domain.md`
-   - `autodev-codebase-runtime` for standalone installs, or `autodev:autodev-codebase-runtime` in direct plugin runs, owns `.autodev/codebase/runtime.md`
-   - `autodev-codebase-quality` for standalone installs, or `autodev:autodev-codebase-quality` in direct plugin runs, owns `.autodev/codebase/quality.md`
-
-6. Tell each agent:
-   - it is not alone in the codebase
-   - it must not overwrite another agent's file
-   - it should stay read-only except for its owned output file
-   - it should prefer concise, decision-useful findings over exhaustive listing
-
-7. If agent delegation is unavailable, do not stop on the raw platform message.
-   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.
-
-8. After the four agent outputs are written, or after the current-session fallback writes them, review them and synthesize `.autodev/codebase/summary.md` with:
-   - architectural overview
-   - major constraints
-   - current track implications
-   - hotspots and likely safe change points
-   - the next planning risks to watch
-
-9. Update `.autodev/STATE.md` and the active track `STATE.md` so they reflect:
-   - `Current Step: planning`
-   - `Run Mode: checkpointed` for `/autodev`, or `Run Mode: auto` for `/autodev-auto`
-   - `Auto Retry Count: 0`
-   - `Next Command: /autodev` for checkpointed mode, or `/autodev-auto` for auto mode
-   - refreshed ISO timestamp
-
-10. End with:
-   - the biggest structural insight
-   - the biggest risk
-   - `/autodev` as the next command
-   - `/autodev-plan-phase <n>` only as the optional manual shortcut when obvious
-</process>