808 skills · sorted by relevance
Adjust an existing commercial contracts profile through a guided conversation. Update risk preferences, approvers, contract positions, or review formats one change at a time, with an explanation of how each update affects later work.
Update an existing employment-law practice profile through guided questions. Adjust employee locations, risk preferences, contacts, hiring or termination review rules, and other settings while reviewing downstream effects, without repeating setup or editing configuration files by hand.
Adjust an existing corporate legal practice profile through guided questions. Change risk preferences, contacts, review thresholds, active modules, or workspace paths, with an explanation of how each change affects related workflows.
Set up an employment legal practice profile through an interview and supplied documents. Record employee locations, hiring and termination review triggers, severance practices, and escalation contacts, then build a jurisdiction-specific table for routing issues to the appropriate reviewer.
Update an existing AI governance profile through guided changes. Adjust risk posture, escalation contacts, registered use cases, vendor positions, or assessment formats, while checking downstream effects and inconsistencies before saving each change.
Prioritize feature requests, analyze customer interviews, and draft product requirements documents. Use RICE scoring—a method weighing reach, impact, confidence, and effort—alongside templates and team capacity planning to turn findings into a quarterly roadmap.
Explore an early software idea through an interview, clarify the problem, and decide whether to proceed. Produce a design document covering decisions, flows, data structures, and interface agreements so others can plan the work.
Learn Ouroboros through a short, hands-on interview about your own project idea. Turn your answers into a sample specification with goals, constraints, and checkable outcomes, then learn the commands for execution, evaluation, and next steps.
Execute an existing Ouroboros Seed, a specification containing a goal and acceptance criteria, as a background job. The workflow checks each criterion, normally queues formal evaluation, and follows a bounded improvement loop if evaluation rejects the result.
Set up Ouroboros inside Claude Code with a guided wizard. Check runtime requirements, configure the Claude runtime, optionally add project instructions to CLAUDE.md, and register existing repositories as context for future interviews.
Bring external materials into a project’s Obsidian knowledge base as source notes organized by material type. Update the source registry, add important sources to the index, and record arrivals during active sessions in daily notes.
Refine a plan or design through an interview built around repeated follow-up questions. Use it to discuss an idea with an agent and work through further questions as you develop the proposal.
Refine a plan or design through an ongoing interview while creating documentation. The skill combines grilling and domain-modeling to produce architectural decision records, which capture design decisions, and a glossary of relevant terms.
Coordinate research from question development through literature searches, analysis, and publication with specialized agents. Supports quantitative, qualitative, and mixed methods studies, plus systematic reviews, with human approval at key decisions about research direction and methods.
Turn an initial research idea into a project specification through a structured interview. Develop testable questions, hypotheses, methods for identifying causal effects, and data requirements, then rank options by feasibility and contribution and save the plan.
Turn a broad coding request into a concrete work plan grounded in the codebase. After user approval, it documents affected files, decisions, dependencies, and verification steps so a separate worker can carry out the implementation.
Turn user data and interviews into research-backed personas, or representative user profiles. The toolkit also supports mapping user journeys, planning usability tests, and combining research findings to guide and validate design decisions.
Socratic deep interview with mathematical ambiguity gating before explicit execution approval
The English summary is being prepared. Showing the original description.
Turn one interview transcript into themes, supporting quotes, and action items. Use immediately after a session. For synthesising many sessions at once, use `affinity-diagram`.
The English summary is being prepared. Showing the original description.
Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint. For non-leading interview technique, see mom-test.
The English summary is being prepared. Showing the original description.
Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user-research questions, interpreting ambiguous feedback, or designing customer-discovery that avoids false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.
The English summary is being prepared. Showing the original description.
Plans, runs, and synthesizes customer research — interviews, surveys, win-loss analysis, and message testing — into findings that change decisions. Use this when the customer is being guessed at, before positioning or a major launch, when churn or conversion has an unexplained cause, or when a team is arguing from anecdotes. Also use to turn raw interview notes into usable findings.
The English summary is being prepared. Showing the original description.
Simulate realistic coding interview experience
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.