'decision' 검색 결과

Use when the user wants the existing codebase analyzed for planning — 'mapear o código', 'analisar o projeto', 'atualizar o contexto', 'map codebase' — or when a planning skill reports a missing or stale map. Runs a deterministic read-only evidence scan and writes codebase.md plus the architecture, conventions, testing and concerns context documents under .planning/feat/. Do NOT use for code review (feat-review), architecture decisions, or writing the project instructions file (feat-setup).

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

Write and refine high-quality user stories — INVEST criteria, "As a X, I want Y, so that Z" format, Gherkin acceptance criteria when applicable, definition of ready, anti-patterns, and a review checklist. Use when creating or reviewing user stories, PRD section 6, backlog items, or acceptance criteria. Do NOT use for technical specs, architecture decisions, or task decomposition.

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

Use when the user wants to query the local pwdev audit trail — 'ver auditoria', 'relatório de auditoria', 'audit stats', 'exportar auditoria em PDF' — summary, events, decisions, artifacts, statistics, a Markdown/PDF export or a custom read-only SELECT. Do NOT use to enable the audit (feat-init) or for plan status (feat-status).

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

Prepare or update a Fabric pull request by proving the changeset-or-skip decision, validation evidence, DCO sign-off, and public-safe PR metadata. Use before the first push, after later revisions, or when asked to create or update a PR. Do not use to review an unrelated PR or authorize relay.

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

Research competitors, analyze market positioning, identify differentiators, and understand competitive landscape to inform product strategy and positioning. Use when researching competitors, analyzing features, identifying market gaps, understanding pricing strategies, evaluating competitive advantages, researching market trends, or informing product decisions.

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

Create comprehensive technical documentation including API docs, component libraries, README files, architecture diagrams, and developer guides using tools like JSDoc, Storybook, or Docusaurus. Use when documenting APIs, creating component documentation, writing README files, generating API references, documenting architecture decisions, creating onboarding guides, maintaining changelogs, documenting configuration options, or building developer documentation sites.

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

Systematically review pull requests, feature implementations, and code changes to ensure quality, maintainability, security, and adherence to best practices. Use when reviewing code before merging, conducting peer reviews, performing self-reviews, auditing code quality, checking for security vulnerabilities, ensuring consistent coding standards, verifying test coverage, assessing performance implications, evaluating architectural decisions, or providing constructive feedback to improve team code quality.

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

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.

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

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see page-cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing-strategy.

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

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

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

YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to "brainstorm this", "I have an idea", "help me think through this", "office hours", or "is this worth building". Proactively invoke this skill (do NOT answer directly) when the user describes a new product idea, asks whether something is worth building, wants to think through design decisions for something that doesn't exist yet, or is exploring a concept before any code is written. Use before /plan-ceo-review or /plan-eng-review. (gstack)

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

Save working context. Captures git state, decisions made, and remaining work so any future session can pick up without losing a beat. Use when asked to "save progress", "save state", "context save", or "save my work". Pair with /context-restore to resume later. Formerly /checkpoint — renamed because Claude Code treats /checkpoint as a native rewind alias in current environments, which was shadowing this skill. (gstack)

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

Survey available blocks from local AEM Edge Delivery Services project and Block Collection to understand the block palette available for authoring. Returns block inventory with purposes to inform content modeling decisions.

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

Guides ownership, borrowing, and lifetime decisions in Rust. Use when encountering E0382, E0597, E0506, E0507, move errors, or when designing data ownership.

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

Guides concurrency and async decisions in Rust. Use when encountering Send/Sync errors (E0277), choosing between threads vs async, designing shared state, or debugging deadlocks.

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

Guides generic vs trait object decisions in Rust. Use when choosing between static and dynamic dispatch, designing traits, handling E0277/E0038, or deciding between enum and dyn Trait.

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

Deep reasoning mode for complex problems requiring maximum cognitive depth. Use when facing difficult architectural decisions, complex debugging, multi-step problem solving, or situations requiring careful analysis before implementation.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.

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

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

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

Write or revise AI-learning-notes article pages in "寫文章模式" when the user asks for articles, technical articles, blog posts, bilingual versions, article formatting consistency, shared article-base alignment, responsive layout, summary/TOC decisions, contrast, or publishing-flow compatibility.

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

Write a Product Soul document — the strategic north star that sits above any PRD or feature spec. Captures the product's reason for existing across five lenses: user, business, strategy, product-market fit, and GTM distribution. Load when the user asks to write a product soul, product strategy doc, product north star, product positioning doc, product one-pager, or "why we exist" document. Also triggers on "write the soul of this product", "product strategy document", "what is this product really about", "capture the product vision", or when an agent needs strategic context before making product decisions. The output is docs/product-soul.md — a living document that brainstorming, prd-writing, and inversion can reference for grounding.

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

Compress bloated project or global memory while preserving decisions, rationale, revisit triggers, provenance, and active user preferences. Load when memory exceeds budget, global memory is too large, session logs are repetitive, or before appending to an over-budget memory file.

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

Load bounded working context at the start of a coding session. FIRES ON EVERY FIRST USER MESSAGE in a fresh session, regardless of content — including bare greetings ("hi", "hello", "hey"), task-only openers, or "let's start". Also triggers on: "fresh session", "session start", "first message in a new thread", "new chat", "cold start", "begin work in this repo", "starting work", "continue from prior session", "what were we working on", "resume", "what happened last time", "load memory", "recall context", "create a handoff", "prior session context", "latest handoff", "current state", "decision context". Skip ONLY if the user explicitly says "fresh start" or "ignore prior context". Self no-ops if invoked mid-session when context is already loaded.

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