unknown
Unknown: Strategy Blind Spot Analysis
Surface hidden assumptions and strategic blind spots using the Known/Unknown 4-quadrant lens.
When to Use
- Strategy documents that look coherent but are hard to execute
- Plans with unclear risk boundaries
- Decision discussions where the team asks: "What are we missing?"
For requirement clarification, use vague. For content/form leverage decisions, use metamedium.
Core Lens
Classify insights into four quadrants:
More from october-academy/agent-plugins
sync
Quick remote sync shortcut. Use when user says "/sync", "동기화", "pull", "git pull", or wants to pull latest changes from remote. Defaults to pulling from origin main.
1.2Kinterview-spec
Start iterative requirement clarification loop. Use this skill when the user has a vague requirement and wants to clarify it through structured questioning. Transforms unclear requirements into precise, actionable specifications.
18ship
Team-orchestrated implement → verify → fix → archive cycle
16frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
16wrap
Session wrap-up workflow. Use when user asks to "wrap up session", "end session", "/wrap", or wants to analyze completed work before ending.
15perf
Quick performance measurement using Lighthouse and Core Web Vitals. Use when user says "/perf", "성능 측정", "performance", "lighthouse", or wants to audit page performance. Supports single page or batch measurement.
14