@xevy/skills 0.1.52 → 0.1.53
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/plugin.json +1 -1
- package/README.md +1 -1
- package/package.json +1 -1
- package/skills/computer/SKILL.md +10 -6
- package/skills/create-artifact/SKILL.md +8 -6
- package/skills/create-xevy-task/SKILL.md +1 -1
- package/skills/execute/SKILL.md +4 -3
- package/skills/fix/SKILL.md +2 -2
- package/skills/generate-guide/SKILL.md +7 -3
- package/skills/generate-image/SKILL.md +8 -5
- package/skills/plan/SKILL.md +8 -6
|
@@ -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.
|
|
5
|
+
"version": "0.1.53",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Xevy"
|
|
8
8
|
},
|
package/README.md
CHANGED
|
@@ -136,7 +136,7 @@ Use generate-guide to make docs/guides/customer-form/manual.md with screenshots
|
|
|
136
136
|
|
|
137
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.
|
|
138
138
|
|
|
139
|
-
The package version is `0.1.
|
|
139
|
+
The package version is `0.1.53`. Run `npx @xevy/skills update -y` after that version is published.
|
|
140
140
|
|
|
141
141
|
## Security
|
|
142
142
|
|
package/package.json
CHANGED
package/skills/computer/SKILL.md
CHANGED
|
@@ -23,7 +23,7 @@ For browser work, use tab-scoped browser actions when the companion advertises t
|
|
|
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
|
|
|
26
|
-
Create a task-owned tab with `browser.newTab {url}` before parallel browser work, then use `browser.tabs`, `browser.navigate`, `browser.snapshot`, `browser.inspect`, `browser.click`, `browser.scroll`, `browser.type`, and `browser.key` as needed. `browser.snapshot {tabId,fullPage:true}` captures a bounded full page; `browser.inspect {tabId,selector?,limit?}` returns page title, URL, and bounded element metadata without running an arbitrary script. `browser.closeTab {tabId}` closes a tab owned by your session. A second agent cannot change a tab another agent owns; use a separate tab. Read every command result and
|
|
26
|
+
Create a task-owned tab with `browser.newTab {url}` before parallel browser work, then use `browser.tabs`, `browser.navigate`, `browser.snapshot`, `browser.inspect`, `browser.click`, `browser.scroll`, `browser.type`, and `browser.key` as needed. `browser.snapshot {tabId,fullPage:true}` captures a bounded full page; `browser.inspect {tabId,selector?,limit?}` returns page title, URL, and bounded element metadata without running an arbitrary script. `browser.closeTab {tabId}` closes a tab owned by your session. A second agent cannot change a tab another agent owns; use a separate tab. Read every terminal command result and request a fresh snapshot after input. Use its saved reference and server evaluation to verify the changed page. Successful input dispatch establishes execution; verify the application outcome separately. Browser coordinates belong to the selected tab viewport; they are distinct from desktop screen coordinates. Prefer `browser.snapshot` for evidence because it captures the tab without unrelated desktop windows. `browser.disconnect` releases this session's browser connection; it closes a managed browser only when no other session uses it. Follow the tool's current schema and capability list, since older companion versions may offer desktop actions only.
|
|
27
27
|
|
|
28
28
|
## Observe, act, verify
|
|
29
29
|
|
|
@@ -33,7 +33,7 @@ For file transfer, use absolute paths and chunks of at most 192 KiB. Download wi
|
|
|
33
33
|
|
|
34
34
|
### Recover an expired command result
|
|
35
35
|
|
|
36
|
-
Poll `computer_command` to terminal status promptly and
|
|
36
|
+
Poll `computer_command` to terminal status promptly. Successful Browser/Desktop snapshots are saved privately and evaluated server-side before the tool returns their immutable `image` handle and `analysisStatus`. Retain the command ID, `image.reference`, attachment/version/hash, and verified `localFilePath` when returned. Temporary capture bytes expire after 60 seconds, while a saved capture can be reused under current session authority. Shell output and file bytes remain ephemeral bulk results. A terminal command may return `resultExpired: true` and an optional content-free `command.receipt`; an expired result leaves the recorded command status intact.
|
|
37
37
|
|
|
38
38
|
A receipt is scoped to its creating session and current generation. Successful `file.uploadStart` receipts carry `{transferId,nextOffset,maxChunkBytes}`; `file.uploadChunk` receipts carry `{transferId,nextOffset,bytesWritten}`; `file.uploadCommit` carries `{committed:true}`; `file.uploadCancel` carries `{transferId,cancelled:true}`. Match the command ID, action, session ID and generation before using one. Resume an upload from its acknowledged `nextOffset` with the saved local bytes and checksum. A receipt reports acknowledged progress at that command; inspect later command results before choosing an offset when later chunks were queued. A commit receipt establishes that commit executed; inspect `file.stat` and download/check the destination when its content matters.
|
|
39
39
|
|
|
@@ -44,7 +44,7 @@ When the result expires, use the safe receipt to reconcile owned work. Never rep
|
|
|
44
44
|
### Verify desktop actions
|
|
45
45
|
|
|
46
46
|
1. Request `desktop.monitors` and `desktop.windows` through `computer_action`, then read their `computer_command` results. Select the actual target window and monitor.
|
|
47
|
-
2. Request `desktop.snapshot
|
|
47
|
+
2. Request `desktop.snapshot`, then read the saved image handle and server analysis from `computer_command`. Ask a specific question through `instructions`. For small controls, repeat `computer_command` with the same command ID and a normalized `region: {x,y,width,height}` to evaluate a focused crop of the saved original. Prefer current window/control metadata where available. Map evaluated bounds to the original screenshot and monitor origin; desktop actions use physical pixels in global desktop coordinates.
|
|
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.
|
|
@@ -52,7 +52,11 @@ When the result expires, use the safe receipt to reconcile owned work. Never rep
|
|
|
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
|
|
55
|
+
Screenshot command responses carry the command envelope, private `capture` metadata, immutable `image` handle, and `analysisStatus`. Read `analysis` when the status is `ready`; `failed` or `pending` keeps the original image reference available for a retry. Supply task-specific `instructions`, use a focused normalized `region` for details, or `analyze: false` when saving evidence without evaluation. The server uses a bounded analysis copy or crop and preserves the original image bytes. `analysisDimensions` records original dimensions, crop offsets, and scale; evaluated target bounds use the original coordinate space. Use a viewport capture for browser clicks, since full-page image coordinates span the document.
|
|
56
|
+
|
|
57
|
+
Keep image bytes outside the main agent context. A returned local path identifies a verified file in the registered `artifact_workspace`; consume it with local helpers when composing artifacts. `computer_save_capture` reuses the saved original and returns stable capture metadata. An expired temporary result requires a fresh snapshot only when the original has never been saved or current authority no longer permits reuse. Repeated successful saves and evaluations use the same capture, so an analysis failure provides no reason to recapture or regenerate.
|
|
58
|
+
|
|
59
|
+
For HTML publication, use `<img src="xevy-image:ATTACHMENT_UUID@VERSION">` with the returned reference and call `computer_create_guide`. The tool also accepts original `xevy-capture:ATTACHMENT_UUID` references. It verifies current ownership, session, project, generation and permissions before embedding exact original bytes. A mixed guide may include authorized uploaded/generated `xevy-image:` sources from the same project; Computer sources retain their session checks. Shell and file responses remain JSON command results; decode file chunks locally and verify checksums. A successful tool request establishes transport; terminal status and relevant evidence establish the operation result.
|
|
56
60
|
|
|
57
61
|
Only after reading terminal operation commands and the relevant final evidence, record the verified result with:
|
|
58
62
|
|
|
@@ -81,8 +85,8 @@ Enabled action/application block rules govern every action. Report the matching
|
|
|
81
85
|
|
|
82
86
|
Use an authorized account and safe test fixtures. Keep credentials in the existing authenticated session or approved credential mechanism. User authorization governs external writes: a walkthrough or test uses the agreed test environment and records. Unexpected production changes, customer messages, financial transactions, or destructive writes require their own authorization.
|
|
83
87
|
|
|
84
|
-
Keep passwords, tokens, typed values, screenshots, raw keys, pointer trails, and personal data out of operation summaries and diagnostic logs.
|
|
88
|
+
Keep passwords, tokens, typed values, screenshots, raw keys, pointer trails, and personal data out of operation summaries and diagnostic logs. Temporary screen transport and bulk command results remain bounded in memory and expire. Retain saved image references and use their server analysis under current authority. 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
89
|
|
|
86
|
-
For an explicitly requested guide,
|
|
90
|
+
Snapshots used for authorized observation are saved privately. For an explicitly requested guide, select only the necessary authentic screenshots from safe fixtures and package their original references as authorized by [generate-guide](../generate-guide/SKILL.md). 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
91
|
|
|
88
92
|
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.
|
|
@@ -94,7 +94,7 @@ The built-in helper deliberately keeps the Artifact in an opaque sandbox. Absolu
|
|
|
94
94
|
|
|
95
95
|
- Make the main information or interaction immediately clear.
|
|
96
96
|
- Use semantic HTML, visible keyboard focus, labelled controls, sufficient contrast, responsive layout, and `prefers-reduced-motion` where motion is present.
|
|
97
|
-
- Use system fonts, inline SVG, CSS, and data URLs
|
|
97
|
+
- Use system fonts, inline SVG, CSS, saved `xevy-image:ATTACHMENT_UUID@VERSION` references in image sources, and locally composed data URLs. Do not reference CDNs, remote fonts, images, APIs, iframes, server-submitting forms, or any script or stylesheet other than the optional built-in Xevy report theme above.
|
|
98
98
|
- Keep state local. Do not assume cookies, same-origin access, parent-page DOM access, or unrestricted storage. The manifest-selected built-in script may use only its documented one-way print `postMessage`; custom Artifact code must not inspect or control the parent.
|
|
99
99
|
- Escape user-supplied values inserted into markup or JavaScript.
|
|
100
100
|
- Include real content. Do not leave placeholder controls, lorem ipsum, TODOs, or buttons that do nothing.
|
|
@@ -121,7 +121,7 @@ Return strict JSON, not JavaScript or a fenced code block. Use a stable top-leve
|
|
|
121
121
|
|
|
122
122
|
### PDF
|
|
123
123
|
|
|
124
|
-
Store real PDF bytes only. Use `sourceUrl` for an existing public PDF or `
|
|
124
|
+
Store real PDF bytes only. Use `sourceUrl` for an existing public PDF, or `filePath` / direct upload for a locally generated PDF. Stream its bytes with a local helper. Never place PDF-looking text in `textContent`; Xevy validates the `%PDF-` signature.
|
|
125
125
|
|
|
126
126
|
### Excalidraw
|
|
127
127
|
|
|
@@ -133,13 +133,15 @@ Before saving, verify that the selected format parses, the requested content is
|
|
|
133
133
|
|
|
134
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 an HTML guide with saved Computer screenshots, use
|
|
136
|
+
For an HTML guide with saved Computer screenshots, use `<img src="xevy-image:ATTACHMENT_UUID@VERSION" alt="Step result">` references and call `computer_create_guide`. Original `xevy-capture:ATTACHMENT_UUID` references also work. The tool checks current session/project authority and embeds exact original bytes. Mixed guides may include authorized project-uploaded/generated references while Computer images retain their session checks. Verify the stored version, images and exact viewer URL.
|
|
137
|
+
|
|
138
|
+
For other project images, retain the immutable handle returned by upload/generation or `analyze_attachment`, and embed its `image.reference` in HTML image sources. `create_attachment` and direct-upload completion resolve authorized original versions server-side. Analysis runs against a separate resized copy or focused crop; artifacts use the full original. Retry failed/pending evaluation against the saved version. Public artifacts require publicly shared image sources; private Computer images stay in the fenced Computer guide path. Use returned local paths with local composition helpers for other formats, preserving originals and keeping bytes outside main-agent context.
|
|
137
139
|
|
|
138
140
|
For other project Artifacts, prefer file transfer so the file bytes stay outside model context and MCP JSON arguments:
|
|
139
141
|
|
|
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.
|
|
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.
|
|
142
|
-
3. Use `create_attachment` with `textContent
|
|
142
|
+
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 accepted files up to 100 MB; images are limited to 25 MB.
|
|
143
|
+
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 uploaded byte count, expands authorized HTML image references, and checks the final signature, embedded size and Artifact security state before the viewer URL becomes readable.
|
|
144
|
+
3. Use `create_attachment` with `textContent` for a small text-backed artifact or `sourceUrl` for an existing public binary when local transfer is unavailable. Export built-in image output to a local file with the host helper before uploading; keep binary/base64 bytes outside main-agent arguments.
|
|
143
145
|
|
|
144
146
|
Text-backed Artifacts remain limited to 10 MB after decoding for safe parsing and preview. Direct upload supports PDFs and other accepted files up to 100 MB. Never split one Artifact across calls or place a large file in base64 tool arguments.
|
|
145
147
|
|
|
@@ -12,7 +12,7 @@ Turn what just happened in this session into an Xevy task a **human developer or
|
|
|
12
12
|
|
|
13
13
|
## 1. Decide the mode
|
|
14
14
|
- **Evaluate the session.** Did the AI make code changes this session? Check git: `git status --short`, `git branch --show-current`, and `git log --oneline` for new commits. Read back the conversation for the user's goal, requirements, and any "must NOT" constraints.
|
|
15
|
-
- **Avoid duplicates.** Is this work already tracked by an Xevy task (
|
|
15
|
+
- **Avoid duplicates.** Is this work already tracked by an Xevy task (explicit session task/worktree context, a task code referenced in the conversation, `.xevy/project.json` context, or a match from `list_tasks`/`find_task`)? If yes, STOP and ask whether to **update that task** (description + status + notes) instead of creating a duplicate.
|
|
16
16
|
- Pick a mode:
|
|
17
17
|
- **Capture mode** (default when the AI changed code this session) → sections 2–5.
|
|
18
18
|
- **Ordinary mode** (no AI work to capture, or `$ARGUMENTS` clearly describes a brand-new unrelated task) → section 6.
|
package/skills/execute/SKILL.md
CHANGED
|
@@ -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__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
|
|
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"
|
|
7
7
|
---
|
|
8
8
|
|
|
9
9
|
# /xevy:execute — execute locally or in the cloud
|
|
@@ -20,7 +20,7 @@ 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 task and read its current numbered Plan and linked visualization.
|
|
23
|
+
- Resolve the task and read its current numbered Plan and linked visualization. Read the current Plan with `get_task_plan`. Show a short plan before substantial changes and wait for the user’s go-ahead. Continue approved work without asking again. Preserve original requirements and legacy history. An Analysis section and generated subtasks are never prerequisites.
|
|
24
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
|
|
@@ -39,7 +39,8 @@ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered P
|
|
|
39
39
|
|
|
40
40
|
- Record the current branch and directory. Derive a canonical branch `xevy/<TASK-ID>-<slug>` using the task code or the first eight characters of its UUID. Reuse an existing task branch; never create a second branch for the same task.
|
|
41
41
|
- Create or attach a git worktree in a sibling directory and change into it. When resuming, first merge the latest source branch (for example `git merge origin/main`). Do all work in the task worktree.
|
|
42
|
-
-
|
|
42
|
+
- Verify the absolute worktree path with `git rev-parse --show-toplevel` and its branch with `git branch --show-current` before editing. Keep the task code, UUID, title, absolute worktree path, and branch in the session context. On resume or after changing directories, verify and refresh that context before continuing.
|
|
43
|
+
- Pass the absolute worktree path as `cwd` to every worker, together with the task code, UUID, title, branch, and assigned file scope. Each worker verifies its working directory and branch before editing.
|
|
43
44
|
- Never commit or push on a protected branch (`master`, `main`, `develop`, `staging`); use only the `xevy/*` task branch.
|
|
44
45
|
|
|
45
46
|
### Implement
|
package/skills/fix/SKILL.md
CHANGED
|
@@ -30,11 +30,11 @@ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered A
|
|
|
30
30
|
|
|
31
31
|
### Locate the worktree
|
|
32
32
|
|
|
33
|
-
Find the existing task worktree and branch with `git worktree list`, matching by task code. The worktree must already exist; do not create a new branch. If none exists, report the missing worktree as blocked. Merge the latest source branch into the feature branch first to avoid divergence.
|
|
33
|
+
Find the existing task worktree and branch with `git worktree list`, matching by task code. The worktree must already exist; do not create a new branch. If none exists, report the missing worktree as blocked. Verify the absolute worktree path with `git rev-parse --show-toplevel` and its branch with `git branch --show-current` before editing. Keep the task code, UUID, title, absolute worktree path, and branch in the session context; verify and refresh them on resume or after changing directories. Merge the latest source branch into the feature branch first to avoid divergence.
|
|
34
34
|
|
|
35
35
|
### Rework
|
|
36
36
|
|
|
37
|
-
Make the requested code fix in the worktree with the host's read/search/edit tools, or use a builder subagent with
|
|
37
|
+
Make the requested code fix in the worktree with the host's read/search/edit tools, or use a builder subagent with the verified absolute worktree path as `cwd`. Pass every worker the task code, UUID, title, branch, and assigned file scope; each worker verifies its working directory and branch before editing. Keep the change surgical and correct the root cause rather than symptoms. Commit coherent code milestones and update code subtasks through MCP; a committed implementation completes the code item without requiring verification, QA, or review completion.
|
|
38
38
|
|
|
39
39
|
Before editing UI pages, components, app shell, forms, or styling, follow `/xevy:xevy-design` and the project's `./.xevy/design.md`.
|
|
40
40
|
|
|
@@ -18,7 +18,9 @@ Use the host's available browser observation tools for web journeys, or [compute
|
|
|
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
|
-
|
|
21
|
+
Poll each snapshot with `computer_command` promptly. Successful Computer snapshots return a saved private original and a separate server evaluation. Retain the command ID, immutable `image.reference` (`xevy-image:ATTACHMENT_UUID@VERSION`), attachment ID, version, SHA256, dimensions and capture time. Retain the verified local path when the runtime returns one. `computer_save_capture` reuses that original; repeated successful saves return its stable metadata. For a host capture tool, save its actual local output with `create_attachment({filePath, ...})` or direct upload, then use `analyze_attachment` for the separate API evaluation.
|
|
22
|
+
|
|
23
|
+
Ask the evaluation a specific question about the step's visible controls and expected result. A normalized `region: {x,y,width,height}` requests a focused crop for small labels or controls while the original remains unchanged. Interpret bounds using `analysisDimensions` and the original coordinate space; use a viewport snapshot for browser clicks. An analysis status of `failed` or `pending` preserves the saved reference. Retry evaluation against that reference and record the step as uncertain until evidence establishes its result. Keep raw image bytes outside the main agent context; local helpers consume saved paths when composing files.
|
|
22
24
|
|
|
23
25
|
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.
|
|
24
26
|
|
|
@@ -28,7 +30,7 @@ Screenshots must show the step they support on the tested build. Generated illus
|
|
|
28
30
|
|
|
29
31
|
Test every numbered step from its documented starting state. Exercise the intended outcome and relevant downstream journeys, such as reopening a saved record or using the next feature that consumes it. Record any error, block, uncertain write, or mismatch. On command timeout, inspect the app and command result before retrying; avoid duplicate writes.
|
|
30
32
|
|
|
31
|
-
For Computer commands, poll terminal results while their 60-second
|
|
33
|
+
For Computer commands, poll terminal results while their temporary 60-second transport is available so snapshot originals can be saved automatically. Saved captures remain reusable under current session authority; their server evaluation can be retried independently. If `resultExpired` appears, follow [computer](../computer/SKILL.md) to reconcile an optional content-free `command.receipt`. Upload receipts retain transfer IDs, progress offsets or terminal flags within bounded memory; they provide no screenshot, file-content or application proof. An unavailable receipt after restart, expiry, eviction or a control change leaves recovery dependent on fresh evidence and owned cleanup. Keep the step uncertain until its effect is verified; preserve its operation ID and avoid replaying upload start or commit to recover an acknowledgement.
|
|
32
34
|
|
|
33
35
|
When a failure belongs to the repository and repair is already authorized, use the isolated task branch/worktree and current engine. Reuse the task branch; keep unrelated work intact. Make a focused root-cause fix, run relevant repository checks, and refresh the existing test environment through its authorized local mechanism. The guide workflow grants no additional deploy or merge authority. For fixes outside approved scope, record the blocker and required decision while continuing independent verification.
|
|
34
36
|
|
|
@@ -42,7 +44,9 @@ Keep the copy-ready guide focused on the user's task: prerequisites, numbered ac
|
|
|
42
44
|
|
|
43
45
|
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
46
|
|
|
45
|
-
For Computer screenshots, build ordinary HTML with `<img src="xevy-
|
|
47
|
+
For Computer screenshots, build ordinary HTML with `<img src="xevy-image:ATTACHMENT_UUID@VERSION" alt="Observable step result">` using each returned immutable reference, then call `computer_create_guide`. It embeds exact original bytes after checking current Computer authority and project access. Original `xevy-capture:ATTACHMENT_UUID` references also work. The same guide can include authorized uploaded/generated image references from the project. Submit the small HTML template with inline CSS; image bytes stay outside model arguments.
|
|
48
|
+
|
|
49
|
+
For other saved images, HTML `create_attachment` and direct-upload completion expand `xevy-image:` references server-side with authorized version checks. Use an actual local file and a local helper for Markdown/PDF composition; stream the finished file with `filePath` or prepare/PUT/complete. Ensure the published viewer resolves every Markdown image. For PDF, generate real PDF bytes from the finished guide and inspect the rendered pages through the available file evaluation/viewer path. Follow [create-artifact](../create-artifact/SKILL.md) for validation, final embedded size limits, viewer security and upload paths.
|
|
46
50
|
|
|
47
51
|
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.
|
|
48
52
|
|
|
@@ -36,10 +36,12 @@ Use Xevy for Gallery storage regardless of which feature generates the image. Do
|
|
|
36
36
|
- Pass the user's image description and any supported reference images directly to that feature.
|
|
37
37
|
- After generation, call Xevy's `create_attachment` to save the output in the Gallery:
|
|
38
38
|
- Prefer `sourceUrl` when the built-in feature returns a public `http(s)` image URL.
|
|
39
|
-
-
|
|
39
|
+
- For a local output, use `create_attachment` with `filePath` from the registered `artifact_workspace` or another permitted local path. Through MCP, use prepare/PUT/complete so a local helper streams the file bytes. A local path belongs in `filePath`; `sourceUrl` accepts public HTTP(S) URLs.
|
|
40
|
+
- If the host returns only a displayed image or data URL, use its native export/download helper to materialize a local file before transfer. When no byte-preserving export is available, report the Gallery save blocker. Keep image bytes outside main-agent text and tool arguments.
|
|
40
41
|
- Pass `mimeType`, a friendly `fileName`, the prompt as `description`, optional `taskId`, and `public: true`.
|
|
41
|
-
-
|
|
42
|
-
-
|
|
42
|
+
- Select one transfer source. Images are limited to 25 MB; keep the original output unchanged.
|
|
43
|
+
- Retain the returned `image.reference`, version/hash and verified local path when available. Call `analyze_attachment` with the saved attachment/version and a concise question about whether the visible result matches the prompt. Use a focused `region` when details need inspection.
|
|
44
|
+
- Report the confirmed Gallery URL and file name. Ground statements about visible content in successful API analysis. A failed evaluation leaves the stored original available for a retry.
|
|
43
45
|
- If attachment creation fails, report that the image was generated but not saved to the Gallery. Do not claim the request completed successfully.
|
|
44
46
|
|
|
45
47
|
## 5. Xevy path (explicit or fallback)
|
|
@@ -50,6 +52,7 @@ Use Xevy for Gallery storage regardless of which feature generates the image. Do
|
|
|
50
52
|
- `prompt`
|
|
51
53
|
- optional `model`, `size`, and `fileName`; `size` accepts `512`, `1K`, `2K`, `4K`, or explicit pixels such as `1024x1024`
|
|
52
54
|
- optional resolved `taskId`
|
|
53
|
-
2.
|
|
55
|
+
2. Read the returned immutable image handle and `analysisStatus`. Xevy saves the original and evaluates a bounded copy against the prompt through its vision API. Use successful analysis to describe the visible result.
|
|
56
|
+
3. Report the confirmed Gallery URL and file name. If evaluation fails or remains pending, retry `analyze_attachment` against the saved version; keep the successful generation and its reference.
|
|
54
57
|
|
|
55
|
-
`generate_image`
|
|
58
|
+
`generate_image` returns Gallery metadata plus `image: {attachmentId, versionNumber, sha256, mimeType, sizeBytes, reference, viewUrl}`, `analysisStatus`, and `analysis` when evaluation succeeds. Runtime tools may also return a verified `localFilePath`. Embed its exact original reference in HTML as `<img src="xevy-image:ATTACHMENT_UUID@VERSION">`; the server resolves the bytes during authorized artifact creation. Xevy generation is a paid provider call: generate once per request and do not retry after success. Never print API keys or environment values. On failure, surface the tool's error without inventing a cause.
|
package/skills/plan/SKILL.md
CHANGED
|
@@ -3,10 +3,10 @@ name: plan
|
|
|
3
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_attachment mcp__xevy__create_attachment_version mcp__xevy__get_task_plan
|
|
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__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 — inspect
|
|
9
|
+
# /xevy:plan — inspect and visualize
|
|
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
|
|
|
@@ -41,19 +41,21 @@ Plan creates zero subtasks. Preserve existing subtasks and treat them as legacy
|
|
|
41
41
|
|
|
42
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
|
-
### Review and
|
|
44
|
+
### Review and present the Plan
|
|
45
45
|
|
|
46
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
|
-
|
|
48
|
+
Read the current Plan with `get_task_plan`. In chat show only the short numbered titles, the task link, and visualization link. Keep the technical details in Xevy. For the example above, chat shows:
|
|
49
49
|
|
|
50
50
|
1. Remove Analyze.
|
|
51
51
|
2. Simplify Plan.
|
|
52
52
|
|
|
53
|
-
|
|
53
|
+
Show a short plan before substantial changes and wait for the user’s go-ahead. Continue approved work without asking again.
|
|
54
|
+
|
|
55
|
+
Explain unresolved decisions or missing visualization separately and keep affected work blocked. Draft remains preparation until explicitly submitted to Ready.
|
|
54
56
|
|
|
55
57
|
## 2B. Cloud workflow (`--cloud`)
|
|
56
58
|
|
|
57
59
|
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.
|
|
58
60
|
|
|
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
|
|
61
|
+
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 guidance as local planning. The server owns status automation.
|