From insight-blueprint
Guides structured reflection on an analysis design using its Insight Journal. Helps draw conclusions, identify gaps, and decide whether to conclude, refine, or branch. Triggers: "振り返り", "reflection", "まとめ", "結論を出す", "分析を振り返る", "この仮説どうなった", "wrap up analysis".
npx claudepluginhub etoyama/insight-blueprint --plugin insight-blueprintThis skill uses the workspace's default tool permissions.
Guides the user through a structured reflection on their analysis,
Generates design tokens/docs from CSS/Tailwind/styled-components codebases, audits visual consistency across 10 dimensions, detects AI slop in UI.
Records polished WebM UI demo videos of web apps using Playwright with cursor overlay, natural pacing, and three-phase scripting. Activates for demo, walkthrough, screen recording, or tutorial requests.
Delivers idiomatic Kotlin patterns for null safety, immutability, sealed classes, coroutines, Flows, extensions, DSL builders, and Gradle DSL. Use when writing, reviewing, refactoring, or designing Kotlin code.
Guides the user through a structured reflection on their analysis, using the Insight Journal as source material. Helps reach a conclusion, identify remaining gaps, or decide to branch.
get_analysis_design(design_id) — load design.insight/designs/{design_id}_journal.yaml using Read tool — load journalShow structured overview:
── Reflection: {design_id} ──
Title: {title}
Hypothesis: {hypothesis_statement}
Intent: {analysis_intent}
Status: {status}
── Journal Overview ──
Total events: {count}
Phase: {inferred_phase} (see /analysis-journal Phase Inference rules)
Timeline: {first_event.created_at} → {last_event.created_at}
── Evidence ──
Supporting: {count} items
- {content} ({created_at})
Contradicting: {count} items
- {content} ({created_at})
── Decisions Made ──
- {method} ({package}) — {reason}
── Open Questions ──
- {question_content} ({event_id})
── Branches ──
- {child_design_id}: {child_title} ({child_status})
To find branches, use:
children = [d for d in list_analysis_designs(theme_id=design.theme_id) if d.parent_id == design_id]
Ask in sequence. Record each answer as a reflect event in the journal.
Q1: Evidence Assessment "証拠を総合すると、仮説「{hypothesis_statement}」についてどう言える？"
Q2: Open Questions Check If open questions exist: "未解決の問い ({count}件) がある。これらは結論に影響する？"
Q3: Conclusion or Next Step "どう進める？"
If user chooses to conclude:
Record conclude event in journal:
- id: "{design_id}-E{nn}"
type: conclude
content: "{user's conclusion statement}"
metadata:
resolves: ["{question_event_ids that are now resolved}"]
created_at: "{now}"
Suggest status transition: "結論が出た。ステータスを変更する？"
transition_design_status(design_id, "analyzing", "supported")transition_design_status(design_id, "analyzing", "rejected")transition_design_status(design_id, "analyzing", "inconclusive")Note: Current status must be "analyzing" for terminal transition. If status is "in_review", suggest going through the review process first.
Show final summary and suggest:
If user chooses to refine:
hypothesize event with the refined hypothesis in journalupdate_analysis_design(design_id, hypothesis_statement=refined)| Tool | Used for |
|---|---|
get_analysis_design(design_id) | Load design details |
transition_design_status(design_id, current, new) | Terminal status transition |
update_analysis_design(design_id, ...) | Hypothesis refinement |
list_analysis_designs(theme_id?) | Find child/sibling designs |
| From | To | When |
|---|---|---|
| /analysis-journal | → /analysis-reflection | Evidence gathered |
| /analysis-reflection | → /analysis-journal | Need more evidence or branching |
| /analysis-reflection | → /catalog-register | Conclusion worth registering as knowledge |
| /analysis-reflection | → /analysis-framing | New hypothesis needed, explore data/direction first: "新しい角度を探すなら /analysis-framing" |
| /analysis-reflection | → /analysis-design | Derived hypothesis already clear: "派生仮説を作るなら /analysis-design" |