From logvalet
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.
npx claudepluginhub youyo/claude-plugins --plugin logvaletThis skill uses the workspace's default tool permissions.
`lv issue timeline` を材料に、LLM がコメント・更新履歴から意思決定を抽出・要約する。
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).
Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.
lv issue timeline を材料に、LLM がコメント・更新履歴から意思決定を抽出・要約する。
For full logvalet CLI documentation, see the
logvaletskill.
Use logvalet-decisions when you need to:
If the user provides a Backlog issue key (e.g., PROJ-123) or project key, extract and use it directly.
If no key is provided, ask for it.
For a single issue:
lv issue timeline ISSUE_KEY -f json
For a richer view, optionally include more activity:
lv issue timeline ISSUE_KEY --max-comments 0 --max-activity-pages 10 -f json
To narrow to a specific period:
lv issue timeline ISSUE_KEY --since YYYY-MM-DD --until YYYY-MM-DD -f json
The timeline returns a chronological sequence of:
Scan the timeline for content that indicates decisions were made:
Comment-based signals:
Update-based signals:
For each identified decision, extract:
Present the decision log in chronological order:
## 意思決定ログ — ISSUE_KEY
> タイムライン期間: FROM〜TO / 意思決定数: N件
---
### 1. [YYYY-MM-DD] <決定内容の1行サマリー>
- **判断者:** UserName
- **決定:** <具体的な決定内容>
- **理由:** <根拠・背景(記載がある場合)>
- **証拠:** <元のコメント or 更新イベント(要約)>
---
### 2. [YYYY-MM-DD] <決定内容の1行サマリー>
...
---
**サマリー:**
- 主要な意思決定: N件
- 主な判断者: UserA, UserB
- 重要な転換点: <あれば記載>
issue timeline が材料の唯一の権威ソース — 追加の issue get / comment list 呼び出しは不要--since で期間を絞ることを検討する--no-include-updates フラグでコメントのみに絞ることもできる