비즈니스 스킬

Explore ideas for products, content, names, strategies, technical approaches, or decisions. It frames the goal and constraints, generates distinct options, challenges assumptions and tradeoffs, then narrows the result to three strong choices with reasons and a next step.

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

• Generating and comparing product or project ideas
• Exploring names, content angles, or campaign concepts
• Pressure-testing technical approaches or important decisions

Turns a raw project idea in an empty workspace into a reviewed `goal-and-requirements.md`. The workflow infers a suitable document shape, confirms key decisions with the user, records settled sections incrementally, and can optionally research alternatives before final review.

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

• Turning an initial idea into product requirements
• Creating a lightweight personal project brief
• Drafting a PRD for a product with named users

Capture durable business rules, metric definitions, aliases, and conventions in reusable wiki pages. The workflow checks related pages and semantic-layer sources first, adds accurate cross-references, and avoids saving temporary requests or values that can quickly become outdated.

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

• Record an agreed metric definition
• Save an organization-wide reporting rule
• Document a domain-specific alias or convention

Forecast existing Azure spending or estimate prices for planned resources and workloads. The skill clarifies region, operating system, currency, and usage assumptions, then uses public or contract prices to support planning and comparisons.

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

• Forecast next month's Azure spending
• Estimate costs for planned virtual machines
• Compare prices across storage tiers or regions

Investigate actual Azure spending, bill changes, and cost spikes. Break down historical charges, examine AKS and AI service costs, and distinguish measured spending from inferred causes while identifying gaps in the available data.

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

• Review historical Azure spending by category
• Investigate sudden increases in Azure bills
• Analyze AKS cluster and namespace costs

Calculate whole-share position size from a trade plan, budget, and configured limits for loss, position value, order size, and cash buffer. See which limit determines the size and get one proposed bracket order; the skill does not place it.

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

• Calculate how many shares fit a trade plan and budget
• See which account limit determines a position size
• Draft a bracket order with stop-loss and take-profit prices

Prepare and present broker order tickets, record the user’s explicit yes, and track order results and fills. The workflow uses paper trading by default and requires a separate permission approval before an order is sent.

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

• Review a paper trading order ticket before sending it
• Set up the Alpaca MCP server in Claude Desktop
• Record an order fill or prepare a closing sell order

Preserve a product team’s intent and decision context by extracting its user promise, audience, current decisions, open loops, and acceptance criteria. It also connects sitemap changes to product intent and records durable updates as memory events.

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

• Carry product decisions across agent sessions
• Check sitemap changes against product intent
• Capture open questions and acceptance criteria

Create or audit an agent team sitemap and product surface map, checking whether required concepts and validation steps are covered. It identifies omissions, adds task biases to protect important concerns, and records skipped or blocked concepts in a validation ledger.

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

• Audit an agent team's sitemap and roles
• Check product concept coverage
• Find missing validation steps

Prepare a sourced closeout proposal for one existing X1 coordination thread, using an explicit or strong decision from Minutes. X1 drafts the proposal for human review; the skill does not settle payments, contact people, or close the thread automatically.

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

• Preparing a closeout proposal from a meeting decision
• Deferring or escalating an existing X1 thread
• Reviewing a sourced proposal in X1 before human approval

Creates a qualitative project risk register using probability and impact ratings. It documents each risk’s cause, event, and impact, assigns an owner, sorts risks by score, and derives a mitigation plan focused on the highest priorities for review by qualified professionals.

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

• List and prioritize risks for a project
• Assign owners and triggers to identified risks
• Draft mitigation and contingency actions

Review an engagement report draft independently against supplied research, coverage, audience, and template materials. The critique identifies claims that need edits, missing evidence, material omissions, and unnecessary sensitive disclosures without rewriting the report.

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

• Check a draft report against its research
• Find unsupported claims or missing evidence
• Review a report for sensitive disclosures

Use phase-specific references to guide RAI planning, from initial scoping and risk classification to impact assessment, review, and backlog handoff. It provides focused guidance and templates for the phase at hand, including an optional Mural board setup.

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

• Scoping an RAI review with exploratory questions
• Classifying risks and assessing indicators
• Recording impact evidence and tradeoffs

Standardize backlog handoffs from planning workflows to Azure DevOps (ADO) and GitHub. This reference provides shared HTML and Markdown templates, metadata and ID conventions, content sanitization rules, autonomy-tier vocabulary, and disclaimer placement guidance while leaving domain-specific fields to each planner.

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

• Formatting a planning handoff for Azure DevOps
• Preparing GitHub issues with consistent metadata and IDs
• Sanitizing paths and state references before backlog handoff

Guide the creation and governance of Business Requirements Documents (BRDs) and Product Requirements Documents (PRDs) through discovery, definition, validation, and handoff. Use canonical templates, testable requirements, acceptance criteria, traceability links, quality reviews, and lifecycle records to produce actionable documents.

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

• Draft a BRD with scope, stakeholders, and business requirements
• Turn an approved BRD into a structured PRD
• Add testable acceptance criteria and traceability links

Examine a confirmed task, decision, plan, or artifact through adaptive, skeptical questions. The exchange surfaces assumptions, evidence gaps, and unresolved choices, then records the discussion without turning it into a review or solution session.

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

• Surfacing assumptions before starting a task
• Exploring evidence gaps in a plan
• Clarifying boundaries around a decision

Create weekly engagement reports grounded in primary sources such as meetings, email, and boards. Organize completed, ongoing, blocked, and upcoming work for the intended audience, review the claims, and optionally prepare an Outlook draft after approval.

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

• Prepare a weekly status report from meeting and email evidence
• Summarize progress and blockers for an internal audience
• Create an approved Outlook draft from a reviewed report

Use a Python command-line tool to search Jira with JQL, inspect issues, create or update work items, change workflow status, manage comments, and discover required fields. It supports Jira Cloud and Jira Server or Data Center authentication.

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

• Search assigned Jira issues with JQL
• Inspect an issue's status and selected fields
• Create or update a Jira work item

Guide a Design Thinking coach through a consistent coaching approach, quality and fidelity expectations, transitions across nine methods, and session-state recovery. It also describes an optional workflow for creating a canonical slide deck and customer cards.

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

• Keep coaching consistent across Design Thinking sessions
• Decide how to move between methods or iterate
• Save and recover coaching session state

Turn a concrete PRD into a validated hierarchy of work items for Azure DevOps, GitHub, or Jira. The skill checks existing context and supported types through read-only discovery, then produces planning files and a reviewable handoff for a separate execution step.

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

• Breaking a PRD into tracker work items
• Refining an existing backlog hierarchy
• Preparing a reviewed handoff for ADO, GitHub, or Jira

Analyze RFI, RFP, tender, bid, and questionnaire items, connect them to approved business or product evidence, and prepare qualified responses for internal review. It tracks coverage and evidence gaps without treating drafts as approved or externally releasable.

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

• Map RFP questions to approved evidence
• Add business or product claims
• Draft qualified internal responses

Plan backlog work in Azure DevOps, GitHub, or Jira by finding candidate items, reviewing priorities, preparing sprint plans, or resuming interrupted planning. It records recommendations and handoff details in planning files without changing tracker items.

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

• Find backlog items related to a request or document
• Review and prioritize existing work items
• Plan a sprint around capacity, dependencies, and gaps

Use this skill to create one work item or execute a reviewed handoff in Azure DevOps, GitHub, or Jira. It validates the confirmed destination, supports dry runs and resumable batches, and records each attempted change. Tracker updates require an available write surface and appropriate access.

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

• Creating a single issue or work item in a confirmed tracker
• Applying a human reviewed handoff to Azure DevOps, GitHub, or Jira
• Previewing and validating planned tracker changes with a dry run

Provides shared conventions for discovering, reviewing, planning, and executing backlog work across Azure DevOps, GitHub, and Jira. It helps assess duplicates and item quality, apply review gates and sanitization rules, and includes guidance for Azure DevOps pull requests and build information.

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

• Turning a request or PRD into planned work items
• Reviewing backlog items for duplicates and quality
• Planning sprint coverage, dependencies, and gaps