91건 · 관련도순
Turn support feedback or chat logs into a structured requirements document. Use numbered questions to clarify problems, goals, users, constraints, and open questions, then guide human review before handing approved requirements to development.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Examine product costs, technical plans, and industry assumptions through a framework drawn from Elon Musk’s public record. Compare prices with material costs, question unnecessary requirements, and explore whether to build components internally or outsource them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Examine plans, proposals, and decisions by questioning assumptions, building opposing arguments, anticipating failures, or checking evidence. Presents three to five concrete challenges, then uses your responses to develop a stronger position and practical next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify implementation choices before planning a development phase. The skill reviews existing project context and code, asks about unresolved decisions, and records the answers in a context file for research and planning agents.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Explore research ideas through conversation, question assumptions, and connect approaches from different fields. Develop a broad set of possibilities, then assess promising directions and outline next steps such as pilot experiments or literature searches.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Clarify an existing feature specification before implementation planning. The skill prioritizes consequential gaps, asks focused questions one at a time, updates the specification with accepted answers, and summarizes unresolved decisions and recommended next steps.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Gather phase context through adaptive questioning before planning. Use --all to skip area selection and discuss all gray areas interactively. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals. Not for applying optimization patterns once profiling has identified a bottleneck (→ See `samber/cc-skills-golang@golang-performance` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Clarify vague requirements through exploratory questioning and option generation before committing to research or implementation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Interactive PM interview with expertise-adaptive questioning for requirements elicitation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Break large features into independently verifiable, human-reviewable slices under a feature directory in specs/. Use for risky or multi-step feature work that needs upfront questioning, API seams, browser-playable checkpoints, HTML visualizations, screenshot gates, staged implementation plans, recursive fog-of-war reslicing, or proactive research into reference implementations/best practices before slicing. Pairs with your project's verification harness and screenshot gates (the browser checkpoints), [refactor-clean](../refactor-clean/SKILL.md) (review the materialized spec so the plan describes one-owner architecture, not the feature bolted on), [screenshot-critique](../../visual/screenshot-critique/SKILL.md) and [compare-screenshots](../../visual/compare-screenshots/SKILL.md) (the visual gates), and a code-review pass (audit each slice before it lands).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deep business diagnosis for when things aren't working. Uses Socratic questioning, first-principles reasoning, and constraint analysis to find WHY a business is stuck — not just prescribe solutions. Use when the user says 'my business isn't working', 'I'm stuck', 'what's wrong', 'diagnose my business', 'why am I not growing', 'help me figure out the problem', or describes a specific business challenge.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Check an educational practice or task for cultural bias, WEIRD assumptions, and cross-cultural validity. Use when adapting resources for diverse contexts or questioning universal claims.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate elaborative interrogation prompts that deepen encoding through targeted why and how questions. Use when students memorise without understanding or need deeper processing of content.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design a checking-for-understanding protocol with specific techniques for each lesson stage. Use when planning systematic comprehension checks during explicit or direct instruction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a phase has unresolved decisions before planning and no CONTEXT.md exists. Asks adaptive questions on the phase's gray areas and writes {phase_num}-CONTEXT.md with locked decisions; --auto, --chain, --power change the questioning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the current milestone has shipped and it is time to scope the next one, or when the user asks to start a new milestone. Updates PROJECT.md, then runs questioning, research, requirements, and roadmap.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when starting GSD in a repo that has no .planning/ yet, or the user wants a new project set up. Questioning, optional research, requirements, and roadmap produce .planning/PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto…
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when drafting GitHub issues for the Positron repository. It provides workflows for searching duplicates, selecting appropriate labels, gathering complete context through questioning, and writing terse, fluff-free issues that precisely describe what is needed or wrong. The skill prepares issues for manual submission by the user. Use this skill when the user asks to draft or prepare an issue for Positron.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.