菜单
Look up YouTrack issues by ID or list open issues. Use this skill FIRST whenever someone mentions an issue ID (CUBEOS-72, MESHSAT-27) or asks about project status, open issues, or issue details. This is for INFORMATION — not implementation. Do NOT escalate lookup requests.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Meta-skill chaining /specify → /constitute → /plan → /tasks → spec-validation → dispatch-ready. Greenfield project from idea to parallel-dev-ready in one flow. Halts with clear remediation if any phase fails the DoD gate.
Phase C of greenfield project bootstrap. Produce constitution.md (5-15 non-negotiable articles) + steering/*.md (cross-cutting agent-wide rules). Pauses for operator review before exit.
Phase D of greenfield project bootstrap. Produce design.md + data-model.md + contracts/{openapi,asyncapi,schemas/*} + adr/NNNN-*.md. Validates contracts via swagger-cli/asyncapi/ajv before exit.
Phase B of greenfield project bootstrap. Interview the operator to produce PROJECT.json + PROJECT.md + spec/NNN-*/requirements.md (EARS-only) + acceptance/*.feature scenarios. Iterates until ears-lint.py passes.
Phase E of greenfield project bootstrap. Atomize design.md + contracts into tasks.json with files_owned + dependencies + acceptance_test + risk_score per task. Iterates until task-dag-validate passes.
Query code graph database for function callers, callees, dependencies, and dead code in CubeOS and MeshSat repos.
| name | youtrack-lookup |
| description | Look up YouTrack issues by ID or list open issues. Use this skill FIRST whenever someone mentions an issue ID (CUBEOS-72, MESHSAT-27) or asks about project status, open issues, or issue details. This is for INFORMATION — not implementation. Do NOT escalate lookup requests. |
| allowed-tools | Bash |
| user-invocable | true |
| metadata | {"openclaw":{"always":true}} |
This skill looks up issue information from YouTrack. Use it for ANY question about issues.
./skills/yt-get-issue.sh CUBEOS-72./skills/yt-get-issue.sh CUBEOS-31./skills/yt-list-issues.sh "project: CUBEOS State: Open"./skills/yt-list-issues.sh "project: CUBEOS meshsat State: Open"./skills/yt-get-issue.sh CUBEOS-48./skills/yt-get-comments.sh CUBEOS-4Step 1: Run the appropriate command using the Bash tool:
# Get issue details
./skills/yt-get-issue.sh CUBEOS-72
# List open issues
./skills/yt-list-issues.sh "project: CUBEOS State: Open"
# List MeshSat issues (MeshSat = CUBEOS issues with "meshsat" in title)
./skills/yt-list-issues.sh "project: CUBEOS meshsat State: Open"
# Get comments
./skills/yt-get-comments.sh CUBEOS-4
Step 2: Read the output and answer the user's question based on it.
./skills/yt-update-state.sh CUBEOS-4 "In Progress"
./skills/yt-post-comment.sh CUBEOS-4 "comment text"
./skills/yt-create-issue.sh CUBEOS "summary" "description"