メニュー
Use when user asks to list, show, or enumerate Jira issues (e.g. "what jira tickets are open", "list HIMMEL stories", "show me in-progress jira"). MUST mention "jira" or a project key (HIMMEL, LUNA, etc.) or an explicit ticket pattern. Do NOT trigger on "list PRs", "show issues" without context, or GitHub references.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Panel-only CR gate for Codex — runs the shell critic panel and CodeRabbit CLI pass over the branch diff, records ledger evidence, and clears the CR marker through the sanctioned chokepoint only when both the panel and CodeRabbit findings are clean (no Critical/Important blockers). Use when the user asks to run /pr-check or clear the CR gate under Codex.
Use when the user says "new epic", "new task", "new standalone", "end session", "update status", "handover", "handover-resume
Arm the OS scheduler to relaunch claude at a given time with a given handover. Dedup-guarded. Use when the user asks to arm a resume / schedule a relaunch or run /handover-arm-resume.
Arm/inspect/remove the recurring luna clip-pipeline cadence (daily harvest+triage, daily synthesize+archive, daily health) via schtasks/cron, each leg pinned to a cheap --model. Dedup-guarded. Use when the user asks to arm/check/disarm the clip-pipeline cadence or runs /pipeline-cadence.
Use when the per-project auto-memory store (`~/.claude/projects/<project-slug>/memory/`: the always-loaded `MEMORY.md` index + one topic file per fact) is approaching or over its load budget (~24.4KB) — the harness emits a size-limit warning at session load when over budget (e.g. "MEMORY.md is NN KB (limit 24.4KB)"), content past the limit is silently dropped = partial recall. Losslessly compounds the DURABLE gotchas out of the auto-memory into qmd-searchable luna / himmel reference notes (read-many → propagation review → write-once → qmd gate → slim index → delete sources), so the always-loaded index stays lean and adopter-generic learnings land in himmel docs (memory + vault never propagate to other users). Lean-invoke, operator-run on demand — NOT an always-on hook (HIMMEL-569).
Use when turning an idea into an implementation plan — runs brainstorm → spec → plan as ONE pipeline with an ADVERSARIAL CRITIC LOOP between each stage. Trigger on "build/implement/design X", "/minerva", or any feature/capability work that should pass through a spec + plan before code. Composes superpowers brainstorming + writing-plans (no fork); adds a spec-critic and a plan-critic.
| name | jira-list |
| description | Use when user asks to list, show, or enumerate Jira issues (e.g. "what jira tickets are open", "list HIMMEL stories", "show me in-progress jira"). MUST mention "jira" or a project key (HIMMEL, LUNA, etc.) or an explicit ticket pattern. Do NOT trigger on "list PRs", "show issues" without context, or GitHub references. |
Run /jira-list [project] [status] with the project and (optional) status the user mentioned. When no project is given, the CLI falls back to JIRA_PROJECT_KEY.
