위 분류에 속하지 않는 스킬 (1.4만건)
Guides God Committee members through consensus-building for collective decisions. Use for proposals, voting, and disagreement resolution. Triggers on: consensus, voting, proposal, committee decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds project visions through interactive guided conversation. Use when users have vague ideas needing structure. Triggers on: build vision, I have an idea, start new project, new idea.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Creates new Source of Truth (SoT) files when existing templates don't fit your needs. Triggers on requests to create a new SoT file, add a new artifact type, or when user says "I need to track [X] but there's no SoT for it", "create SoT", "new source of truth". Outputs a properly structured SoT.*.md file with ID prefix, frontmatter, and update protocol.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Allocate launch channels using the Owned / Rented / Borrowed (ORB) framework during PRD v0.9 Go-to-Market. Triggers on requests to pick launch channels, distribute the offer, build a channel portfolio, or when user asks "where do we launch?", "what channels?", "ORB", "owned vs rented vs borrowed", "channel allocation", "channel mix", "Corey Haines launch". Outputs GTM-* entries with Type=Channel, a channel-mix matrix, and a launch sequence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define product positioning using April Dunford's 5-step framework during PRD v0.9 Go-to-Market. Triggers on requests to position the product, define category, frame against competitors, or when user asks "what category are we?", "how do we position?", "Dunford positioning", "obviously awesome", "market frame of reference", "positioning statement". Outputs GTM-* entries with Type=Positioning and BR-POS-* positioning rules.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish weekly customer-discovery cadence and Opportunity Solution Tree practice using Teresa Torres's Continuous Discovery Habits framework during PRD v1.0 Market Adoption. Triggers on requests to set up discovery cadence, build opportunity solution tree, run weekly customer interviews, or when user asks "Torres", "continuous discovery", "opportunity solution tree", "outcomes vs outputs", "weekly interviews", "assumption mapping". Outputs CFD-* discovery entries and updates to ADO-STAGE-* and PER-* with new evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map user missions from trigger to value moment, organizing features into coherent paths during PRD v0.4 User Journeys. Triggers on requests to map user journeys, define user flows, describe how users accomplish goals, or when user asks "map user journeys", "define user flows", "user missions", "how do users accomplish X?", "journey mapping", "what steps do users take?", "pain to value flow". Consumes PER- (Persona Definition), FEA- (Feature Value Planning), KPI- (Outcome Definition). Outputs UJ- entries with step flows, pain points, and value moments. Feeds v0.4 Screen Flow Definition.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extracts durable insights from temp/ files to SoT during EPIC Phase E. Triggers at EPIC completion or explicit `/ghm-harvest` invocation. Outputs new SoT entries and archive manifest.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Synchronizes README.md Command Center with current project state. Triggers on gate changes, EPIC status changes, or explicit `/ghm-status-sync` invocation. Outputs updated README.md dashboard with current lifecycle stage, blockers, and metrics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Install the PRD-Driven Context Engineering methodology into a fresh OR existing repository — the subscription-native alternative to forking the whole repo. Runs an interactive wizard that seeds the framework (.claude/ hooks, skills, agents, rules, scripts) without clobbering product content. Triggers on "install the methodology", "adopt this into my repo", "self-install", "set up PRD lifecycle here", "onboard existing project". Outputs an installed framework + a verification report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect template version drift and guide migration to the latest template version. Compares current repo against the template, identifies what's outdated, and automates safe updates while protecting product-specific content. Triggers on requests to sync with template, update template version, check for template drift, or when user asks "sync template", "update to v3", "template drift", "check template version".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform vague product ideas into evidence-anchored problem statements for PRD v0.1 Spark. Triggers on starting new products/features, validating market opportunities, drafting PRD Why sections, or requests like "frame the problem", "define pain points", "write problem statement", "start v0.1", "what problem are we solving". Outputs structured problem tables with CFD evidence IDs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define and prioritize features with strategic traceability during PRD v0.3 Commercial Model. Triggers on requests to define features, prioritize capabilities, scope MVP, map features to pricing tiers, identify parity vs. delta features, or when user asks "what features do we build?", "what's in MVP?", "which features matter?", "feature priority", "parity features", "what's our delta?". Consumes KPI- (Outcome Definition), BR- (Pricing Model, Moat), and CFD- (Market Moat Analysis) from v0.3. Outputs FEA- entries with strategic traceability and BR-FEA- governance rules. Feeds v0.4 User Journeys.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[1-2 sentence description of what this skill does]. Triggers on [specific phrases/contexts that should activate this skill]. Outputs [what the skill produces].
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Define measurable success metrics (KPIs) tied to product type during PRD v0.3 Commercial Model. Triggers on requests to define success metrics, set KPI targets, determine what to measure, establish go/no-go thresholds, or when user asks "how do we measure success?", "what metrics matter?", "what's our target?", "how do we know if this works?", "define KPIs", "success criteria". Consumes Product Type Classification (BR-) from v0.2. Outputs KPI- entries with thresholds, evidence sources, and downstream gate linkages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates gate criteria before PRD lifecycle advancement by delegating to the readiness scoring pipeline (scripts/readiness.py). Returns a graduated PASS / WARN / BLOCK verdict with top blockers and their causal chain. Triggers before advancing from v0.X to v0.Y or explicit `/ghm-gate-check`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Seed a fresh (greenfield) repository with the PRD-Driven Context Engineering scaffold — PRD.md, SoT/ knowledge files, EPIC templates, domain-profile config, and agent MEMORY starters. Invoked as /prd-ce:init when the plugin is installed. The framework itself (skills, agents, hooks, scripts) ships LIVE in the plugin; this skill only plants the consumer-owned files the plugin cannot carry as behavior. Triggers on "/prd-ce:init", "set up PRD lifecycle here", "scaffold a new PRD-CE project", "initialize the methodology". Outputs a seeded scaffold + a verification report.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Map customer journeys from awareness to advocacy. Visualize touchpoints, identify drop-off points, analyze channel interactions, and optimize the end-to-end experience. Use when the user asks about customer journey, funnel mapping, touchpoint analysis, or experience optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate and maintain llms.txt files for AI discoverability. Scans repos to create curated content maps that help AI answer engines surface your project accurately. Implements the llms.txt specification from Answer.AI.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user has an AI-generated Xiaohongshu draft and wants it to sound more personal, concrete, platform-appropriate, and stronger in hook, retention, and interaction value. Trigger phrases: "去 AI 味", "不像我", "合规检查", "改得像真人", "开头不抓人", "没停留", "humanize draft", "platform check". Do not use for initial positioning or topic generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user has a Xiaohongshu niche and needs to find, compare, and extract reusable content structures from low-follower high-performing posts, or diagnose why a post did or did not become a breakout using click rate, retention, and interaction signals. Trigger phrases: "找对标", "低粉爆款", "拆爆款", "内容骨架", "点击率", "停留时长", "互动率", "competitor pattern", "viral post structure". Do not use before the monetization direction is clear.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cut AI tells from any writing. Must always apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Layered technical-writing standard: Diátaxis structure, Google developer style sentences, STE instruction rules, Global English syntax. Use for /technical-writing or when writing or reviewing docs, RFCs, readmes, PR descriptions, or commit messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.