Search Backlog documents by keyword within a space: runs lv document search and presents results as a snippet-based digest — title, project, and a relevant excerpt from each document. TRIGGER when: user says "ドキュメント検索", "document search", "資料を探して", "ドキュメントを探して", "Backlog ドキュメント検索", "wiki 検索", "ドキュメントを検索", "document を検索", "search documents", "find documents", "資料検索", "ドキュメントから探して", "document を探したい", "ドキュメントで調べて", "search backlog docs", "find in documents", "ドキュメント一覧から探す", "キーワードでドキュメントを検索", "keyword document search", "ドキュメントの中を検索", "資料を見つけて". DO NOT TRIGGER when: user wants to get a specific document by ID (use lv document get), wants to list all documents in a project (use lv document list), or wants to search issues/wiki (use the respective commands).
Backlog 向け LLM-first CLI「logvalet」の PM メタモデル。 全スキルの使い方・組み合わせ・ワークフローを案内するハブスキル。 TRIGGER when: user asks "logvaletって何", "どのスキルを使えばいい", "backlogの操作方法", "logvalet help", "スキル一覧", "ワークフロー", "logvaletの使い方", "Backlogで何ができる", "課題管理のやり方", "タスク管理の方法", "backlog.com の操作", "プロジェクト管理をやりたい", "PM ワークフロー", "logvalet commands", "available skills", "what can logvalet do". DO NOT TRIGGER when: user has a specific task (issue creation, triage, report, etc.) — use the specialized skill instead.
Fetch full context for a Backlog issue in one shot: issue details, comments, status signals, overdue/stale detection, and LLM hints — everything needed to understand and act on an issue. TRIGGER when: user provides a Backlog issue key (e.g. PROJ-123, ESU2_S2-32), a Backlog URL (*.backlog.com/view/*, *.backlog.com/alias/*), or says "課題の詳細", "この課題について", "issue context", "課題を理解したい", "issue を調べて", "この issue の状況", "課題の背景", "課題の情報をまとめて", "PROJ-123 について教えて", "バックログの課題の詳細", "issue summary", "課題コンテキスト", "backlog issue context", "チケットの状態", "このチケットについて", "課題の全体像", "what's the status of this issue". DO NOT TRIGGER when: user wants to create/update an issue (use issue-create), wants a triage recommendation (use triage), or wants a comment draft (use draft).
Extract and summarize decision logs from a Backlog issue's timeline: who decided what, when, and why — by analyzing comments and status change history. TRIGGER when: user says "意思決定", "decision log", "決定履歴", "なぜこうなったか", "経緯を教えて", "決定の背景", "decision history", "どうして変更された", "意思決定ログ", "何が決まった", "承認経緯", "設計の経緯", "why was this decided", "変更の理由", "この課題の歴史", "議論の経緯", "ステータス変更の理由", "誰が決めたか", "合意形成の過程", "過去の決定を振り返りたい", "この仕様になった理由". DO NOT TRIGGER when: user wants current issue status (use context) or wants to analyze project-wide activity patterns (use intelligence). Complements: Use after /logvalet:context to dive deeper into the decision history.
Generate a weekly or daily digest of Backlog project activity: completed issues, newly started work, blocked items, and active issue counts — deterministic, no LLM needed. TRIGGER when: user says "週次ダイジェスト", "日次ダイジェスト", "今週の進捗", "weekly digest", "daily digest", "今週のまとめ", "進捗まとめ", "先週の振り返り", "日報ネタ", "週報ネタ", "今日の進捗", "プロジェクトの今週の動き", "weekly summary", "daily summary", "weekly progress", "今週完了したもの", "今日のアクティビティ", "定期レポート", "periodic digest", "進捗サマリー". DO NOT TRIGGER when: user wants a full activity report with user/team breakdown (use report) or wants anomaly detection (use intelligence). Complements: Combine with /logvalet:report for a comprehensive periodic review.
Draft a context-aware Backlog issue comment: progress update, inquiry, resolution notice, or escalation — the LLM generates a draft based on the issue's full context and comment history. TRIGGER when: user says "コメント下書き", "draft comment", "コメントを書いて", "返信を作って", "コメントを作成", "comment draft", "コメント草稿", "コメントを下書きして", "issue comment を書いて", "バックログにコメント", "進捗報告コメント", "確認依頼コメント", "解決通知コメント", "コメントで報告したい", "返信案を作って", "エスカレーションコメント", "write a comment", "reply to this issue", "コメントの文面を考えて". DO NOT TRIGGER when: user wants to create a new issue (use issue-create) or wants to update issue fields like status/assignee (use logvalet CLI directly). Workflow: Automatically fetches context via /logvalet:context before drafting.
Check the health of a Backlog project: stale issues, blockers, user workload imbalance, and an overall health score (0-100) with level (healthy/warning/critical). Use this skill whenever someone asks about the state of a project, team performance, or whether a project is on track. TRIGGER when: user says "プロジェクトの状態", "project health", "プロジェクト健全性", "プロジェクト大丈夫", "このプロジェクトどう", "停滞してる課題ある？", "ブロッカーは？", "プロジェクトの健全性", "health check", "チームの負荷状況", "ワークロード", "workload", "プロジェクト診断", "project status", "is the project on track", "プロジェクトのスコア", "開発の進み具合", "課題の滞留状況", "プロジェクト概況". DO NOT TRIGGER when: user wants a detailed risk assessment with recommendations (use risk) or wants activity trend analysis (use intelligence). Complements: Follow up with /logvalet:risk for actionable recommendations.
Analyze Backlog activity patterns: detect anomalies, concentration bias, peak hours, and unusual trends — the LLM interprets activity statistics and project health data to surface risks that numbers alone don't reveal. TRIGGER when: user says "アクティビティ分析", "activity intelligence", "異常検知", "偏り", "アクティビティの傾向", "activity patterns", "最近の動きに異常は", "チームの活動パターン", "作業の偏り", "ピーク時間帯", "activity anomaly", "特定の人に集中してない？", "活動量の分析", "誰が何をしてるか", "concentration analysis", "activity trends", "稼働分析". DO NOT TRIGGER when: user wants a simple activity list (use logvalet CLI directly), wants a periodic digest (use digest-periodic), or wants risk recommendations (use risk). Workflow: Combines activity stats + project health for holistic analysis.