@xevy/skills 0.1.23 → 0.1.24

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. Cloud (server Web Agent) by default; '-here' variants run locally in this Claude Code session. Claude reviews and corrects the result after every action.",
5
- "version": "0.1.23",
5
+ "version": "0.1.24",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.23",
3
+ "version": "0.1.24",
4
4
  "description": "Install Xevy agent skills and MCP for Cursor, Claude Code, Codex, and other coding agents — one command via npx skills + add-mcp.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: mark-ready
3
- description: Mark a task ready for work — answer any open questions (decisions) first, then move its status to ready. Analyze is optional; this is the human gate that promotes a task from draft → ready. Runs locally in this session (no cloud agent, no code changes).
3
+ description: Submit a prepared draft to refinement — answer open decisions first, then move draft → ready. Ready hands the task to the configured Refine owner and may start AI Analyze/Plan.
4
4
  argument-hint: "[task]"
5
5
  disable-model-invocation: true
6
6
  allowed-tools: "Read Bash mcp__xevy__find_task mcp__xevy__list_task_decisions mcp__xevy__answer_decision mcp__xevy__update_task_status"
@@ -8,13 +8,13 @@ allowed-tools: "Read Bash mcp__xevy__find_task mcp__xevy__list_task_decisions mc
8
8
 
9
9
  # /xevy:mark-ready — answer open questions, then mark the task ready
10
10
 
11
- This is the **human gate** that promotes a task from `draft` → `ready`. Analyze is optional, so a task does not need an Analysis section to become ready. This command runs locally in this session: it does **not** start a cloud agent, write code, or touch git — it only resolves open questions and flips the status.
11
+ This is the **human submission gate** from `draft` → `ready`. Draft is preparation-only. Ready hands the task to the configured Refine owner; when that owner is AI, server automation may start Analyze and Plan after the status change.
12
12
 
13
13
  ## 1. Resolve the task
14
14
  Resolve from `$ARGUMENTS` (`mcp__xevy__find_task` by code) or the in-context task. If ambiguous, ask which task — never guess.
15
15
 
16
16
  ## 2. Check the current status
17
- Read the resolved task's status. `mark-ready` only promotes a task that is in **`draft`**. If it is already `ready` or further along (`in_progress` / `for_review` / `for_qa` / `done`), STOP and report the current status — do **NOT** move it backwards. Continue only when the status is `draft`.
17
+ Read the resolved task's status. `mark-ready` only promotes a task that is in **`draft`**. If it is already `ready` or further along (`planned` / `in_progress` / `for_review` / `for_qa` / `done`), STOP and report the current status — do **NOT** move it backwards. Continue only when the status is `draft`.
18
18
 
19
19
  ## 3. Answer open questions (MANDATORY gate)
20
20
  - Call `mcp__xevy__list_task_decisions` for the task.
@@ -23,4 +23,4 @@ When the host supports subagents, dispatch a **plan-reviewer** to cross-check ev
23
23
  When planning surfaces a genuine open question a human must resolve, record it with `mcp__xevy__create_decision` (preset choices + explanation) rather than guessing — it gates execution until answered.
24
24
 
25
25
  ## 4. Review & correct (MANDATORY)
26
- Confirm the final plan is complete and feasible against the actual code; fix any remaining gap before finishing. Post-check: call `mcp__xevy__list_task_decisions` — if any decision is still open, surface it. Then call `mcp__xevy__get_process_owners`: if the task is still `draft` and the Refine owner is `ai`, automatically call `mcp__xevy__update_task_status({ taskId, status: "ready" })`; if Refine is human-owned, leave it draft for the user to move manually. Do not start execution as part of local planning. Report a PASS/PARTIAL verdict, the matrix summary, any open decisions, the resulting status, and the task URL.
26
+ Confirm the final plan is complete and feasible against the actual code; fix any remaining gap before finishing. Post-check: call `mcp__xevy__list_task_decisions` — if any decision is still open, surface it. 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 performed as the configured Refine work for a Ready task, completion moves it to Planned through the normal server-owned Process Owner flow. Do not start execution as part of local planning. Report a PASS/PARTIAL verdict, the matrix summary, any open decisions, the resulting status, and the task URL.