logvalet

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.

Create a Backlog issue interactively: gather project, type, summary, description, priority, assignee, and other fields via questions, preview with dry-run, then submit. Use this skill whenever the user wants to create, register, file, or add a new Backlog issue, ticket, task, or bug report. TRIGGER when: user says "課題作成", "issue作成", "チケット作成", "タスク登録", "backlogに課題を作って", "バックログに登録", "新しいissue", "create issue", "file a ticket", "make a task", "backlog.com に課題追加", "課題を作りたい", "issueを立てたい", "チケットを切って", "タスクを作って", "バグ報告を登録", "新規課題", "register an issue", "open a ticket", "add a task to backlog", "課題追加", "バックログに追加". DO NOT TRIGGER when: user wants to update an existing issue (use logvalet CLI directly) or wants to bulk-create issues from a spec (use spec-to-issues).

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.

Show near-term Backlog issues assigned to me AND issues I'm watching: next few business days across all projects, including overdue items — helps answer "what should I work on next?" and "what should I keep an eye on?" Watched issues are included because they represent work you care about even without being the assignee — blocked dependencies, pending reviews, cross-team items. TRIGGER when: user says "直近のタスク", "upcoming tasks", "次にやること", "次やること", "明日以降のタスク", "backlogの直近", "coming up", "what's next", "明日何やる", "次の予定", "今日と明日のタスク", "直近の課題", "next tasks", "upcoming issues", "what should I do next", "明日の予定", "次のアクション", "今日やること", "today's tasks", "直近やるべきこと", "tomorrow's tasks", "近日中のタスク", "ウォッチしてるやつどうなった", "watched issues status". DO NOT TRIGGER when: user wants a full week overview (use my-week) or wants a project-wide task list (use logvalet CLI directly).

Show this week's Backlog issues assigned to me AND issues I'm watching across all projects, including overdue items from previous weeks — the weekly planning view. Watched issues matter because they affect your work even when you're not the assignee: dependency blockers, reviews you're waiting on, cross-team items you need to track. TRIGGER when: user says "今週のタスク", "my week", "今週やること", "今週の予定", "backlogの今週分", "weekly tasks", "this week's issues", "今週やるべきこと", "今週何やる", "今週の課題", "今週のバックログ", "weekly plan", "week overview", "今週の計画", "月曜から金曜のタスク", "今週のスケジュール", "weekly planning", "what's on my plate this week", "今週の見通し", "ウォッチしてる課題", "watching issues", "気にしてる課題", "注視してる課題", "watched tasks this week". DO NOT TRIGGER when: user wants only the next 1-2 days (use my-next) or wants team-wide workload (use health).

Generate a Backlog activity report for specified users, teams, or projects over a time period: monthly report, weekly report, team activity summary, KPT retrospective material, and more. Use this skill whenever someone needs a shareable report or summary of Backlog activity. TRIGGER when: user says "レポート作成", "月次レポート", "活動レポート", "チームレポート", "backlogレポート", "activity report", "monthly report", "team report", "先月のレポート", "今月のレポート", "メンバーの活動", "チームの活動まとめ", "KPTレポート", "ふりかえりレポート", "活動報告", "月報", "週報", "進捗報告", "稼働報告", "generate a report", "activity summary", "team performance report", "期間レポート", "backlog 月報", "チームの成果", "実績報告". DO NOT TRIGGER when: user wants a quick daily/weekly digest without user breakdown (use digest-periodic) or wants project health metrics (use health).

Generate an integrated risk assessment for a Backlog project: combining project health, blockers, stale issues, and workload data — the LLM produces risk ratings, root cause analysis, and prioritized recommended actions. TRIGGER when: user says "リスク評価", "risk summary", "プロジェクトリスク", "リスク分析", "リスクは何", "対策は", "risk assessment", "リスクを洗い出して", "プロジェクトの懸念事項", "危険な兆候", "リスクマネジメント", "what are the risks", "risk analysis", "プロジェクトの課題を特定", "改善すべき点", "問題点の洗い出し", "risk mitigation", "推奨アクション", "次にやるべき対策", "プロジェクトの危機管理". DO NOT TRIGGER when: user wants a quick health score only (use health) or wants activity pattern analysis without risk interpretation (use intelligence). Workflow: Automatically gathers health + blockers + stale data before analysis.

Decompose a specification document into Backlog issues: the LLM analyzes a spec/requirements file, breaks it into appropriately-scoped tasks, and creates them in Backlog one by one with dry-run preview before each submission. TRIGGER when: user says "specから課題作成", "仕様から課題を作って", "spec to issues", "仕様書を課題に分解", "要件を課題にして", "spec 分解", "仕様分解", "仕様書からチケットを切って", "spec からタスクを作成", "要件定義を課題に", "仕様をバックログに登録", "spec を issue に変換", "設計書から課題を起こして", "PRD から課題を作成", "タスク分解", "break down spec into issues", "create issues from requirements", "一括課題作成", "bulk issue creation from spec". DO NOT TRIGGER when: user wants to create a single issue manually (use issue-create) or wants to write a spec first (use an external spec tool).

Triage a Backlog issue: the LLM analyzes triage materials (issue attributes, history, project statistics, similar issues) and suggests priority, assignee, and category assignments. Use this skill whenever someone needs help deciding how to prioritize or assign an issue. TRIGGER when: user says "トリアージ", "triage", "優先度を決めて", "アサイン提案", "課題を振り分けて", "誰に担当させる", "priority 提案", "担当者を決めて", "課題のカテゴリ分類", "issue triage", "優先度の見直し", "アサインの提案", "この課題の優先度は", "誰にアサインすべき", "振り分けて", "prioritize this issue", "who should handle this", "assign this task", "課題の優先順位", "タスクの振り分け", "課題を整理して". DO NOT TRIGGER when: user wants full issue context without recommendations (use context) or wants to create a new issue (use issue-create). Workflow: Automatically fetches triage-materials before analysis.