// Query task status and relationships — read-only, no file writes. Use to inspect task inventory, check progress, view dependency graphs, or audit status transition history.
Process Plan panel annotations — triage, cross-impact assessment, and execution. Triggered automatically when annotations (Insert/Delete/Replace/Comment) are submitted from the Plan panel UI.
Autonomous execution loop — single Claude session orchestrates plan/check/exec cycle internally
Cancel a task module — set status to cancelled, stop auto if running, optionally clean up worktree. Use when a task becomes infeasible, is deprioritized, or needs to be abandoned.
Check plan feasibility at key checkpoints — post-plan, mid-execution, post-execution
Execute the implementation plan for a reviewed task module. Triggered after check PASS (from review status) or on NEEDS_FIX continuation (from executing status with fix guidance).
Initialize a new task module in AiTasks/ directory with system files, git branch, and optional worktree. Use when starting a new feature, bug fix, or refactoring task that needs structured lifecycle tracking.
| name | list |
| description | Query task status and relationships — read-only, no file writes. Use to inspect task inventory, check progress, view dependency graphs, or audit status transition history. |
| arguments | [{"name":"task_module","description":"Task module name (optional — omit to list all tasks)","required":false},{"name":"deps","description":"Output dependency relationship graph (Mermaid)","required":false},{"name":"timeline","description":"Output status transition timeline from git history","required":false}] |
Query task status, details, and relationships. Pure read-only — no files written, no status changes, no git commits.
/moonview:list # List all tasks
/moonview:list <task_module> # Single task details
/moonview:list --deps # Dependency graph (all tasks)
/moonview:list --timeline <task_module> # Status transition timeline
Output a summary table of all task modules:
| Column | Source |
|---|---|
| Module | directory name |
| Title | .index.json → title |
| Status | .index.json → status |
| Phase | .index.json → phase (if non-empty) |
| Progress | .index.json → completed_steps |
| Type | .index.json → type |
| Updated | .index.json → updated |
<task_module>)Output all fields from <module>/.index.json plus:
.summary.md content (if exists) — condensed context.target.md first 10 lines — requirements preview--deps)Generate a Mermaid diagram showing all task modules and their depends_on relationships:
graph LR
auth-refactor[auth-refactor<br/>status: review]
api-design[api-design<br/>status: executing]
auth-refactor --> api-design
Nodes colored by status: green (complete), blue (executing/review), yellow (planning/re-planning), red (blocked), gray (draft/cancelled).
--timeline <task_module>)Extract status transition history from git log:
git log --oneline --fixed-strings --grep="ai-cli-task(<module>)"
Use --fixed-strings to prevent ( and ) in the pattern from being interpreted as regex metacharacters.
Parse commit messages to reconstruct the timeline of status changes with timestamps.
AiTasks/.index.json — get module listing<module>/.index.json to get task metadata--deps: build dependency graph from all modules' depends_on fields; if --timeline: extract history via git log --oneline --grep="ai-cli-task(<module>)"None — list is a pure read-only query. No status changes.
None — list does not create any commits.
None — list does not write .auto-signal. It is a utility command that does not participate in the automation loop.
list never writes files, never changes status, never creates commits. It is safe to run at any time without side effectslist only reads files, it does not acquire AiTasks/<module>/.lock--deps mode only visualizes relationships; it does not validate whether dependencies are met (that is check's responsibility)