'context-engineering' 검색 결과

Design the changelog as a distribution surface bridging engineering releases (DEP-/FEA-) to marketing channels (GTM-) during PRD v0.8 Deployment & Ops. Triggers on requests to set up a changelog system, publish releases, or when user asks "how should we publish releases?", "changelog as marketing", "release notes", "Stripe-style changelog", "what to do with our release notes", "ship and tell". Outputs MON-CHG-* changelog entries and per-channel formats.

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

Establish channels and processes for capturing and processing post-launch feedback during PRD v0.9 Go-to-Market. Triggers on requests to set up feedback systems, capture user input, or when user asks "how do we collect feedback?", "feedback loop", "user research", "post-launch feedback", "customer feedback", "NPS", "voice of customer". Outputs CFD- entries specialized for post-launch feedback capture.

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

Map the competitive landscape before positioning your product for PRD v0.2 Market Definition. Triggers on completing v0.1 Spark, analyzing competitors, researching market, or requests like "competitive analysis", "who else solves this", "market landscape", "what alternatives exist", "competitor research", "feature comparison". Outputs CFD- entries for competitive intelligence and BR- entries for positioning rules.

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

Audit how AI search engines (ChatGPT, Perplexity, Google AI Overviews, Claude) describe and recommend your product, then propose fixes. Triggers on requests to audit AI search visibility, improve AEO/GEO, check ChatGPT/Perplexity coverage, or when user asks "do we show up in AI search?", "AEO audit", "generative engine optimization", "AI discoverability", "how does ChatGPT describe us?", "Perplexity ranking". Outputs GTM-AEO-* entries and a Coverage Matrix.

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

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 monitoring strategy, metrics collection, and alerting thresholds during PRD v0.8 Deployment & Ops. Triggers on requests to set up monitoring, define alerts, or when user asks "what should we monitor?", "alerting strategy", "observability", "metrics", "SLOs", "dashboards", "monitoring setup". Outputs MON- entries with monitoring rules and alert configurations.

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

Establish baseline → snapshot → compare → history monitoring for any KPI, config, or metric that can drift during PRD v0.8 Deployment & Ops. Triggers on requests to monitor drift, baseline a value for later comparison, or when user asks "how do we track if X changes?", "baseline this", "config drift", "performance regression", "metric drift", "compare to last week", "is this getting worse?". Outputs MON-DRIFT-* entries with baseline + comparison rules.

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

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.

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

Select and validate pricing model for PRD v0.3 Commercial Model. Triggers on requests to set pricing, choose monetization model, design pricing tiers, validate willingness to pay, or when user asks "how much should we charge?", "what pricing model?", "freemium vs paid?", "how to structure tiers?", "price point?". Consumes Competitive Landscape (CFD-) and Product Type (BR-) from v0.2. Outputs BR- entries for pricing rules, tier boundaries, and competitive positioning.

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

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.

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

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.

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

Transform validated pain points into articulated user value statements for PRD v0.1 Spark. Triggers on completing problem framing, defining user outcomes, articulating value propositions, or requests like "what value do users get", "define outcomes", "articulate the benefit", "finish v0.1", "pain to value", "what do they gain". Outputs CFD- entries tagged as value hypotheses with evidence tiers. Follows Problem Framing skill in workflow.

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

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.

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

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.

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

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".

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

Systematically harvest short testimonials from customers via NPS, milestones, post-purchase, and email during PRD v1.0 Market Adoption. Triggers on requests to collect testimonials, set up social proof harvest, gather customer quotes, or when user asks "how do we get testimonials?", "social proof harvest", "NPS responses", "testimonial wall", "customer quotes", "post-purchase survey", "milestone follow-up". Outputs CFD-TST-* testimonial entries and GTM-TST-* placement assets.

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

Apply Rob Fitzpatrick's Mom Test discipline to customer interviews during PRD v1.0 Market Adoption. Triggers on requests to interview customers, run discovery calls, validate ideas with users, or when user asks "how do I interview customers?", "Mom Test", "Rob Fitzpatrick", "customer interview", "user research without lies", "talking to humans", "discovery conversation". Outputs CFD-* discovery entries with Mom Test-calibrated confidence.

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

Context-driven AI development with AGENTS.md, repo knowledge bases, Claude Code, Codex, and Copilot. Use when adopting repo-native AI workflows or multi-repo setups.

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

Creates reusable vector-brain implementations: repo, docs, compliance. Use when building pgvector SQL, manifests, ingest scripts. Not for context design (dev-context-engineering).

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

Designs cross-session agent memory: point-in-time facts, consolidation, tenant isolation. Use when auditing user memory or Mem0/Zep. Not for repo context (dev-context-engineering).

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

Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.

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

Check context usage limits, monitor time remaining, optimize token consumption, debug context failures. Use when asking about context percentage, rate limits, usage warnings, context optimization, agent architectures, memory systems.

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

Use when a long session has accumulated stale or conflicting context or the user asks to refresh it. Not for remote, credential, publish, deploy, or irreversible changes.

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

Master context engineering for AI agent systems. Use when designing agent architectures, debugging context failures, optimizing token usage, implementing memory systems, building multi-agent coordination, evaluating agent performance, or developing LLM-powered pipelines. Covers context fundamentals, degradation patterns, optimization techniques (compaction, masking, caching), compression strategies, memory architectures, multi-agent patterns, LLM-as-Judge evaluation, tool design, and project development.

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