비즈니스 스킬

Analyze individual stocks using current quotes and historical price data. Calculate trend and momentum measures, identify price gaps and potential support or resistance levels, and produce a three-day outlook with trading scenarios and risk notes.

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

• Reviewing an individual stock's price trend
• Checking support and resistance around price gaps
• Comparing three-day price scenarios

Create a resume tailored to a specific job posting by matching requirements with relevant experience and achievements. Adjust keywords for applicant tracking systems, software used to manage applications, and identify strengths and qualification gaps.

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

• Tailor an existing resume to a job posting
• Highlight transferable experience for a career change
• Adjust resume keywords for applicant tracking systems

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.

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

• Rank feature requests using RICE scores
• Extract customer problems and themes from interviews
• Draft a product requirements document from a template

Connect product research, 1688 data collection, listing templates, advertising copy, and promotional video creation for cross-border ecommerce. It also supports finding secondhand deals on 闲鱼 and monitoring prices against selected requirements.

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

• Research trending products for cross-border ecommerce
• Prepare listing templates from 1688 product data
• Create advertising copy and vertical product videos

Review Word contracts for textual inconsistencies, business terms, and legal clauses while preserving the original wording and formatting. Produce clause-specific comments, an objective contract summary, consolidated review opinions, and a business flowchart based on the contract.

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

• Checking amounts, dates, and clause references
• Reviewing payment and acceptance terms
• Organizing risks in liability and termination clauses

Simulate a decision meeting with three to five AI roles with different expertise and personalities. Follow their debate and receive a meeting record covering conclusions, supporting arguments, risks, and suggested next actions.

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

• Compare technical architecture options
• Discuss pricing strategies for a new product
• Identify project risks and possible responses

Turn site requirements or existing content into a SITE.md project guide for the Stitch Build Loop. It records the site's purpose, visual direction, navigation, file structure, and prioritized tasks to guide successive development rounds.

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

• Organize a site brief before development
• Record site purpose and visual direction
• List completed and planned pages

Manage Workspace users, groups, and organizational units through gog. The skill guides account selection and command checking, with confirmation of the target and intended change before writes or deletions, plus preview checks for supported writes.

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

• Managing Workspace users
• Managing Workspace groups
• Managing Workspace organizational units

Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.

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

• Define feature requirements and scope in a PRD
• Split development plans into tasks and sync them to GitHub
• Coordinate parallel agents working on issues

Turn a development-ready feature's specifications, customer context, demand evidence, and mockups into a concise executive summary. Give sales, leadership, and engineering one shared document covering the problem, solution, key decisions, scope, dependencies, metrics, and audience-specific questions.

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

• Create a shared feature briefing for sales, leadership, and engineering
• Summarize customer needs and reasons to prioritize a feature
• Clarify key decisions, exclusions, and dependencies

Collects and summarizes background research for a product feature, including customer needs, competitors, regulations, and internal decisions. Produces a source-linked background.md and updates shared context documents when findings are useful across features.

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

• Gathering background research for a new feature
• Organizing customer requests and pain points
• Reviewing competitor approaches and relevant regulations

Review feature plans before development from business strategy, user experience, and engineering perspectives. Receive scored assessments, specific gaps tied to requirements, and prioritized actions that clarify what must change before the team starts building.

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

• Checking a feature specification before development
• Reviewing screen states and accessibility requirements
• Assessing scope against business priorities

Turn rough meeting notes, customer requests, and product ideas into structured backlog entries, a list of possible improvements. Capture who needs each idea and why, categorize it, and update matching entries with new evidence.

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

• Capturing feature ideas after a meeting
• Recording requests from customers or sales
• Logging product gaps found in competitor research

Evaluate a feature idea before turning it into requirements using six sequential questions. Examine customer demand, current workarounds, a specific user's pain, and the smallest useful solution, then save an evidence-based assessment with a verdict and next steps.

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

• Validating customer demand before writing requirements
• Narrowing a feature to its smallest useful version
• Separating customer evidence from assumptions

Turn rough feature ideas into a clear SPEC.md through focused questions. Define target users, business rules, current scope, and acceptance criteria based on observable results, giving developers or AI agents concrete requirements to implement.

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

• Turning rough feature ideas into requirements
• Defining observable acceptance criteria
• Clarifying current scope and exclusions

Interpret Culture Index behavioral profiles to understand individual traits, team balance, and possible strain from workplace adaptation. Use PDF or JSON data to inform hiring discussions, management approaches, onboarding plans, and conflict mediation.

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

• Understanding an individual’s behavioral profile
• Assessing team balance and missing roles
• Exploring strain from Survey and Job differences

Plan how to approach a key stakeholder by examining their role, authority, concerns, and situation. Get tailored messaging, communication methods, frequency, mutual expectations, and a concrete next action with an owner and deadline.

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

• Preparing executive alignment before a roadmap review
• Planning a conversation with a resistant stakeholder
• Including frontline users in decisions that affect them

Draft an Amazon-style press release before development to clarify a product's customer value. Using Working Backwards, a method that starts with the intended customer outcome, organize the problem, benefits, and launch promise so stakeholders can assess the idea.

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

• Clarifying customer value before product development
• Aligning stakeholders on a launch promise
• Testing whether a product idea has a convincing story

Evaluate SaaS customer economics and cash efficiency using acquisition costs, customer lifetime value, margins, and payback periods. Compare segments and channels, estimate how long cash will last, and assess whether to expand spending or improve efficiency.

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

• Reviewing customer economics before increasing paid acquisition
• Comparing acquisition costs and payback across channels
• Estimating cash runway and funding needs

Assess whether a product is mature or declining, then compare extending it, replacing it, or retiring it. Use diagnostic questions, a product portfolio worksheet, and a replacement risk register with backup plans to document the next move.

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

• Choosing between a product refresh, replacement, or retirement
• Checking whether a mature product is entering decline
• Setting consistent plans across an aging product line

Turn business goals and customer problems into a product roadmap. Define initiatives, rank priorities, check dependencies and team capacity, and organize releases with clear reasons stakeholders can review and discuss.

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

• Planning a quarterly or six-month product roadmap
• Prioritizing competing initiatives across teams
• Explaining roadmap choices to executives

Turn user research and complaints into a clear problem statement. Identify who is struggling, their desired outcome, barriers, root causes, constraints, and emotional impact, then summarize the problem in one sentence for team discussions or product planning.

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

• Agreeing on the user problem before proposing solutions
• Writing a concise problem statement for a PRD
• Finding the underlying problem behind feature requests

Choose a prioritization method that fits your product stage, team, stakeholder needs, and available data. Get a recommended framework, practical setup steps, a scoring example, and an alternative approach with its tradeoffs.

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

• Choosing a method for recurring roadmap prioritization
• Selecting a lightweight approach when data is scarce
• Agreeing on prioritization rules with stakeholders

Split large feature requests or user stories, descriptions of what users need, into smaller deliverable pieces. Eight patterns guide the breakdown, with acceptance criteria and checks that each piece provides value and can be developed and tested independently.

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

• Breaking down work that will not fit in one sprint
• Clarifying backlog items that are too large to estimate
• Separating stories with multiple acceptance scenarios