Loading...
Loading...
Found 9 Skills
Apply Socratic questioning — systematic inquiry via clarification, assumption-probing, evidence-testing, perspective-shifting, implication-tracing, and meta-questions — to coach learning or surface hidden assumptions in a person's reasoning. Use this skill when the user is explicitly facilitating learning, coaching a person through their own thinking, or needs a structured questioning sequence to probe a held belief, even if they say 'play devil's advocate on this claim' or 'how should I coach my team through this problem via questions'. Do NOT use for open-ended brainstorming, information gathering, or requirements-discovery question lists where no belief is being probed.
Brainstorm - Requirements Discovery (AI Coding Enhanced)
Product manager for PRD creation and requirements discovery. Use when the user asks to talk to John or requests the product manager.
Interactive discovery + implementation workflow that gathers requirements through picker-based questions (intent, scope, constraints, preferences), scans the codebase for what it can already infer, then writes an AWS architectural scaffold and implementation directly into the project. Use when the user wants to build a new app, scaffold a project, or expand/refactor an existing one on AWS — anything that calls for a structured discovery flow followed by code changes, not a one-off lookup. Do not use for: factual lookups about AWS Activate / programs / credits, requests for a single copy-paste prompt, non-AWS architectural work, or architecture advice/recommendations without code changes (see architect-for-startups).
Activate brainstorming mode for collaborative discovery and creative problem-solving. Use when users have vague requests, want to explore ideas, or need requirements discovery.
Requirements Discovery Specification, applicable to exploratory scenarios, helps users identify high-ROI functional directions when they are confused through role-playing. Automatically triggered, purely conversational inspiration.
The domain expert's product manager in a project repository run by the Boring Factory. Use when the expert brings a need or an idea, wants to clarify, change or resume a feature ("reprends la fiche"), asks what is happening with a feature, has a builder's question to answer, or has a preview to try and accept. Interviews one question at a time, writes the contract and mockups on the contract pull request, and submits the expert's approval only after the expert confirms. Never writes code.
Plant mit einer Person ohne Vorwissen ihre Webseite, bevor gebaut wird: für wen, was Besucher tun sollen, welche Seiten es braucht, welche Inhalte schon da sind, welche Vorbilder gefallen. Ergebnis ist ein Grundriss in docs/plan.md. Nutze den Skill bei «ich will eine Webseite», «Webseite planen», «was brauche ich für eine Webseite», «welche Seiten», «Sitemap», «wo fange ich an», und immer bevor auf dem Weg Webseite die erste Seite gebaut wird.
Interrogate the brief before a line is built — ask only the questions whose answers change the work, and put every unasked decision on the record as a stated assumption.