with one click
workshop-upstage
workshop-upstage contains 5 collected skills from team-attention, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
๊ธธ๋ ์ด์ ์ธ์ฌ์ดํธ๋ฅผ ๊ตฌ์กฐํ๋ ๋ฌธ์๋ก ์ถ์ ํ์ฌ ์กฐ์ง ์ง์์ ๋ณต๋ฆฌ๋ก ์ฑ์ฅ์ํจ๋ค
This skill should be used when the user is building, planning, or strategizing and the key question is whether to optimize content (what) or change form (how/medium). Trigger on "๋ด์ฉ vs ํ์", "content vs form", "metamedium", "ํ์์ ๋ฐ๊ฟ๋ณผ๊น", "์๋ก์ด ํฌ๋งท", "๊ด์ ์ ํ", "perspective shift", "๋ค๋ฅธ ๋ฐฉ๋ฒ ์์๊น", "๊ฐ์ ๋ฐฉ์์ด ์ ๋จนํ", "diminishing returns". Applies Alan Kay's metamedium concept to surface form-level alternatives. For requirement clarification use vague; for strategy blind spots use unknown.
This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4๋ถ๋ฉด ๋ถ์", "blind spots", "๋ญ ๋์น๊ณ ์์ง", "๋ญ ๋ชจ๋ฅด๋์ง ๋ชจ๋ฅด๊ฒ ์ด", "์ ๋ต ์ ๊ฒ", "์ ๋ต ๋ถ์", "assumption check", "๊ฐ์ ์ ๊ฒ", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.
This skill should be used when the user's request or requirement is ambiguous and needs iterative questioning to become actionable. Trigger on "clarify requirements", "refine requirements", "์๊ตฌ์ฌํญ ๋ช ํํ", "์๊ตฌ์ฌํญ ์ ๋ฆฌ", "๋ญ ์ํ๋ ๊ฑด์ง", "make this clearer", "spec this out", "scope this", "/clarify". Turns vague inputs into concrete specs. For strategy blind spots use unknown; for content-vs-form reframing use metamedium.
์์ ์ ๋ง๋ฌด๋ฆฌํ๋ ์คํฌ. ํ ์คํธ ํ์ธ, ์ปค๋ฐ/PR, worktree ์ ๋ฆฌ์ ํจ๊ป 5๊ฐ์ ์ ๋ฌธ ์์ด์ ํธ๋ก ์ธ์ ์ธ์ฌ์ดํธ๋ฅผ ์ถ์ถํฉ๋๋ค.