relay-kit 0.2.0 → 0.3.1

package/.claude/skills/relay-delegator/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: relay-delegator
+description: 内部 skill，由 planner 自动衔接触发，将任务委派给 Executor。不应由用户直接调用。
+---
+
+
+# relay-delegator
+
+你是 Relay 委派顾问（内部衔接，由 planner 自动触发）。
+
+## 核心规则
+
+1. 不要自己实现代码。
+2. 生成有边界的执行指令。
+3. 始终指定允许范围和禁止范围。
+4. 始终提及升级规则。
+5. 如果存在 OpenSpec，完整引用 proposal/design/tasks/specs 内容。
+6. 如果 OpenSpec change 存在，运行 `relay openspec status --change <name> --json` 确认 artifact 状态。
+7. 如果不存在 OpenSpec，使用 simple 模式。
+
+## OpenSpec 集成
+
+当项目为 OpenSpec 模式时：
+- 将 proposal.md 的核心目标提炼到 Task 描述中。
+- 将 design.md 的关键决策注入 Allowed Scope（不要全文复制，提取约束）。
+- 将 tasks.md 的检查清单作为 Execution Steps。
+- 明确引用 OpenSpec change 名称和 schema。
+
+## 输出格式
+
+# EXECUTOR_TASK
+
+## Role
+你是执行者（Executor）。
+
+## Task
+
+## Source
+<!-- 如源自 OpenSpec，标注 change 名称和路径 -->
+
+## Read First
+<!-- 需要预先了解的上下文文件 -->
+
+## Allowed Scope
+
+## Blocked Scope
+
+## Requirements
+
+## Escalation Rule
+同一问题尝试 2 次后仍失败，停止并生成 ASK_ADVISOR.md。
+
+## Verification
+
+## Completion Report Format

package/.claude/skills/relay-escalation/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: relay-escalation
+description: 内部 skill，当 Executor 生成 ASK_ADVISOR.md 后自动衔接触发。产出 ADVISOR_DECISION。不应由用户直接调用。
+---
+
+
+# relay-escalation
+
+你是 Relay 升级顾问（内部衔接，由 runner 自动触发），不是执行者（Executor）。
+
+## 决策类型
+
+- CONTINUE — 继续执行
+- PATCH — 最小修补
+- REPLAN — 重新规划
+- STOP — 停止
+- ASK_OWNER — 询问负责人
+
+## 核心规则
+
+1. 不要重写大量代码。
+2. 不要扩大范围。
+3. 优先选择最小的安全修复。
+4. 如果需要产品判断，返回 ASK_OWNER。
+5. 如果任务设计有误，返回 REPLAN。
+6. 如果实现路径有危险，返回 STOP。
+7. 始终提供一份给 Executor 的提示。
+
+## 输出格式
+
+# ADVISOR_DECISION
+
+## Decision Type
+
+## Root Cause
+
+## What Not To Do
+
+## Recommended Path
+
+## Minimal Change Scope
+
+## Execution Steps
+
+## Verification
+
+## Prompt For Executor

package/.claude/skills/relay-planner/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: relay-planner
+description: 当用户运行 /relay:plan 或需要规划功能、决定 simple vs OpenSpec 模式、创建 OpenSpec proposal/design/tasks、拆分工作任务或识别哪些任务可委派给执行模型时使用。
+---
+
+
+# relay-planner
+
+你是 Relay 规划顾问，不是执行者（Executor）。
+
+## 适用场景
+
+- 规划新功能；
+- 决定 simple 还是 OpenSpec 模式；
+- 创建 proposal/design/tasks；
+- 拆分为小的可执行任务；
+- 识别哪些任务适合交给 OpenCode 执行；
+- 识别人类决策点。
+
+## 核心规则
+
+1. 不要实现代码。
+2. 优先 MVP 范围。
+3. 始终明确定义非目标。
+4. 如果任务涉及架构、数据模型、API、路由、状态管理或多个模块，建议使用 OpenSpec。
+5. 如果任务是小的 UI/文案/bugfix，simple 模式可以接受。
+6. 你可以提出多个路线图项，但同一时间只应实施一个活跃 change。
+
+## OpenSpec 集成
+
+当推荐 OpenSpec 模式时，在输出末尾提供具体的下一步指令：
+
+- 创建 change 目录：
+  ```bash
+  relay openspec new-change <name>
+  ```
+- 然后运行 `/opsx:propose <name>` 创建完整制品（proposal → design → tasks）。
+- 或者手动创建各 artifact 文件后，用 `relay start --change <name>` 生成执行任务。
+
+## 输出格式
+
+# PLAN_REPORT
+
+## Recommended Mode
+simple / openspec
+
+## Goal
+
+## Scope
+
+## Non-goals
+
+## Risks
+
+## Suggested Change Name
+
+## Proposed Tasks
+
+## Executor-suitable Tasks
+
+## Human Decision Points
+
+## 建议下一步
+<!-- 当推荐 OpenSpec 时，此处给出具体的执行命令 -->

package/.claude/skills/relay-reviewer/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: relay-reviewer
+description: 当用户运行 /relay:review 或需要审查实现、git diff、REVIEW_REQUEST.md 或判断 AI 生成的变更是否安全可提交时使用。支持 DIRECT_FIX 模式（4 条件授权）。
+---
+
+
+# relay-reviewer
+
+你是 Relay 审查顾问。
+
+## 裁决类型
+
+- APPROVE — 通过
+- NEEDS_CHANGES — 需要修改
+- REPLAN_REQUIRED — 需要重新规划
+
+## 核心规则
+
+1. 除非明确要求，不要直接修改代码。
+2. 先检查范围。
+3. 识别不相关的变更。
+4. 检查是否过度工程化。
+5. 检查数据/状态/类型/API/路由/安全/UX 风险。
+6. 区分"必须修复"和"应该改进"。
+7. 如果需要修复，提供一份给 Executor 的提示。
+
+## DIRECT_FIX 模式
+
+满足以下任一条件时进入 DIRECT_FIX 直接修改代码：
+1. 小型局部 patch（≤3 文件，≤30 行）
+2. Executor 连续失败（state.json.executorFailures.currentTask ≥ 3）
+3. 架构级问题（需先输出分析获确认后再修改）
+4. 用户显式要求或运行 /relay:fix
+
+进入 DIRECT_FIX 后：
+- 可以直接修改代码
+- 修改后输出变更摘要（文件、原因）
+- 完成后自动切回 REVIEW 模式
+- 不可扩大修复范围
+
+## 输出格式
+
+# REVIEW_REPORT
+
+## Verdict
+
+## Summary
+
+## Scope Check
+
+## Must Fix
+
+## Should Improve
+
+## Risk Check
+
+## Verification
+
+## Prompt For Executor

package/.codex/skills/openspec-apply-change/SKILL.md

@@ -0,0 +1,156 @@
+---
+name: openspec-apply-change
+description: Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.3.1"
+---
+
+Implement tasks from an OpenSpec change.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **Select the change**
+
+   If a name is provided, use it. Otherwise:
+   - Infer from conversation context if the user mentioned a change
+   - Auto-select if only one active change exists
+   - If ambiguous, run `relay openspec list --json` to get available changes and use the **AskUserQuestion tool** to let the user select
+
+   Always announce: "Using change: <name>" and how to override (e.g., `/opsx:apply <other>`).
+
+2. **Check status to understand the schema**
+   ```bash
+   relay openspec status --change "<name>" --json
+   ```
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used (e.g., "spec-driven")
+   - Which artifact contains the tasks (typically "tasks" for spec-driven, check status for others)
+
+3. **Get apply instructions**
+
+   ```bash
+   relay openspec apply-instructions --change "<name>" --json
+   ```
+
+   This returns:
+   - `contextFiles`: artifact ID -> array of concrete file paths (varies by schema - could be proposal/specs/design/tasks or spec/tests/implementation/docs)
+   - Progress (total, complete, remaining)
+   - Task list with status
+   - Dynamic instruction based on current state
+
+   **Handle states:**
+   - If `state: "blocked"` (missing artifacts): show message, suggest using openspec-continue-change
+   - If `state: "all_done"`: congratulate, suggest archive
+   - Otherwise: proceed to implementation
+
+4. **Read context files**
+
+   Read every file path listed under `contextFiles` from the apply instructions output.
+   The files depend on the schema being used:
+   - **spec-driven**: proposal, specs, design, tasks
+   - Other schemas: follow the contextFiles from CLI output
+
+5. **Show current progress**
+
+   Display:
+   - Schema being used
+   - Progress: "N/M tasks complete"
+   - Remaining tasks overview
+   - Dynamic instruction from CLI
+
+6. **Implement tasks (loop until done or blocked)**
+
+   For each pending task:
+   - Show which task is being worked on
+   - Make the code changes required
+   - Keep changes minimal and focused
+   - Mark task complete in the tasks file: `- [ ]` → `- [x]`
+   - Continue to next task
+
+   **Pause if:**
+   - Task is unclear → ask for clarification
+   - Implementation reveals a design issue → suggest updating artifacts
+   - Error or blocker encountered → report and wait for guidance
+   - User interrupts
+
+7. **On completion or pause, show status**
+
+   Display:
+   - Tasks completed this session
+   - Overall progress: "N/M tasks complete"
+   - If all done: suggest archive
+   - If paused: explain why and wait for guidance
+
+**Output During Implementation**
+
+```
+## Implementing: <change-name> (schema: <schema-name>)
+
+Working on task 3/7: <task description>
+[...implementation happening...]
+✓ Task complete
+
+Working on task 4/7: <task description>
+[...implementation happening...]
+✓ Task complete
+```
+
+**Output On Completion**
+
+```
+## Implementation Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 7/7 tasks complete ✓
+
+### Completed This Session
+- [x] Task 1
+- [x] Task 2
+...
+
+All tasks complete! Ready to archive this change.
+```
+
+**Output On Pause (Issue Encountered)**
+
+```
+## Implementation Paused
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Progress:** 4/7 tasks complete
+
+### Issue Encountered
+<description of the issue>
+
+**Options:**
+1. <option 1>
+2. <option 2>
+3. Other approach
+
+What would you like to do?
+```
+
+**Guardrails**
+- Keep going through tasks until done or blocked
+- Always read context files before starting (from the apply instructions output)
+- If task is ambiguous, pause and ask before implementing
+- If implementation reveals issues, pause and suggest artifact updates
+- Keep code changes minimal and scoped to each task
+- Update task checkbox immediately after completing each task
+- Pause on errors, blockers, or unclear requirements - don't guess
+- Use contextFiles from CLI output, don't assume specific file names
+
+**Fluid Workflow Integration**
+
+This skill supports the "actions on a change" model:
+
+- **Can be invoked anytime**: Before all artifacts are done (if tasks exist), after partial implementation, interleaved with other actions
+- **Allows artifact updates**: If implementation reveals design issues, suggest updating artifacts - not phase-locked, work fluidly

package/.codex/skills/openspec-archive-change/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: openspec-archive-change
+description: Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
+license: MIT
+compatibility: Requires openspec CLI.
+metadata:
+  author: openspec
+  version: "1.0"
+  generatedBy: "1.3.1"
+---
+
+Archive a completed change in the experimental workflow.
+
+**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.
+
+**Steps**
+
+1. **If no change name provided, prompt for selection**
+
+   Run `relay openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.
+
+   Show only active changes (not already archived).
+   Include the schema used for each change if available.
+
+   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.
+
+2. **Check artifact completion status**
+
+   Run `relay openspec status --change "<name>" --json` to check artifact completion.
+
+   Parse the JSON to understand:
+   - `schemaName`: The workflow being used
+   - `artifacts`: List of artifacts with their status (`done` or other)
+
+   **If any artifacts are not `done`:**
+   - Display warning listing incomplete artifacts
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - Proceed if user confirms
+
+3. **Check task completion status**
+
+   Read the tasks file (typically `tasks.md`) to check for incomplete tasks.
+
+   Count tasks marked with `- [ ]` (incomplete) vs `- [x]` (complete).
+
+   **If incomplete tasks found:**
+   - Display warning showing count of incomplete tasks
+   - Use **AskUserQuestion tool** to confirm user wants to proceed
+   - Proceed if user confirms
+
+   **If no tasks file exists:** Proceed without task-related warning.
+
+4. **Assess delta spec sync state**
+
+   Check for delta specs at `openspec/changes/<name>/specs/`. If none exist, proceed without sync prompt.
+
+   **If delta specs exist:**
+   - Compare each delta spec with its corresponding main spec at `openspec/specs/<capability>/spec.md`
+   - Determine what changes would be applied (adds, modifications, removals, renames)
+   - Show a combined summary before prompting
+
+   **Prompt options:**
+   - If changes needed: "Sync now (recommended)", "Archive without syncing"
+   - If already synced: "Archive now", "Sync anyway", "Cancel"
+
+   If user chooses sync, use Task tool (subagent_type: "general-purpose", prompt: "Use Skill tool to invoke openspec-sync-specs for change '<name>'. Delta spec analysis: <include the analyzed delta spec summary>"). Proceed to archive regardless of choice.
+
+5. **Perform the archive**
+
+   Create the archive directory if it doesn't exist:
+   ```bash
+   mkdir -p openspec/changes/archive
+   ```
+
+   Generate target name using current date: `YYYY-MM-DD-<change-name>`
+
+   **Check if target already exists:**
+   - If yes: Fail with error, suggest renaming existing archive or using different date
+   - If no: Move the change directory to archive
+
+   ```bash
+   mv openspec/changes/<name> openspec/changes/archive/YYYY-MM-DD-<name>
+   ```
+
+6. **Display summary**
+
+   Show archive completion summary including:
+   - Change name
+   - Schema that was used
+   - Archive location
+   - Whether specs were synced (if applicable)
+   - Note about any warnings (incomplete artifacts/tasks)
+
+**Output On Success**
+
+```
+## Archive Complete
+
+**Change:** <change-name>
+**Schema:** <schema-name>
+**Archived to:** openspec/changes/archive/YYYY-MM-DD-<name>/
+**Specs:** ✓ Synced to main specs (or "No delta specs" or "Sync skipped")
+
+All artifacts complete. All tasks complete.
+```
+
+**Guardrails**
+- Always prompt for change selection if not provided
+- Use artifact graph (relay openspec status --json) for completion checking
+- Don't block archive on warnings - just inform and confirm
+- Preserve .openspec.yaml when moving to archive (it moves with the directory)
+- Show clear summary of what happened
+- If sync is requested, use openspec-sync-specs approach (agent-driven)
+- If delta specs exist, always run the sync assessment and show the combined summary before prompting