メニュー
Inspect one PRD or build item, explain how Lisa classifies it right now, and report the exact intake or repair gate affecting it. Read-only by default.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/CodySwannGT/grist --skill lisa-intake-explainコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
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.
| name | lisa-intake-explain |
| description | Inspect one PRD or build item, explain how Lisa classifies it right now, and report the exact intake or repair gate affecting it. Read-only by default. |
/lisa:intake-explain$lisa-intake-explain or a plain-English request that matches this skill.<item-ref>Use the /lisa:intake-explain skill to inspect a single repo-scoped PRD or build item, explain its current lifecycle role, and report whether Lisa would intake it, repair it, hold it, skip it, or leave it product-owned. Use the user's surrounding request as this command's arguments.
Common operator usage:
/lisa:intake-explain https://github.com/acme/repo/issues/123/lisa:intake-explain PRD-456/lisa:intake-explain https://linear.app/acme/issue/ENG-123/exampleThe diagnosis uses stable verdicts:
ELIGIBLE_FOR_INTAKE: run /lisa:intake <queue> when normal pickup is the next move.ELIGIBLE_FOR_REPAIR: run /lisa:repair-intake <queue> when Lisa-owned stuck work is actionable.WAITING_ON_STALENESS: wait and re-check after the configured freshness window.HELD_BY_BLOCKERS: clear the listed dependency or blocker before rerunning intake.NON_LEAF_CONTAINER: decompose the item or move build-ready status to leaf work.PRODUCT_OWNED_STATE: finish product clarification, promotion, or verification first.MISCONFIGURED: fix lifecycle labels, repo scope, or queue configuration before relying on automation.Use it for these operator workflows:
/lisa:intake right now./lisa:repair-intake.This surface is read-only in v1. It never claims, relabels, comments on, repairs, or decomposes the item; it only reports the item facts, verdict, decisive gate, and smallest useful next action before an operator chooses /lisa:intake, /lisa:repair-intake, /lisa:queue-status, or a tracker-native fix.