@xevy/skills 0.1.50 → 0.1.52

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.
@@ -2,7 +2,7 @@
2
2
  "name": "xevy",
3
3
  "displayName": "Xevy",
4
4
  "description": "Native /xevy:* SDLC workflow commands driven through the Xevy MCP server. Analyze, plan, execute, fix, and move-to-qa run locally by default and accept --cloud for the server Web Agent. Merge stays local; merge-pull-request evaluates and lands the remote PR.",
5
- "version": "0.1.50",
5
+ "version": "0.1.52",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/README.md CHANGED
@@ -112,8 +112,7 @@ with `codex mcp add`.
112
112
  | `generate-image` | Generate an image and save it in the project Gallery |
113
113
  | `seo-research` | Run and explain decision-led SEO reports and supporting research |
114
114
  | `xevy-setup` | Link repo, `.xevy/project.json`, deploy defaults, env sync |
115
- | `analyze [task] [--cloud]` | Task analysis (local by default) |
116
- | `plan [task] [--cloud]` | Planning + review (local by default) |
115
+ | `plan [task] [--cloud]` | Reconnaissance, numbered technical steps, and linked visualization for approval |
117
116
  | `execute [task] [--cloud]` | Build, verify, and open a PR (local by default) |
118
117
  | `fix [task] [--cloud]` | Rework after review (local by default) |
119
118
  | `merge [task]` | Merge a task branch locally for review; leaves remotes and pull requests unchanged |
@@ -123,7 +122,7 @@ with `codex mcp add`.
123
122
  | `investigate` | Diagnose with ephemeral scripts (.env; no secrets) |
124
123
  | `create-xevy-task` | Capture session work into a task |
125
124
 
126
- The analyze, plan, execute, fix, and move-to-qa skills run in the current coding-agent session by default. Add the exact `--cloud` flag before or after the task code to delegate one of those workflows to Xevy's server agent, for example `execute VI22-01 --cloud`. Merge stays local; `merge-pull-request` evaluates and lands an open pull request.
125
+ The plan, execute, fix, and move-to-qa skills run in the current coding-agent session by default. Add the exact `--cloud` flag before or after the task code to delegate one of those workflows to Xevy's server agent, for example `execute VI22-01 --cloud`. Merge stays local; `merge-pull-request` evaluates and lands an open pull request.
127
126
 
128
127
  ## Computer and verified guides
129
128
 
@@ -137,7 +136,7 @@ Use generate-guide to make docs/guides/customer-form/manual.md with screenshots
137
136
 
138
137
  Computer works across desktop and browser apps and projects. Windows uses the signed-in desktop; macOS 14+ requires native Screen Recording and Accessibility consent. The guide workflow stays in the active engine, respects blocks and human take-over, and identifies incomplete verification or publication. Execute/fix use it for UI journeys when an authorized test environment is available.
139
138
 
140
- The package version is `0.1.41`. Run `npx @xevy/skills update -y` after that version is published.
139
+ The package version is `0.1.52`. Run `npx @xevy/skills update -y` after that version is published.
141
140
 
142
141
  ## Security
143
142
 
package/bin/cli.mjs CHANGED
@@ -30,6 +30,7 @@ const pkgRoot = path.resolve(here, "..");
30
30
  const DEFAULT_BASE = "https://xevy.ai";
31
31
  const DEFAULT_AGENTS = ["cursor", "claude-code", "codex"];
32
32
  const RETIRED_SKILLS = [
33
+ "analyze",
33
34
  "analyze-here",
34
35
  "bot",
35
36
  "bot-agent",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.50",
3
+ "version": "0.1.52",
4
4
  "description": "Install Xevy agent skills and secure per-agent MCP transports for Cursor, Claude Code, Codex, and other coding agents.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -11,15 +11,15 @@ Use the connected desktop for the user's application task. Resolve the target Co
11
11
 
12
12
  Use `computer_list` and `computer_get` to find the requested device. Pairing uses `computer_pair` and Xevy Connect. Windows controls the signed-in user's desktop. macOS 14+ requires native Screen Recording and Accessibility consent; report missing consent as a blocker.
13
13
 
14
- Start an `agent` session with `computer_start`, associating the current project/task when relevant. Agent sessions can coexist on one Computer; each keeps its own session ID and shares the device generation until a human takes over or the device pauses. Capture your session ID and generation. A recently heartbeating paused device can accept a fresh controller; input waits for the companion to resume. Explicit local pause requires the user to resume Xevy Connect. Offline, revoked, expired, or unavailable devices require recovery before input. Report the observed state and fixed `pauseReason` when available.
14
+ Start or reuse an `agent` session with `computer_start`, associating the current project/task when relevant and supplying the current schema’s concise purpose and requested capability set. Request Browser for browser journeys, Desktop for native keyboard/mouse work and Shell for Windows commands or files. Local artifact composition on the Agent runtime needs no Windows Shell capability. Repeated start calls under the same authenticated Agent session reuse its live Computer grant. Keep its session ID for follow-up work. Poll pending approval instead of creating another request; request only missing capabilities, while already-enabled capabilities remain usable. The owner approves the requested set in one click in Xevy Computer; the AI cannot enable permissions itself. Continue already-authorized work without repeating chat confirmation. Agent sessions can coexist on one Computer; each keeps its own session ID and shares the device generation until a human takes over or the device pauses. Capture your session ID and generation. A recently heartbeating paused device can accept a fresh controller; input waits for the companion to resume. Explicit local pause requires the user to resume Xevy Computer. Pause retains the selected capabilities and the existing deadline; Resume within that deadline continues with those choices. Capability Off blocks affected work immediately. Approval expires after 24 hours without successful control; screenshots, status checks and reads leave the deadline unchanged. Stop, an ended authenticated Agent session, an actual companion replacement or a new grant epoch needs fresh approval. Deny closes the current request and permits a fresh request; denial of added capabilities leaves previously enabled access available. Offline, revoked, expired, or unavailable devices require recovery before input. Report the observed state and fixed `pauseReason` when available.
15
15
 
16
- Inspect existing sessions before changing control. Human take-over advances the generation and stops agent sessions. Continue only when control is explicitly returned; refresh session metadata before further input. Send the captured generation with pause/resume/stop, including cleanup, so an old agent cannot stop a new controller. Stop only the session this run owns; stopping one agent session leaves other agents connected. For owned cleanup, call `computer_control({computerId, sessionId, generation, transition: 'stop'})` with the captured generation. On the public surface, start with `computer_start({computerId, mode: 'agent', projectId, taskId})` using relevant context; the internal server surface takes only `computerId` and inherits its task, so follow the active tool schema.
16
+ Inspect existing sessions before changing control. Human take-over advances the generation and stops agent sessions. Continue only when control is explicitly returned; refresh session metadata before further input. Send the captured generation with pause/resume/stop, including cleanup, so an old agent cannot stop a new controller. Stop only the session this run owns; stopping one agent session leaves other agents connected. For owned cleanup, call `computer_control({computerId, sessionId, generation, transition: 'stop'})` with the captured generation. Use the active `computer_start` schema for purpose, requested capabilities and project/task context. The internal server surface inherits its authenticated task context. Start never grants an owner permission on its own.
17
17
 
18
18
  For parallel work, start a separate agent session for each agent and keep its session ID with its generation. Agents on the same Computer can share a generation; a generation alone establishes no ownership. Keep browser tabs and file-transfer IDs scoped to the creating session. Submit independent work concurrently, then poll each command ID to its terminal result. The companion bounds simultaneous execution and queues additional work. Native desktop input uses an exclusive focus lease; release it after the observed sequence so another agent can act. A busy desktop lease requires waiting or using an independent browser tab. It provides no reason to pause, stop, or take over another agent. Xevy's Computer view lists connected sessions; “Stop my session” releases only the viewer session created by that view, while “Take over agents” explicitly ends agent control.
19
19
 
20
20
  ## Browser control
21
21
 
22
- For browser work, use tab-scoped browser actions when the companion advertises them. Start an agent session, then call `browser.discover` through `computer_action` and read its `computer_command` result. Select the browser and profile named by the user; otherwise use the relevant open browser/profile shown by discovery. Do not infer a profile from a window title alone.
22
+ For browser work, use tab-scoped browser actions when the companion advertises them. Reuse the current authenticated Agent session’s Computer session, then call `browser.discover` through `computer_action` and read its `computer_command` result. Select the browser and profile named by the user; otherwise use the relevant open browser/profile shown by discovery. Do not infer a profile from a window title alone.
23
23
 
24
24
  Call `browser.connect` with the selected `browserId` and `profileId` to attach to an existing local debugging endpoint. A running browser with a usable endpoint should remain open. If there is no endpoint, explain that starting debugging requires closing and reopening the selected browser/profile. Send `restart: true` only when that restart is authorized; never terminate another profile to obtain a port. The companion owns the loopback debugging connection. Do not connect directly to a debug port from the agent host or expose it across the network.
25
25
 
@@ -48,11 +48,11 @@ When the result expires, use the safe receipt to reconcile owned work. Never rep
48
48
  3. Queue bounded actions with the current generation: focus, launch a supported application, click, drag, scroll, type, or press a key. Use observations to choose the next dependent action.
49
49
  4. Read each command until a terminal result, then take a fresh screenshot and check the expected app result. For a transaction, verify its final state, such as the saved file, submitted record, or visible deletion confirmation. Native input success establishes that the action executed; business success requires observed application evidence.
50
50
  5. A timeout or lost acknowledgement leaves the result uncertain. Inspect command status and the desktop before retrying a write. Resume from the observed state; avoid repeating a submit, payment, send, or delete whose outcome is unresolved.
51
- 6. After the final desktop observation, queue `desktop.release {}` when you used native desktop input and wait for its terminal result. This releases the desktop focus lease so another agent can act. Browser tabs remain independent during the lease. Then call `computer_complete_operation` using the same `operationId`, current generation, and `completed`, `submitted`, `deleted`, or `failed`. Summarize the result actually verified. Stop owned control when finished.
51
+ 6. After the final desktop observation, queue `desktop.release {}` when you used native desktop input and wait for its terminal result. This releases the desktop focus lease so another agent can act. Browser tabs remain independent during the lease. Then call `computer_complete_operation` using the same `operationId`, current generation, and `completed`, `submitted`, `deleted`, or `failed`. Summarize the result actually verified. Release guide-owned resources when the operation finishes. Keep the grant for follow-up work in the same authenticated Agent session; stop owned control on actual Agent session end or an explicit End request.
52
52
 
53
53
  Use the actual tool argument names and response envelope. Queue `const {command} = await computer_action({computerId, sessionId, generation, action: 'desktop.snapshot', payload: {}, operationId, summary: 'Verify the test record'})`, then read `await computer_command({computerId, commandId: command.id})`. The action response is `{command: {...}}`; take the ID from its nested `command`, while MCP clients parse the response's JSON text content. Read each action's current payload schema before constructing inputs.
54
54
 
55
- Screenshot command responses include an image block and JSON text with the command envelope, including its ID, session ID, generation, action, status, and result metadata. Inspect both: the image establishes the visible outcome and the envelope associates it with the command being verified. Image bytes are omitted from the JSON text. Shell and file responses remain JSON command results; decode file chunks locally and verify their checksums. A tool transport response alone proves neither a completed command nor a completed app transaction.
55
+ Screenshot command responses include an image block and JSON text with the command envelope, including its ID, session ID, generation, action, status, and result metadata. Inspect both: the image establishes the visible outcome and the envelope associates it with the command being verified. Image bytes are omitted from the JSON text. For an authorized guide, save the selected terminal capture immediately with `computer_save_capture` using its command reference and actual schema. Retain the returned private attachment ID and capture metadata. This explicitly persists the original bytes; an image block alone provides no file to read. For HTML publication, refer to the saved ID as `xevy-capture:ATTACHMENT_UUID` in an image source and call `computer_create_guide`; it validates ownership and embeds the bytes server-side without sending image base64 through the model. Shell and file responses remain JSON command results; decode file chunks locally and verify their checksums. A tool transport response alone proves neither a completed command nor a completed app transaction.
56
56
 
57
57
  Only after reading terminal operation commands and the relevant final evidence, record the verified result with:
58
58
 
@@ -83,6 +83,6 @@ Use an authorized account and safe test fixtures. Keep credentials in the existi
83
83
 
84
84
  Keep passwords, tokens, typed values, screenshots, raw keys, pointer trails, and personal data out of operation summaries and diagnostic logs. Screen frames and command results remain bounded in memory and expire; inspect them while available. The companion's durable audit outbox has a 100 MiB cap and pauses at capacity. Report `audit_full` and let supported recovery drain it; preserve pending audit evidence. Activity retains the latest 2,000 segments per Computer. Logical activity limits include all retained segments for selected operations; older segments expire at that boundary.
85
85
 
86
- For an explicitly requested guide, save only the necessary authentic screenshots from safe fixtures to the project-local guide evidence, then package them as authorized by [generate-guide](../generate-guide/SKILL.md). Treat every other screen capture as ephemeral. Arrange the screen and use safe fixtures so captures contain no sensitive material. Never redact or mask screenshots. If safe capture is unavailable, omit the capture and report the capture blocker; keep publication private.
86
+ For an explicitly requested guide, save only the necessary authentic screenshots from safe fixtures through the capture-save tool or into the registered temporary / verified gitignored artifact workspace, then package them as authorized by [generate-guide](../generate-guide/SKILL.md). Treat every other screen capture as ephemeral. Arrange the screen and use safe fixtures so captures contain no sensitive material. Never redact or mask screenshots. If safe capture is unavailable, omit the capture and report the capture blocker; keep publication private.
87
87
 
88
88
  The autonomous server extension inherits its task and can control only associated sessions and results. When pairing, rule administration, screenshot export, or publication tools are unavailable, report the exact handoff needed. Use the current engine and available tools; Computer usage never delegates a local run to the cloud.
@@ -11,7 +11,7 @@
11
11
  "Inspects monitor/window and screenshot results before dependent input and uses physical global coordinates from the current image.",
12
12
  "Uses one operationId for edit/save/reopen/final snapshot and reads terminal command status.",
13
13
  "Completion reports completed only after inspecting the reopened exact text and final screenshot; native input success alone is insufficient.",
14
- "Stops only S with captured generation 7; summaries contain semantic app/task metadata and exclude typed content and screenshot bytes.",
14
+ "Releases owned desktop resources and keeps S for follow-up work until the authenticated Agent session ends; any requested stop uses captured generation 7; summaries contain semantic app/task metadata and exclude typed content and screenshot bytes.",
15
15
  "Handoff cites the supplied simulated observations and does not claim a new live Windows or macOS test."
16
16
  ]
17
17
  },
@@ -53,7 +53,7 @@
53
53
  "Creates a B-owned browser tab and transfer; never mutates tab-A or transfer IDs owned by A.",
54
54
  "Uses separate command IDs to read terminal results and examines the image and command envelope together.",
55
55
  "Waits for the busy native lease or uses browser control; never stops, pauses or takes over A to obtain the desktop.",
56
- "Releases a desktop lease only if used, and stops only B with captured generation 12; preserves A.",
56
+ "Releases a desktop lease only if used, and retains B for this live Agent session; any actual session-end stop uses captured generation 12 and preserves A.",
57
57
  "Clearly labels the evidence as scripted and makes no claim of newly performed live testing."
58
58
  ]
59
59
  },
@@ -95,6 +95,20 @@
95
95
  "Cancels only the known owned transfer or stops only B with captured generation 12 to release staged uploads; preserves A.",
96
96
  "Keeps completion honest if new evidence is unavailable; clean-up or terminal status alone does not prove destination bytes."
97
97
  ]
98
+ },
99
+ {
100
+ "prompt": "Scripted evaluation: S has Browser approved and enabled at revision 7 with a deadline six hours away. The same Agent reconnects, pauses/resumes, captures a Browser screenshot and asks for a guide. It then requests Shell for an actual Windows command. The owner denies the additional Shell request. A later Browser snapshot succeeds. The user asks for another Browser guide before ending this Agent session. State session, request and cleanup behavior.",
101
+ "expected_output": "Reuse S and Browser consent; request only Shell, retain Browser after extra-request denial, preserve the deadline during observations and end only owned resources/session at its actual end.",
102
+ "files": [],
103
+ "expectations": [
104
+ "Reconnection and Pause/Resume reuse the existing session and choices within the six-hour deadline, without a new Browser approval.",
105
+ "Requests Shell only for the Windows command; denial of added Shell leaves Browser access valid and allows a fresh later request.",
106
+ "Snapshots and status observations leave inactivity expiry unchanged; successful control alone refreshes it.",
107
+ "Persists selected guide capture through the available capture-save schema and uses opaque attachment references for HTML embedding.",
108
+ "Releases only owned tabs/leases/transfer resources after each guide; keeps S for the follow-up and generation-fences actual End cleanup.",
109
+ "Never enables a capability via AI tool or bypasses owner Off, expired approval or controller fences."
110
+ ],
111
+ "id": 8
98
112
  }
99
113
  ]
100
114
  }
@@ -131,11 +131,13 @@ Before saving, verify that the selected format parses, the requested content is
131
131
 
132
132
  ## 4. Save it as an Artifact
133
133
 
134
- Choose a concise kebab-case filename with the exact extension from the format table and a one-sentence description. Save the finished Artifact to a project-local file before uploading it when filesystem access is available.
134
+ Choose a concise kebab-case filename with the exact extension from the format table and a one-sentence description. With filesystem access, call `artifact_workspace` when available and save the draft in its registered session-owned temporary directory. A project-local fallback must pass `git check-ignore` for each generated file before writing. Generated artifact HTML, PDFs, screenshot files and verification records stay outside tracked repository paths and commits. An explicit request to maintain repository documentation has its own destination. Continue within existing task authorization; artifact creation adds no routine approval prompt.
135
135
 
136
- For a project Artifact, prefer file transfer so the file bytes stay outside model context and MCP JSON arguments:
136
+ For an HTML guide with saved Computer screenshots, use the returned private capture attachment IDs as `<img src="xevy-capture:ATTACHMENT_UUID" alt="Step result">` references and call `computer_create_guide` with its current schema. It validates referenced captures against the authenticated session/project and embeds the bytes server-side. The resulting guide is private and self-contained; verify its stored version, images and exact viewer URL. An unsupported or expired capture requires fresh evidence; the visible tool image cannot be decoded by copying it from chat.
137
137
 
138
- 1. When `create_attachment` exposes `filePath`, call it with the project-local path, exact `mimeType`, matching `fileName`, `description`, optional resolved `taskId`, and `public: false` unless the user explicitly requested a public/shareable Artifact. This streams files up to 100 MB.
138
+ For other project Artifacts, prefer file transfer so the file bytes stay outside model context and MCP JSON arguments:
139
+
140
+ 1. When `create_attachment` exposes `filePath`, call it with a regular file inside the registered temporary workspace or the tool’s permitted project path, exact `mimeType`, matching `fileName`, `description`, optional resolved `taskId`, and `public: false` unless the user explicitly requested a public/shareable Artifact. This streams files up to 100 MB.
139
141
  2. Through MCP, call `prepare_attachment_upload` with the exact filename, MIME type, byte size, description, optional task UUID, and visibility. PUT the local file bytes to the returned `uploadUrl` using the exact `uploadMethod` and `requiredHeaders`, then call `complete_attachment_upload` with the returned `attachmentId`. Completion validates the byte count, signature, and Artifact security state before the viewer URL becomes readable.
140
142
  3. Use `create_attachment` with `textContent`, `sourceUrl`, or `dataBase64` when direct local file transfer is unavailable. Keep inline content for small files; use `sourceUrl` for an existing public binary.
141
143
 
@@ -85,6 +85,19 @@
85
85
  "The content remains readable without external network requests.",
86
86
  "Explicitly requested formats in the other test cases retain their requested MIME type and extension."
87
87
  ]
88
+ },
89
+ {
90
+ "prompt": "Scripted evaluation: create a private HTML feature guide artifact from two saved Computer captures. artifact_workspace returns /tmp/xevy-artifacts/session-42, registered for uploads. Both capture IDs belong to this project and Agent session. computer_create_guide validates xevy-capture image references and returns a stored HTML version and viewer URL. A project docs/guides directory exists but is tracked. Explain the creation and verification using only supplied simulated outcomes.",
91
+ "expected_output": "Temporary draft, server-side embedding of private owned captures, verified private artifact URL and no generated files in tracked docs.",
92
+ "files": [],
93
+ "expectations": [
94
+ "Saves draft/verification files in the registered temporary workspace; never chooses tracked docs/guides merely because it exists.",
95
+ "Uses capture IDs returned by the save tool and xevy-capture image references; no copied chat pixels or model-supplied screenshot base64.",
96
+ "Uses current computer_create_guide schema and confirms stored private metadata, version bytes and image readability.",
97
+ "Keeps custom HTML self-contained and existing sandbox/security rules intact.",
98
+ "Returns the exact supplied viewer URL only after successful storage; labels supplied evidence as scripted."
99
+ ],
100
+ "id": 9
88
101
  }
89
102
  ]
90
103
  }
@@ -47,7 +47,7 @@ Check `list_tasks`/`find_task` once more before creating to avoid a duplicate.
47
47
  After the task exists, if scope, approach, category/epic placement, or trade-offs are **genuinely ambiguous** — don't bury them in the description or guess:
48
48
  - Call `mcp__xevy__create_decision` with preset choices + explanations (optional follow-up per choice).
49
49
  - If the user is present, use the host's user-question mechanism first, then persist the answer with `create_decision` + `answer_decision`.
50
- - Open questions gate `/xevy:mark-ready`, analyze, plan, and execute until answered — keep them few and high-signal.
50
+ - Open questions gate `/xevy:mark-ready`, plan and execute until answered — keep them few and high-signal.
51
51
  - In **capture mode**, only raise decisions for real ambiguities in requirements or review routing — not for documented AI work.
52
52
  - In **ordinary mode**, this is the primary way to capture unresolved intake ambiguities.
53
53
 
@@ -62,7 +62,7 @@ After the task exists, if scope, approach, category/epic placement, or trade-off
62
62
  No AI work to capture (or a fresh, unrelated task): create the task from `$ARGUMENTS`/the request. Capture the user's story, problem, expectation, and desired outcome in plain language — do NOT fabricate technical detail or a PR. Raise any genuine ambiguities with `create_decision` (section 4b). Leave status at `draft` — use `/xevy:mark-ready` to promote once open questions are answered. Do NOT set `ready` while any decision is still open. Skip the review/QA routing.
63
63
 
64
64
  ## 7. Report
65
- Give the task **code + the `url` returned by the create/update tool** (always show this link so the user can open and review it), its **status**, any **open decisions** (call `list_task_decisions` if you raised questions), and a one-line summary of what was captured (PR link, branch, preview URL). Tell the user a developer/QA can now pick it up directly from Xevy (capture mode) or that they should answer open questions and analyze/plan while draft (ordinary mode). After planning, AI Agent-owned Process Owner stages advance automatically; human-owned stages wait for the user to run `/xevy:mark-ready`.
65
+ Give the task **code + the `url` returned by the create/update tool** (always show this link so the user can open and review it), its **status**, any **open decisions** (call `list_task_decisions` if you raised questions), and a one-line summary of what was captured (PR link, branch, preview URL). Tell the user a developer/QA can now pick it up directly from Xevy (capture mode) or that they should answer open questions and plan while draft (ordinary mode). After planning, AI Agent-owned Process Owner stages advance automatically; human-owned stages wait for the user to run `/xevy:mark-ready`.
66
66
 
67
67
  ## Rules
68
68
  - Call order: `create_task` first, then any taskId-dependent call with its returned `task.id`; never retry a `Task not found` note call.
@@ -3,7 +3,7 @@ name: execute
3
3
  description: Execute code changes locally by default — use the task worktree, implement, push, and open a PR for separate verification and review. Pass --cloud to delegate implementation to the Xevy server agent, then review and correct its result.
4
4
  argument-hint: "[task] [--cloud]"
5
5
  disable-model-invocation: true
6
- allowed-tools: "Read Grep Edit Write Bash Agent mcp__xevy__find_task mcp__xevy__update_task mcp__xevy__update_task_status mcp__xevy__list_specs mcp__xevy__create_spec mcp__xevy__update_spec mcp__xevy__create_subtask mcp__xevy__list_subtasks mcp__xevy__update_subtask mcp__xevy__list_task_notes mcp__xevy__create_task_note mcp__xevy__update_task_note mcp__xevy__list_sprints mcp__xevy__assign_task_to_sprint mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision mcp__xevy__start_ai_action mcp__xevy__get_ai_execution mcp__xevy__list_ai_executions set_session_task_lock"
6
+ allowed-tools: "Read Grep Edit Write Bash Agent mcp__xevy__find_task mcp__xevy__update_task mcp__xevy__update_task_status mcp__xevy__get_task_plan mcp__xevy__list_specs mcp__xevy__create_spec mcp__xevy__update_spec mcp__xevy__list_subtasks mcp__xevy__update_subtask mcp__xevy__list_task_notes mcp__xevy__create_task_note mcp__xevy__update_task_note mcp__xevy__list_sprints mcp__xevy__assign_task_to_sprint mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision mcp__xevy__start_ai_action mcp__xevy__get_ai_execution mcp__xevy__list_ai_executions set_session_task_lock"
7
7
  ---
8
8
 
9
9
  # /xevy:execute — execute locally or in the cloud
@@ -20,20 +20,20 @@ Local implementation is the default. Pass the exact standalone `--cloud` flag to
20
20
 
21
21
  ## 1. Resolve and apply common gates
22
22
 
23
- - Resolve the remaining task argument or the in-context task. Read its `## Analysis`, plan spec, and subtasks. If planning artifacts are absent, inspect the code and prepare a concrete plan/checklist within the approved requirements before implementing. If scope or authorization prevents preparing it, record the missing prerequisite as blocked and continue independent authorized work.
24
- - Sprint gate: if an active sprint exists and the task is not on it, require `## Analysis` and `storyPoints` greater than zero, then call `assign_task_to_sprint`. If those prerequisites are missing, record the sprint prerequisite as blocked; preserve sprint and authorization gates without opening a question dialog.
23
+ - Resolve the task and read its current numbered Plan and linked visualization. Fetch `get_task_plan` and require approval of the current fingerprint before implementation. Missing, stale, or absent approval means present the short titles for human approval and pause affected implementation. Preserve original requirements and legacy history. An Analysis section and generated subtasks are never prerequisites.
24
+ - Sprint gate: if an active sprint exists and the task is not on it, require the Plan and `storyPoints` greater than zero, then call `assign_task_to_sprint`. Record missing sprint prerequisites as blocked and preserve authorization gates.
25
25
 
26
26
  ### Code-only checklist and resume fallback
27
27
 
28
- Classify the actual work described in each existing subtask and any resume note before following its next action; keywords and stage labels alone do not determine eligibility. Mark legacy purely investigative, validation, verification, QA, review, or procedural spec-lock items `skipped` with an explanation through `update_subtask`. Preparation belongs to Analyze/Plan; post-execution checks belong to separate **QA Notes** or **Technical Review Instructions**. Select the next pending code subtask when a stale resume target is workflow-only.
28
+ Classify the actual work described in each existing subtask and any resume note before following its next action; keywords and stage labels alone do not determine eligibility. Mark legacy purely investigative, validation, verification, QA, review, or procedural spec-lock items `skipped` with an explanation through `update_subtask`. Preparation belongs to Plan; post-execution checks belong to separate **QA Notes** or **Technical Review Instructions**. Select the next pending code subtask when a stale resume target is workflow-only.
29
29
 
30
- For mixed items, implement the concrete code portion and defer its workflow checks to those notes. Input-validation implementation and adding/editing test files remain code work. Procedural checklist requirements do not block Execute; existing unanswered Analyze/Plan decisions, missing authorization, and conflicting technical contracts remain blockers. If inline planning is authorized, finish investigation and feasibility checks before recording code-only implementation steps. If no code changes remain, report that truthfully; never create empty commits or claim skipped work produced implementation.
30
+ For mixed items, implement the concrete code portion and defer its workflow checks to those notes. Input-validation implementation and adding/editing test files remain code work. Procedural checklist requirements do not block Execute; existing unanswered Plan decisions, missing authorization, and conflicting technical contracts remain blockers. If inline planning is authorized, finish investigation and feasibility checks before recording code-only implementation steps. If no code changes remain, report that truthfully; never create empty commits or claim skipped work produced implementation.
31
31
 
32
32
  ## 2A. Local workflow (default)
33
33
 
34
34
  ### Decisions gate
35
35
 
36
- Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered Analyze/Plan and intake decisions, missing authorization, and scope or contract conflicts remain gates; record affected work as blocked and continue independent authorized work. For new material implementation choices, inspect the code and record `create_decision` with `raisedAtStage: "execute"`, exactly one `recommended: true` choice per question (including follow-ups), and evidence/rationale in explanations. The recommended path is answered by AI; continue without asking the user or re-running Analyze.
36
+ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered Plan and intake decisions, missing authorization, and scope or contract conflicts remain gates; record affected work as blocked and continue independent authorized work. For new material implementation choices, inspect the code and record `create_decision` with `raisedAtStage: "execute"`, exactly one `recommended: true` choice per question (including follow-ups), and evidence/rationale in explanations. The recommended path is answered by AI; continue without asking the user or re-running Plan.
37
37
 
38
38
  ### Worktree protocol
39
39
 
@@ -45,7 +45,7 @@ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered A
45
45
  ### Implement
46
46
 
47
47
  - Move the task to `in_progress` with `update_task_status` when implementation begins. This mirrors cloud execution, which moves to `in_progress` at start and `for_review` on success.
48
- - Work through the remaining code subtasks in order, committing coherent code milestones without requiring per-subtask checks or sign-off. When useful and supported, dispatch builder/frontend subagents with the worktree as their working directory. Keep changes surgical, match existing style, and update subtask status through MCP.
48
+ - Work through the approved numbered steps in order, committing coherent code milestones without requiring per-subtask checks or sign-off. When useful and supported, dispatch builder/frontend subagents with the worktree as their working directory. Keep changes surgical, match existing style, and update existing legacy subtask status through MCP only when applicable; never generate subtasks from the Plan.
49
49
  - Before editing UI pages, components, app shell, forms, or styling, follow `/xevy:xevy-design` and the project's `./.xevy/design.md`.
50
50
  - Apply the Decisions gate policy to material choices discovered during implementation.
51
51
  - Record deferred verification, QA, and review in separate handoff notes. A code subtask is complete when its implementation is committed; workflow check completion is outside its checklist.
@@ -12,12 +12,14 @@ Deliver a usable manual for the requested app or feature with authentic screensh
12
12
 
13
13
  Read the current task, approved scope, repository guidance, and project context when available. Resolve the intended user, app, build/commit, test URL or desktop app, starting state, and final outcome. Select an authenticated test account and disposable fixtures appropriate to that journey. Protect real customers and production records; obtain authorization before any external mutation beyond the agreed test scope.
14
14
 
15
- Use the host's available browser observation tools for web journeys, or [computer](../computer/SKILL.md) for native desktop and connected-computer work. Read the actual tool contracts. If access, authentication, operating-system consent, blocks, offline state, or human take-over prevents testing, preserve the evidence and identify the next action. Respect the current controller and enabled rules.
15
+ Use the host's available browser observation tools for web journeys, or [computer](../computer/SKILL.md) for native desktop and connected-computer work. Read the actual tool contracts. State a short purpose and request only the needed Computer capabilities; a browser guide normally needs Browser. Reuse this authenticated Agent session’s Computer session throughout the journey and follow-up guide work. Poll an existing pending request; request owner approval only for capabilities currently missing. A valid approval remains available through reconnection and Pause/Resume until the session ends or its rolling 24-hour inactivity deadline expires. Successful control advances that deadline; screenshots, status checks, and reads leave it unchanged. Local file composition in the Agent runtime requires no Windows Shell permission. Continue authorized work without repeating chat confirmation; native owner consent and capability Off still govern access. If access, authentication, operating-system consent, blocks, offline state, or human take-over prevents testing, preserve the evidence and identify the next action. Respect the current controller and enabled rules.
16
16
 
17
17
  ## 2. Walk through and draft
18
18
 
19
19
  Run the journey in the real app. Number the user actions in the order a user performs them. Each step states its starting condition, concrete action, and observable expected result. Capture the relevant controls and result from the actual application using safe fixtures. Include setup requirements, role/access requirements, and recovery guidance only where the user needs them.
20
20
 
21
+ Persist each selected screenshot while its command result is still available. After observing the terminal snapshot, use `computer_save_capture` with its owned command reference and the current tool schema. Retain the returned attachment ID, MIME type, dimensions and capture time; an image block in chat supplies observation, while the capture-save tool supplies the reusable file. The save operation is idempotent for the same owned capture. If it is unavailable, use an actual file returned by the host capture tool; report a blocker only when neither path provides bytes.
22
+
21
23
  Maintain a separate verification ledger with step ID, environment/build, fixture, expected and observed result, command/test references, screenshot path and capture time, and PASS/FAIL/BLOCKED. A native click or successful API call alone does not establish that the user's journey worked. Verify visible app state and meaningful persistence or downstream effects, using authorized read-only checks where useful.
22
24
 
23
25
  Screenshots must show the step they support on the tested build. Generated illustrations, rewritten screenshots, mocked UI, old captures, and passing unit tests cannot stand in for observed app evidence. A simulated evaluation is labelled as simulated; it never becomes live proof.
@@ -38,14 +40,18 @@ Discard superseded screenshots. After the final code changes and review correcti
38
40
 
39
41
  Keep the copy-ready guide focused on the user's task: prerequisites, numbered actions with screenshots, expected results, and useful recovery guidance. Keep code changes, technical checks, fixture IDs, failures, and fix history in a separate verification record. Mention a user-facing limitation in the manual where it affects a step.
40
42
 
41
- Save the guide and verification record under the project's existing documentation/artifact convention, or a descriptive project-local `docs/guides/<feature>/` directory when none exists. Use HTML by default and honour an explicit requested format or filename. For self-contained HTML, embed the selected real screenshots as data URLs and keep styles inline. For Markdown, use supported embedded images or project-local relative screenshot files; ensure the published viewer actually resolves them. For PDF, generate real PDF bytes from the finished guide and inspect the rendered pages. Follow [create-artifact](../create-artifact/SKILL.md) for format validation, file limits, viewer security, and supported upload paths.
43
+ Stage the guide, screenshots and verification ledger in the session-owned temporary directory returned by `artifact_workspace` when available. A project-local staging fallback must pass `git check-ignore` for every generated path before writing. Keep generated HTML, PDFs and screenshots out of tracked paths and commits; a request for an artifact uses private Drive as the final destination. Honour an explicit request for repository documentation separately. Use HTML by default and honour an explicit requested format or filename.
44
+
45
+ For Computer screenshots, build ordinary HTML with `<img src="xevy-capture:ATTACHMENT_UUID" alt="Observable step result">` using each returned capture attachment ID, then call `computer_create_guide` with the current tool schema. The server validates ownership/project and embeds the actual private image bytes. Submit the small HTML template, keep CSS inline, and let the tool produce the self-contained file; do not reconstruct image bytes from a displayed image block or place screenshot base64 in model arguments. When real local screenshot files are available, embed those bytes with a local helper and upload the resulting file. For Markdown, use supported embedded images or project-local relative screenshot files; ensure the published viewer actually resolves them. For PDF, generate real PDF bytes from the finished guide and inspect the rendered pages. Follow [create-artifact](../create-artifact/SKILL.md) for format validation, file limits, viewer security, and supported upload paths.
42
46
 
43
47
  Store only the selected safe screenshots needed for the requested guide. Keep credentials, customer data, typed secrets, screen bytes, raw keys, and pointer trails out of logs. Arrange the screen and use safe fixtures to keep sensitive material out of captures. Never redact or mask screenshots. If a safe capture is unavailable, omit it and report a capture blocker; keep publication private. Computer frames/results stay in bounded memory; the companion audit cap is 100 MiB. Keep stable operation IDs for logical transactions, verify business outcomes separately, and clean up only owned sessions using captured generations.
44
48
 
45
49
  ## 5. Publish and hand off
46
50
 
47
- Publish the complete, verified guide privately to the current project's Xevy Drive through [create-artifact](../create-artifact/SKILL.md). When a blocker leaves a useful manual within the requested journey, publish it privately with a clear PARTIAL label, affected steps, and limitations. Blocked and untested steps retain those labels; they receive no passing labels. When the available evidence cannot support a useful manual, retain the local draft and verification record and report the required handoff. Save the project-local file first; prefer direct file upload or the prepare/PUT/complete upload flow. Use `public: false` unless the user explicitly requests public sharing. Resolve any task code to its real UUID. Verify successful storage and the exact returned viewer URL; open the uploaded guide through an available viewer and check images, layout, and step readability. Keep the verification record separate and attach its local path or a distinct private artifact when appropriate.
51
+ Publish the complete, verified guide privately to the current project's Xevy Drive through [create-artifact](../create-artifact/SKILL.md). When a blocker leaves a useful manual within the requested journey, publish it privately with a clear PARTIAL label, affected steps, and limitations. Blocked and untested steps retain those labels; they receive no passing labels. When the available evidence cannot support a useful manual, retain the local draft and verification record and report the required handoff. Retain the draft and verification ledger in the temporary or verified gitignored workspace; prefer `computer_create_guide` for saved Computer captures, or direct file upload / the prepare/PUT/complete flow for a completed local file. A temporary upload path must be inside the registered workspace root; read the tool’s returned path constraints. Use `public: false` unless the user explicitly requests public sharing. Resolve any task code to its real UUID. Verify successful storage and the exact returned viewer URL; open the uploaded guide through an available viewer and check images, layout, and step readability. Keep the verification record separate and attach its local path or a distinct private artifact when appropriate.
48
52
 
49
53
  If publication fails, retain the local manual and evidence, report the real error and incomplete publication, and avoid inventing a Drive link. If a server autonomous agent lacks artifact or capture/export tools, return the prepared content, verification ledger, and precise publication/capture handoff to the interactive agent. Tool absence does not permit switching engines or bypassing scope restrictions.
50
54
 
51
- Return the guide path and confirmed viewer URL when stored, final build/environment, tested journey outcome, and any remaining blockers. Separate user steps from technical verification and fix history. Hand off review; merge, deploy, and task status changes remain governed by the parent workflow and explicit authorization.
55
+ Release any owned desktop focus lease, close only guide-owned browser tabs and disconnect this session’s browser connection when finished. Completing a guide releases those resources and keeps the same authenticated Agent session’s grant available for follow-up work. Stop Computer control when the Agent session actually ends or the user asks to end access; preserve other agents and the captured generation. Verify that generated outputs have left tracked repository paths clean.
56
+
57
+ Return the temporary guide path and confirmed viewer URL when stored, final build/environment, tested journey outcome, and any remaining blockers. Separate user steps from technical verification and fix history. Hand off review; merge, deploy, and task status changes remain governed by the parent workflow and explicit authorization.
@@ -10,7 +10,7 @@
10
10
  "Walks the actual scripted journey, numbers user actions, and records starting condition/action/observable result for each.",
11
11
  "Tests every step and reopens the saved record to verify meaningful persistence on build A.",
12
12
  "Uses only authentic supplied captures tied to the final tested build; never claims synthetic illustrations or unit tests prove the live app.",
13
- "Saves a project-local HTML file by default and embeds selected safe screenshots; technical verification/fix history is separate.",
13
+ "Saves HTML in the registered temporary or verified gitignored artifact workspace by default and embeds selected safe screenshots; technical verification/fix history is separate.",
14
14
  "Follows create-artifact with public false and reports exactly https://test.invalid/file/guide-1 only after successful upload/viewer confirmation.",
15
15
  "Final result states environment/build and simulated evidence scope; no merge/deploy/statusdone or cloud delegation occurs."
16
16
  ]
@@ -56,6 +56,20 @@
56
56
  "Leaves missing evidence PENDING or BLOCKED rather than PASS, and preserves separate verification ledger and private publication scope.",
57
57
  "Clearly labels this supplied scripted evidence and claims no new live test, guide URL or completed publication."
58
58
  ]
59
+ },
60
+ {
61
+ "prompt": "Scripted evaluation: an owner asks for a private guide for Computers through WinPC and approves Browser once. computer_start returns S generation 12, permissionRevision 4, Browser enabled, expiresAt tomorrow. artifact_workspace returns a registered temporary path. Two observed browser.snapshot commands show the real feature and each computer_save_capture returns a private attachment ID. computer_create_guide accepts xevy-capture image references and returns a private HTML artifact with images embedded. A follow-up guide request in the same authenticated Agent session returns S again without pending approval. Pause/Resume keeps Browser enabled. Produce the guide workflow and handoff without performing live mutations.",
62
+ "expected_output": "Both scripted guides use S and temporary staging, save real captures, publish verified private self-contained HTML and retain the grant for follow-up work.",
63
+ "files": [],
64
+ "expectations": [
65
+ "Uses Browser only and supplies a concise guide purpose; never requests Windows Shell for writing guide HTML in the Agent runtime.",
66
+ "Reuses S for both guides, polls only a genuinely pending missing capability and repeats neither native approval nor chat confirmation for authorized work.",
67
+ "Saves each owned terminal capture promptly, uses returned private attachment IDs in xevy-capture image references and lets computer_create_guide embed bytes.",
68
+ "Stages HTML/screenshots/ledger in the registered temporary path; checks gitignore before any project-local fallback and leaves tracked repositories clean.",
69
+ "Verifies the saved artifact, actual embedded images and exact returned URL; reports the supplied proof as scripted.",
70
+ "Releases owned browser tabs/connection and desktop lease if used, keeps S until true Agent session end and preserves the unchanged 24-hour timer during passive reads."
71
+ ],
72
+ "id": 5
59
73
  }
60
74
  ]
61
75
  }
@@ -19,11 +19,11 @@ Read the resolved task's status. `mark-ready` only promotes a task that is in **
19
19
  ## 3. Answer open questions (MANDATORY gate)
20
20
  - Call `mcp__xevy__list_task_decisions` for the task.
21
21
  - For **every** decision that is still OPEN, present the question and its preset choices to the user, then record their answer with `mcp__xevy__answer_decision` (pass the chosen `answerChoiceId` and/or `answerText`). Never fabricate an answer or skip an open question.
22
- - Answering may trigger a server-side analyze re-run — that is expected and does **not** change the task status.
22
+ - Answering may trigger a server-side Plan refresh — that is expected and does **not** change the task status.
23
23
  - Do not proceed while any decision is still open.
24
24
 
25
25
  ## 4. Mark ready
26
26
  Once **no** open decisions remain, call `mcp__xevy__update_task_status({ taskId, status: "ready" })`.
27
27
 
28
28
  ## 5. Report
29
- Report the task code/title, its new status (`ready`), and the task URL. Don't push the user into `/xevy:plan` or `/xevy:analyze` — let them choose the next step at their own pace.
29
+ Report the task code/title, its new status (`ready`), and the task URL. Don't push the user into `/xevy:plan` — let them choose the next step at their own pace.
@@ -1,12 +1,12 @@
1
1
  ---
2
2
  name: plan
3
- description: Plan a task locally by default — finish investigation and plan validation, then record concrete code changes as ordered subtasks. Pass --cloud to delegate planning to the Xevy server agent, then review and correct its result.
3
+ description: Plan a task locally by default — inspect the code and write a short numbered technical plan with a linked visualization for human approval. Pass --cloud to delegate planning to the Xevy server agent, then review and correct its result.
4
4
  argument-hint: "[task] [--cloud]"
5
5
  disable-model-invocation: true
6
- allowed-tools: "Read Grep Bash Agent mcp__xevy__find_task mcp__xevy__create_spec mcp__xevy__update_spec mcp__xevy__list_specs mcp__xevy__get_spec mcp__xevy__create_subtask mcp__xevy__update_subtask mcp__xevy__list_subtasks mcp__xevy__list_task_notes mcp__xevy__create_task_note mcp__xevy__update_task_note mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision mcp__xevy__get_process_owners mcp__xevy__update_task_status mcp__xevy__start_ai_action mcp__xevy__get_ai_execution mcp__xevy__list_ai_executions"
6
+ allowed-tools: "Read Grep Bash Agent mcp__xevy__find_task mcp__xevy__create_spec mcp__xevy__update_spec mcp__xevy__list_specs mcp__xevy__get_spec mcp__xevy__create_attachment mcp__xevy__create_attachment_version mcp__xevy__get_task_plan mcp__xevy__approve_task_plan mcp__xevy__update_task mcp__xevy__list_task_notes mcp__xevy__create_task_note mcp__xevy__update_task_note mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision mcp__xevy__get_process_owners mcp__xevy__update_task_status mcp__xevy__start_ai_action mcp__xevy__get_ai_execution mcp__xevy__list_ai_executions"
7
7
  ---
8
8
 
9
- # /xevy:plan — plan locally or in the cloud
9
+ # /xevy:plan — inspect, visualize, and approve
10
10
 
11
11
  Local planning is the default. Pass the exact standalone `--cloud` flag to delegate planning to the Xevy server agent.
12
12
 
@@ -18,53 +18,42 @@ Local planning is the default. Pass the exact standalone `--cloud` flag to deleg
18
18
  - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
19
  - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
20
20
 
21
- ## 1. Resolve the task
21
+ ## 1. Resolve the task and investigate
22
22
 
23
- Resolve the remaining task argument or the in-context task. It should already have a `## Analysis` section. If it does not, suggest `/xevy:analyze` and stop.
23
+ Resolve the task argument or the in-context task. Read the original requirements, existing Plan, relevant code, similar patterns, and open decisions. Plan owns reconnaissance and feasibility checks; an Analysis section is never a prerequisite. Preserve original requirements and legacy task history.
24
+
25
+ Resolve routine technical choices from the code. Collect meaningful human questions together, persist them with `create_decision` at `raisedAtStage: "plan"`, and record human answers with `answerSource: "human"`. Open decisions block the affected work. Use a scout or independent plan reviewer when supported and authorized.
24
26
 
25
27
  ## 2A. Local workflow (default)
26
28
 
27
- ### Decisions gate and recon
29
+ ### Write the concrete Plan
28
30
 
29
- Call `mcp__xevy__list_task_decisions`. If any decision is **open**, review the questions together through the host's user-question mechanism, record each human answer with `mcp__xevy__answer_decision`, and reflect it in the plan. Open decisions block AI work, so never guess or bypass them.
31
+ Write the canonical `## Plan` section in the task description. Synchronize an existing spec with kind `plan` when present; separate contract specs are optional when the changes need them. Use approximately five or six numbered steps; each Xevy step follows **Title — concise technical details**. Name the relevant files, functions or components, the change, and resulting behavior in one or two short sentences. Keep the plan proportionate to the task; use fewer steps for small changes.
30
32
 
31
- When the host supports subagents, dispatch a **scout** for codebase recon covering relevant files, callers/callees, similar patterns, and baseline health. Otherwise perform the same recon in this session. Complete investigation, feasibility checks, and validation of the proposed approach during Analyze/Plan preparation. Preserve genuine authorization requirements and resolve conflicting technical contracts before implementation.
33
+ Example stored in Xevy:
32
34
 
33
- ### Write the plan
35
+ 1. Remove Analyze — Remove the action from task controls, runner schemas, prompts, and packaged skills; retain historical executions and decisions.
36
+ 2. Simplify Plan — Write numbered technical steps to the task description; remove automatic subtask generation.
34
37
 
35
- - Create a plan spec with `mcp__xevy__create_spec` using kind `plan`. Numbered implementation steps contain only concrete code changes: target files, changes, and expected behavior. Include a trace matrix: requirement → files → code change → expected behavior.
36
- - Create ordered subtasks with `mcp__xevy__create_subtask`, one per discrete code change, using fullstack or frontend stages. Group work into reviewable end-to-end pieces; keep frontend and backend work for one capability together.
37
- - Adding input-validation code and adding/editing test files are code work. Investigation, validation, running verification, QA, review, and procedural spec-lock work are outside the numbered implementation plan and subtask checklist.
38
- - Create or update separate task notes titled **QA Notes** and **Technical Review Instructions** for post-execution checks. Keep these checks out of subtask descriptions and dependencies.
38
+ Plan creates zero subtasks. Preserve existing subtasks and treat them as legacy guidance. Do not convert numbered steps into subtasks, a trace-matrix document, or a required checklist. Keep verification details in separate **QA Notes** or **Technical Review Instructions** when needed. Estimate `storyPoints` during Plan when the project uses sprint estimates.
39
39
 
40
- ### Plan-review
40
+ ### Link the visualization
41
41
 
42
- When the host supports subagents, dispatch a **plan-reviewer** to cross-check every matrix item against requirements, find orphans and gaps, and validate cross-flow risks and “must NOT” constraints during planning. Otherwise perform a separate self-review pass. Fold code changes into the spec and subtasks, and verification instructions into the separate handoff notes. Finish plan validation before finalizing the implementation checklist; do not create a review or sign-off subtask.
42
+ Follow [create-artifact](../create-artifact/SKILL.md) to save a private project Artifact associated with the task UUID. Use self-contained HTML by default. Show the proposed UI, before/after behavior, or a clear flow of the changes; connect it to the numbered plan. Update an existing task visualization through a new attachment version when appropriate. Link the returned stable Artifact URL from the task's `## Plan` section and any existing matching plan spec. Never invent an Artifact URL. If publication is unavailable, report the exact gap and leave the plan awaiting completion.
43
43
 
44
- Scope each review to the approved requirements and inspected commit. In the first review pass, check the complete scope and report all findings together. Record requirement coverage, evidence references, and each finding's severity, location, expected behavior, and verification. In the second review pass, verify the fixes and regressions affected by those findings, reusing evidence that remains valid for the current commit and scope. A further pass requires a recorded reason: failed fix, new regression, missing evidence, or changed approved scope. Keep unresolved findings and unverified coverage visible, and report PARTIAL/FAIL until the required evidence supports approval.
44
+ ### Review and request approval
45
45
 
46
- Finish inspecting the code and similar patterns, then collect all remaining meaningful human questions together before implementation. Persist each through `mcp__xevy__create_decision` with `raisedAtStage: "plan"`, preset choices, exactly one `recommended: true` choice per question, evidence/rationale in explanations, and necessary branching follow-ups. Resolve routine choices from the code. When the user is present, collect answers together and record each with `answer_decision` and `answerSource: "human"`.
46
+ Check every requirement against the inspected code, numbered steps, and visualization; correct gaps before presenting it. Do not create review/sign-off subtasks. Do not start Execute or change task status as a side effect of planning.
47
47
 
48
- ### Final check
48
+ Fetch `get_task_plan` and retain the fingerprint of the Plan being presented. In chat show only the short numbered titles, the task link, and visualization link, then request approval. Keep the technical details in Xevy. For the example above, chat shows:
49
49
 
50
- Confirm the final plan is complete and feasible against the actual code and fix every remaining gap. Call `mcp__xevy__list_task_decisions` again and surface any decision that remains open. Do not change task status as a side effect of local planning. Draft is preparation-only; the user explicitly submits it to Ready. When planning is configured Refine work for a Ready task, completion moves it to Planned through the server-owned Process Owner flow. Do not start execution.
50
+ 1. Remove Analyze.
51
+ 2. Simplify Plan.
51
52
 
52
- Report a PASS/PARTIAL verdict, the matrix summary, open decisions, resulting status, and task URL.
53
+ After a new affirmative human message approves this exact current plan, fetch `get_task_plan` again and compare its `fingerprint` with the revision presented. Record the retained fingerprint through `approve_task_plan` only when they match. A changed plan requires fresh approval. The approval tool records a human decision; planning agents must never approve their own output. Explain unresolved decisions or missing visualization separately and keep affected work blocked. Draft remains preparation until explicitly submitted to Ready.
53
54
 
54
55
  ## 2B. Cloud workflow (`--cloud`)
55
56
 
56
- ### Run the server action
57
-
58
- - Call `mcp__xevy__start_ai_action({ taskId, action: "plan", stream: true })`; always pass `stream: true`. Report live progress as it arrives. Do not use fire-and-forget or sleep/manual polling loops.
59
- - Only if the streamed call returns before a terminal status because of a genuine disconnect, resume with `mcp__xevy__get_ai_execution` (use `list_ai_executions` if needed).
60
- - On failure, surface the output and offer to retry or rerun `/xevy:plan` without `--cloud`.
61
-
62
- ### Review and correct
63
-
64
- - Read the produced plan spec (`list_specs` → `get_spec`) and subtasks (`list_subtasks`).
65
- - Build a trace matrix from every task/Analysis requirement to a subtask or plan step. Flag orphaned requirements and unjustified steps. Inspect the code with Read/Grep to confirm referenced files and approaches are real and feasible.
66
- - Check cross-flow risks such as guards, context rehydration, effects, and async side effects during planning. Put post-execution verification of “must NOT” constraints in separate QA Notes or Technical Review Instructions.
67
- - Correct the produced plan so numbered steps and subtasks contain only concrete code changes with expected behavior; remove workflow-only plan steps and move their checks to separate handoff notes. Retain input-validation implementation and test-file changes. Fix gaps by editing the spec or adding/reordering code subtasks through MCP. Apply the review passes above: consolidate the complete first-pass findings, then verify corrections and affected flows in the second pass. Record the reason for any further pass; retain unresolved matrix gaps and missing evidence in the verdict.
68
- - Do not change task status or start execution yourself. The server applies Process Owner automation after a successful run.
57
+ Call `start_ai_action({ taskId, action: "plan", stream: true })` and report live progress. If a genuine disconnect ends the stream early, resume through `get_ai_execution` or `list_ai_executions`. On failure, report the captured output and offer a retry in the selected engine.
69
58
 
70
- Report a PASS/PARTIAL verdict, gaps closed, resulting task status, and task URL.
59
+ Read the canonical task description Plan and any existing plan spec. Inspect referenced code and validate the numbered steps, concise technical details, requirement coverage, real linked task Artifact, and zero generated subtasks. Correct gaps in the task Plan, any existing matching spec, or Artifact; leave legacy subtasks intact. Apply the same short-title chat presentation and explicit human approval procedure as local planning. The server owns status automation and never treats successful planning as approval to Execute.
@@ -54,4 +54,4 @@ Cursor, and other remote MCP clients use OAuth.
54
54
  - Read `get_project_workbreakdown`. Only when the project has no categories, create 3–6 user/product-area categories (never technical-layer categories such as Frontend or API) and 1–3 starter epics per category for already-present capabilities. If categories exist, skip this step. Never create tasks.
55
55
 
56
56
  ## 7. Report
57
- Summarise: workspace/project, repo link, deploy build pack + ports, count of env keys added (names only), and the next Xevy skills they can run (`analyze`, `execute`, `deploy`; slash-command names may be available in some clients). Do not print secrets.
57
+ Summarise: workspace/project, repo link, deploy build pack + ports, count of env keys added (names only), and the next Xevy skills they can run (`plan`, `execute`, `deploy`; slash-command names may be available in some clients). Do not print secrets.
@@ -1,68 +0,0 @@
1
- ---
2
- name: analyze
3
- description: Analyze a task locally in the current coding-agent session by default — inspect the codebase, write the Analysis section and story points, then self-review. Pass --cloud to delegate analysis to the Xevy server agent, then review and correct its result.
4
- argument-hint: "[task] [--cloud]"
5
- disable-model-invocation: true
6
- allowed-tools: "Read Grep Bash mcp__xevy__find_task mcp__xevy__update_task mcp__xevy__list_specs mcp__xevy__list_subtasks mcp__xevy__list_task_notes mcp__xevy__create_task_note mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision mcp__xevy__start_ai_action mcp__xevy__get_ai_execution mcp__xevy__list_ai_executions"
7
- ---
8
-
9
- # /xevy:analyze — analyze locally or in the cloud
10
-
11
- Local analysis is the default. Pass the exact standalone `--cloud` flag to delegate the analysis to the Xevy server agent.
12
-
13
- ## 0. Choose the engine
14
-
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
- - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
- - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
- - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
20
-
21
- ## 1. Resolve the task
22
-
23
- Resolve the remaining task argument or the in-context task (`mcp__xevy__find_task` / `find_task`). If ambiguous, ask which task. Read existing specs, subtasks, and notes.
24
-
25
- ## 2A. Local workflow (default)
26
-
27
- ### Decisions gate
28
-
29
- Call `mcp__xevy__list_task_decisions`. If any decision is **open**, review the questions together using their preset choices and explanations, record each human answer with `mcp__xevy__answer_decision`, and fold the answers into the analysis. Never guess or bypass an open decision.
30
-
31
- ### Inspect the codebase
32
-
33
- Read the relevant files, including callers, callees, and similar patterns. Identify whether the task involves UI changes; if so, study existing UI patterns and record a `UI/UX Flow` note with `mcp__xevy__create_task_note`. Base decisions on established patterns and ask only about genuine ambiguity.
34
-
35
- Complete investigation, feasibility checks, and validation of the proposed approach during Analyze/Plan preparation. Record findings and actual unresolved questions here. Later numbered plans and subtasks contain concrete code changes; post-execution verification, QA, and review belong to separate handoff notes and workflow.
36
-
37
- ### Write the Analysis
38
-
39
- Use `mcp__xevy__update_task` to append a `## Analysis` section without replacing the user's original request:
40
-
41
- - **Overview:** plain-language summary, before/after behaviour, user impact, and key decisions.
42
- - **Technical Implementation:** affected files/modules, API/data/UI changes, assumptions, risks, and verification approach.
43
- - Estimate `storyPoints` (1 trivial · 2 small · 3 medium · 5 large · 8 XL · 13 epic) and set it.
44
- - Finish inspecting the code and similar patterns, then gather all meaningful human questions together before implementation. Persist each through `mcp__xevy__create_decision` with `raisedAtStage: "analyze"`, preset choices, exactly one `recommended: true` choice per question, evidence/rationale in explanations, and necessary branching follow-ups. Resolve routine choices from the code. If the user is present, collect answers together through the host's user-question mechanism and record each with `answer_decision` and `answerSource: "human"`.
45
-
46
- ### Review and correct
47
-
48
- Re-read the Analysis against the actual code. Confirm every claim is accurate, affected files exist, and risks and acceptance criteria are concrete. Fix every gap or inaccuracy before finishing. Call `mcp__xevy__list_task_decisions` again and surface any decision that remains open.
49
-
50
- Report a PASS/PARTIAL verdict, what you corrected, any open decisions, and the task URL. Do not push the user to the next phase.
51
-
52
- ## 2B. Cloud workflow (`--cloud`)
53
-
54
- ### Run the server action
55
-
56
- - Call `mcp__xevy__start_ai_action({ taskId, action: "analyze", stream: true })`; always pass `stream: true`. The call blocks and streams live per-step progress, so report progress as it arrives. Do not use fire-and-forget or sleep/manual polling loops.
57
- - Only if the streamed call returns before a terminal status because of a genuine client disconnect, resume with `mcp__xevy__get_ai_execution` until `succeeded | failed | cancelled` (use `list_ai_executions` to find the newest run if needed).
58
- - If it fails, read the captured output, report the error, and offer to retry or rerun `/xevy:analyze` without `--cloud`.
59
-
60
- ### Review and correct
61
-
62
- Act as the reviewer of the cloud result:
63
-
64
- - Re-read the task, specs, subtasks, and the Analysis section the agent wrote.
65
- - Confirm it covers the plain-language overview, before/after behaviour, user impact, affected files, API/data/UI changes, assumptions, risks, verification, and a `storyPoints` estimate. Inspect referenced code with Read/Grep rather than trusting the write-up.
66
- - Repair missing, inaccurate, or contradictory material with `mcp__xevy__update_task`; append or repair the Analysis and never delete the user's original request. Set `storyPoints` if absent.
67
-
68
- Report a PASS/PARTIAL verdict, what you corrected, and the task URL. Do not push the user to the next phase.