'product question' 검색 결과

Resolve a design question by building a temporary, runnable prototype. Explore logic through clickable scenarios or compare three structurally different interface variants, then record the user's decision while keeping the prototype separate from production code.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Comparing three different interface structures
• Exploring state transitions through clickable scenarios
• Resolving design discussions that need a visible example

Build AI applications with LangChain, including chatbots with conversation history and systems that search documents before answering. The skill provides examples for connecting models, calling tools, retrieving information, and tracing application runs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Building a chatbot that uses conversation history
• Creating a question-answering system for documents
• Developing an agent that calls external tools

Research customer questions using available internal documents, account history, support records, and public sources. Produce a brief with an answer, source references, confidence level, unresolved questions, and recommended next steps before drafting a customer response.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check product capabilities before answering a customer
• Find previous bug reports and known workarounds
• Review what a specific customer was told before

Find the right specialist skill for a marketing question, coordinate content, SEO, advertising, and analytics tasks, or review gaps across current activities. Get recommended next steps or a campaign plan with a sequence and timeline.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing a marketing skill for a specific question
• Coordinating a product launch campaign
• Reviewing gaps and priorities across marketing activities

Design or review SaaS pricing by choosing what customers pay for, defining plan features, and assessing price points. Create pricing page outlines, customer research questions, and price increase plans with communication templates and risk scenarios.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Designing pricing plans for a new SaaS product
• Reviewing existing prices and plan features
• Planning a price increase and customer notices

Review data strategy plans through six focused questions covering training data permissions, infrastructure choices, data asset value, and hiring. Produce a structured verdict with unresolved issues and three concrete next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review customer data permissions before AI training
• Compare data architecture options
• Assess data assets before productization or M&A

Review engineering delivery plans, hiring proposals, and team changes through six operational questions. Assess delivery metrics, recruitment stages, management structure, and production practices, then produce a verdict and three concrete actions to address the findings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing quarterly delivery commitments
• Checking an engineering hiring plan
• Assessing a proposed team reorganization

Review startup contracts and investment terms to identify risky clauses, prepare negotiation proposals, and organize questions for qualified attorneys. It also covers intellectual property ownership and regulatory exposure, helping founders prepare for legal review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking contract risks before signing
• Reviewing investment terms and founder dilution
• Auditing intellectual property ownership and open source licenses

Review contracts, investment terms, and employment arrangements through six legal lenses. Identify key risks, organize negotiation priorities, and prepare specific questions for outside counsel before making commitments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing investment terms before signing
• Identifying negotiation points in customer contracts
• Checking IP ownership for employees and contractors

Prepares medical device quality systems for ISO 13485 audits using six focused questions. Reviews design records, corrective actions, process validation, risk files, post-market monitoring, and management reviews, then summarizes readiness gaps and three priority actions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check readiness before an ISO 13485 internal audit
• Review design history files before a product launch
• Check evidence that corrective actions were effective

Create a concise sales reference comparing your product with a specific competitor. Organize product and pricing differences, strengths on both sides, responses to common objections, and win/loss patterns into a Markdown document for use during sales conversations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Preparing sales teams for competitive deals
• Answering questions about a cheaper competitor
• Creating a feature and pricing comparison

Develop a product or side-project idea through guided questions and premise checks. Startup discussions examine evidence of demand, while builder discussions explore possibilities and scope, producing a design document before implementation begins.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Examining demand for a startup idea
• Defining the smallest useful internal project
• Shaping a hackathon or side-project idea

Guides building chatbots and tool-using agents with LangChain. Covers conversation history, model provider integration, and RAG, which retrieves relevant documents to inform answers, plus tracing to inspect application behavior.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Build a chatbot that remembers conversation history
• Create document question answering with source references
• Build an agent that uses custom tools

Turn a feature idea or rough notes into a product requirements document, or PRD. It organizes the problem, users, scope, prioritized requirements, success measures, and unresolved questions so a team can agree on what to build.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Turn a feature idea into a product requirements document
• Agree on goals and boundaries before development
• Prioritize requirements and define success measures

Build a single-page landing page for a SaaS product, organizing supplied content into features, steps, pricing, and frequently asked questions. Include action buttons and a customer logo section, with a single-column layout on mobile.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating a landing page for a SaaS product
• Organizing features, usage steps, and pricing
• Designing a product page for desktop and mobile

Guide a workshop one question at a time with visible progress and clear answer options. The skill adapts to supplied context, handles interruptions and pauses, and closes with a summary of decisions and actionable choices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Guide a product team positioning workshop
• Structure the kickoff of a discovery sprint
• Facilitate a retrospective on a failed beta launch

Plan stakeholder conversations before retiring a product or feature. Get an ordered sequence of meetings, with questions, commitments, warning signs, and required outcomes, adjusted to the scale and complexity of the retirement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Planning conversations before a product retirement
• Checking promises made by Sales before announcing
• Coordinating a retirement involving resellers

Turn a competitive or market question into a focused research approach through three adaptive questions. Get recommendations for information sources, review frequency, and executing skills, with reasons tailored to the decision and available time.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing where to investigate a suspected competitor move
• Planning competitive research within limited time
• Setting a sustainable market monitoring schedule

Turn research notes and discussions into a PRD, a product requirements document for development teams. Connect customer problems, target users, proposed solutions, and success metrics, while documenting acceptance criteria, excluded work, dependencies, and unresolved questions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Writing requirements for a major new feature
• Turning discovery findings into an engineering handoff
• Aligning teams on scope and success metrics

Examines project code, development history, tests, and documentation, then asks three focused questions to recommend a combination of AI-assisted development methods, with practical starting steps tailored to the project.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choosing development methods for a solo prototype
• Reviewing workflows for an existing SaaS product
• Selecting evaluation methods for an AI product

Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy, clean-architecture, pragmatic-programmer, release-it, system-design, ddia-systems - asking the user questions at every decision point and recording results in the project docs/ folder (TESTING.md, TECH-DEBT.md, IMPROVE-CODE-QUALITY-PLAN.md) so the journey resumes across sessions. Use when the user wants to harden an AI-generated prototype, add tests before refactoring, make code safe to change, or says 'this works on my machine but I am scared to touch it'. For an aged codebase, remove-technical-debt; for greenfield structure, design-code-architecture; for a product and UX pass, improve-app; to optimize speed and structure, architecture-optimization. For one framework in isolation, invoke that skill directly.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build traceable internal-review proposal, RFI, RFP, tender, bid, and questionnaire responses from supplied questions and approved sources. Use to analyze questions, contribute business or product evidence, or draft qualified responses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review generated or changed WooCommerce code — extensions, payment and shipping integrations, checkout customizations, and order/product logic — before it ships. Best used reactively after an agent writes, edits, or reviews code touching WooCommerce APIs: wc_get_order, wc_get_orders, wc_get_product, WC() cart or session, woocommerce_* hooks, Store API endpoints, payment gateways, order or product meta, HPOS, subscriptions, or bookings. Use on 'review this Woo plugin', 'is this HPOS compatible', or after tasks like 'write a WooCommerce extension', 'add a checkout field', 'hook into the order flow', or 'update stock'. Enforces HPOS-safe order access, CRUD over direct meta, feature-compatibility declarations, server-side checkout validation, money-handling discipline, and hooks over template overrides. DO NOT USE for WordPress code without WooCommerce APIs (use wp-guard), generic code review (use clean-code-guard), test review (use test-guard), or store configuration and admin-screen questions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Guide ethical customer discovery and research synthesis, distinguishing direct observations from inferences, preventing leading interview questions, and tracking quote-to-insight provenance. (triggers: `product customer discovery`, `product research synthesis`)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.