90 skills · sorted by relevance
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.
Structured clarification workflow for underspecified requirements. Use before planning to resolve ambiguities through coverage-based questioning. Records answers in spec clarifications section.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
Clarify vague requirements through exploratory questioning and option generation before committing to research or implementation.
The English summary is being prepared. Showing the original description.
Interactive PM interview with expertise-adaptive questioning for requirements elicitation
The English summary is being prepared. Showing the original description.
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
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Design a checking-for-understanding protocol with specific techniques for each lesson stage. Use when planning systematic comprehension checks during explicit or direct instruction.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Mom Test questioning toolkit, JTBD analysis, interview conduct, assumption testing framework, and hypothesis design
The English summary is being prepared. Showing the original description.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto…
The English summary is being prepared. Showing the original description.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
The English summary is being prepared. Showing the original description.
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.
The English summary is being prepared. Showing the original description.