菜单
Inspect the current project's PRD and build queues, summarize lifecycle counts, and surface actionable queue-health signals without mutating work.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CodySwannGT/grist --skill lisa-queue-status命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Acceptance criteria definition. Gherkin user flows (Given/When/Then), error states, UX concerns, and empirical verification from the user perspective.
Build or Refactor large Rails controller files into clean, maintainable code. Use when a controller action exceeds ~10 lines, a controller has custom non-RESTful actions, or when the user asks to refactor, slim down, clean up, or organize a Rails controller. Applies patterns: service objects, query objects, form objects, controller concerns, presenters/decorators, and RESTful resource extraction.
Best practices for Ruby on Rails models, splitting code into well-organized, maintainable code. Use when a model exceeds ~100 lines, has mixed responsibilities, or when the user asks to refactor, extract, clean up, or organize a Rails model. Applies patterns: concerns, service objects, query objects, form objects, and value objects.
基于 SOC 职业分类
正在显示 SKILL.md
| name | lisa-queue-status |
| description | Inspect the current project's PRD and build queues, summarize lifecycle counts, and surface actionable queue-health signals without mutating work. |
/lisa:queue-status$lisa-queue-status or a plain-English request that matches this skill.Use the /lisa:queue-status skill to inspect the current project's configured PRD source and build tracker, report queue-health verdicts, and highlight actionable backlog or stuck-state signals. Use the user's surrounding request as this command's arguments.
Common operator usage:
/lisa:queue-status/lisa:queue-status queue=prd/lisa:queue-status queue=buildUse this when you need to answer:
/lisa:intake, /lisa:repair-intake, /lisa:automation-status, or /lisa:verify-prd?This surface is read-only in v1. Use it to understand whether the repo's PRD and build queues are idle, healthy, attention-needed, or misconfigured before deciding whether to run /lisa:intake, /lisa:repair-intake, /lisa:automation-status, /lisa:verify-prd, or deeper tracker-native investigation.
Quick interpretation guide:
IDLE: the queue resolved correctly and nothing actionable is waiting. No immediate Lisa action is required.HEALTHY: the queue resolved correctly and normal work is present. Follow the highlighted next step, usually /lisa:intake.ATTENTION_NEEDED: blocked, stalled, or aging work needs operator follow-up. Use the highlighted item and remediation hint to choose the next command, usually /lisa:repair-intake.MISCONFIGURED: queue resolution or lifecycle adoption is broken. Fix config, labels/statuses, or scheduler drift before trusting queue state.Highlighted-item semantics:
ready highlights usually point to /lisa:intake.blocked, stalled, or long-claimed highlights usually point to /lisa:repair-intake./lisa:verify-prd./lisa:automation-status before assuming the queue itself is the problem.