'planning' 검색 결과

Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan, design-doc folder, roadmap tree, active implementation-status file, repo cleanup/filesystem plan, ADR/decision log, ideas inbox, or linked planning knowledge base; reconcile Done/In Progress/Next state; resume work from TODO/handoff state; move resolved questions into decisions; promote ideas into formal plan artifacts; or keep plan documents and file-structure planning internally consistent without making this project-specific.

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

[omh] Uncertain technical choice for a spike: bounded decision prototype workflow: resolve one uncertain interaction, API, performance, or integration choice with a disposable, isolated experiment whose observed result feeds planning. Use when the user says: decision-prototype, decision prototype, prototype this uncertain choice before planning, prototype before planning, prototype the uncertain choice, run a small spike, small spike, spike solution.

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

Implement load testing, auto-scaling, and capacity planning for Claude API. Use when running performance benchmarks, planning for traffic spikes, or configuring horizontal scaling for Claude-powered services. Trigger with phrases like "anthropic load test", "claude scaling", "anthropic capacity planning", "scale claude api".

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

Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or "make it resilient". Also trigger when designing resilient microservices, planning zero-downtime deployments, or capacity-planning for peak load. Covers stability patterns, capacity planning, deploy/release decoupling, and observability. For data systems, see ddia-systems. For system architecture, see system-design.

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

Performance, load, and reliability (SLO/SRE) planning for production readiness. Use when defining service level objectives, load characterization, capacity, latency budgets, stress/soak/spike test plans, false-positive baselines, and reliability targets. USE FOR: SLO/SLA definition, load testing plan, performance budget, capacity planning, reliability/SRE backlog, latency targets, error-budget policy. DO NOT USE FOR: executing load tests (use Azure Load Testing tooling), security threat modeling, RAI assessment, privacy/compliance planning, or authoring/restating PRD requirements (cite the PRD's existing NFR/FR ids instead).

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

Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.

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

Design a complete lesson study cycle from research question through collaborative planning to research lesson. Use when planning jugyou kenkyuu or collaborative teacher inquiry into practice.

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

Expert guidance for planning and executing cloud adoption using Azure Cloud Adoption Framework. Covers strategy, planning, readiness & landing zones, adoption patterns, governance, security, operations & management, organization & teams, and adoption scenarios. Use when planning AVD, SAP, Oracle, Arc, AI/agent workloads, or Azure landing zones and governance, and other Azure Cloud Adoption Framework related development tasks.

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

Amazon deal planning and promotional strategy optimization. Lightning Deals, Best Deals, Coupons, Prime Exclusive Discounts analysis and ROI calculation. Deal eligibility assessment, timing optimization, and promotional campaign planning. Use when the user asks about Amazon deals, Lightning Deals, promotional planning, deal strategy, or Amazon promotions.

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

Use when you need GitHub CLI (`gh`) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for traceability. This should trigger for requests such as GitHub issue inventory workflow; GitHub CLI setup for issues; Prepare issue traceability lists; Analyze repository planning artifacts linked to GitHub issues. Part of Plinth Toolkit

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

Core planning principles for Portfolio Buddy 2 development. Use when: planning any feature implementation, modification, or refactoring. Ensures code preservation, mobile/desktop optimization, and thorough requirement gathering.

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

Generate structured planning documentation for web projects with context-safe phases, verification criteria, and exit conditions. Creates IMPLEMENTATION_PHASES.md plus conditional docs (DATABASE_SCHEMA, API_ENDPOINTS, UI_COMPONENTS, CRITICAL_WORKFLOWS). Use when: starting new Cloudflare Workers/React projects, adding major features to existing apps, breaking large work into manageable phases, or need verified planning before coding begins.

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

Performs deep architectural analysis of a specified module, directory, or feature area by examining structural coupling, data flow, concurrency patterns, risk, and SOLID alignment. Use when the user wants to assess, evaluate, or review the architecture, design quality, dependency structure, coupling, cohesion, or technical debt of an existing part of the codebase. Not for investigating specific bugs, runtime errors, or failures — use investigate. Not for test planning — use automated-test-planning. Not for file-level code review — use code-review. Not for researching open-ended options, prior art, or how something works — use research. Not for designing a new interface or contract — use design-an-api. Not for planning the change its findings imply — use plan-a-change. Not for discovering bounded contexts, ubiquitous language, or where code boundaries diverge from domain boundaries — use ddd-analysis. Not for writing documentation or architectural decision records.

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

Guides conducting privacy law gap analysis for market entry into new jurisdictions. Covers target jurisdiction assessment, existing compliance mapping, remediation effort estimation, and implementation timeline planning. Keywords: gap analysis, market entry, jurisdiction assessment, remediation planning, compliance mapping.

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

Binder design campaign planning, monitoring, and troubleshooting. Use this skill when: (1) Planning a complete binder design campaign, (2) Converting high-level goals into runnable pipelines, (3) Assessing campaign health and pass rates, (4) Diagnosing why designs are failing QC, (5) Estimating time, cost, and expected yields, (6) Selecting between design tools for a specific target. This skill orchestrates the other protein design tools. For individual tool parameters, use the specific tool skills.

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

Goal-oriented binder design campaign planning and health assessment. Use this skill when: (1) Planning a complete binder design campaign, (2) Converting high-level goals into runnable pipelines, (3) Assessing campaign health and pass rates, (4) Diagnosing why designs are failing QC, (5) Estimating time, cost, and expected yields, (6) Selecting between design tools for a specific target. This skill orchestrates the other protein design tools. For individual tool parameters, use the specific tool skills.

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

Produce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.

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

Produce a risk matrix or heatmap that quantifies what could break by business impact × probability, runs failure mode analysis on the top items, and maps test coverage to risk zones. Includes stakeholder interview frameworks and continuous reassessment. Run this BEFORE test-strategy or test-planning. Use when: "risk assessment," "risk matrix," "risk heatmap," "what could break," "critical paths," "failure modes," "where to focus testing." Not for: multi-quarter QA direction — use test-strategy. Not for: a single sprint/release test plan — use test-planning. Not for: hands-on session-based bug hunting — use exploratory-testing. Related: test-strategy, test-planning, release-readiness, qa-metrics.

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

个人投资理财 (个人投资理财 (Personal Investing & Financial Planning) (从业者/自主投资者视角) — 个人与家庭自主管理投资组合、做长期财务规划的认知操作系统。覆盖: (a) 四大流派互掐 (本行业最有价值的智识谱系) — 价值投资 (Graham 安全边际 / Buffett·Munger 护城河+能力圈)、被动指数 (Bogle 成本至上+市场组合+定投)、技术分析 (趋势线/形态/动量择时)、趋势/动量跟踪 (CTA/双动量/turtle); (b) 资产配置与组合构建 — 股/债/现金/另类的配置框架 (60/40、全天候 All-Weather、三基金组合 three-fund、再平衡)、风险预算、定投 (DCA) vs 一次性; (c) 工具栈 — 券商/交易平台、组合追踪 (Portfolio Visualizer/Morningstar/雪球)、ETF/基金筛选与费率、回测、税优账户 (401k/IRA/Roth vs 中国养老 Y 账户); (d) 行为金融与风险管理 — 损失厌恶/过度交易/择时谬误、仓位与回撤管理、再平衡纪律; (e) 财务规划脚手架 — 应急金、目标-时间轴-风险承受度、退休/教育金规划、税务效率。主战场 = 美股/全球指数 (canon 母语区) + A 股/港股/公募基金 (zh-CN 散户层)。核心分歧: 主动选股 vs 被动指数 (是否能持续跑赢市场)、基本面 vs 技术面 (价格是否已反映信息 / EMH 强弱)、择时 vs 持有 (market timing vs time in market)、集中 vs 分散。不含: 持牌为他人理财的展业 (FA/RIA/投顾资质与合规销售)、机构资管/量化高频/对冲基金策略、投行/卖方研究、加密货币投机与 meme 炒作、日内打板/杠杆赌博式交易。) Master OS — automated mastery of 个人投资理财 (Personal Investing & Financial Planning) (从业者/自主投资者视角) — 个人与家庭自主管理投资组合、做长期财务规划的认知操作系统。覆盖: (a) 四大流派互掐 (本行业最有价值的智识谱系) — 价值投资 (Graham 安全边际 / Buffett·Munger 护城河+能力圈)、被动指数 (Bogle 成本至上+市场组合+定投)、技术分析 (趋势线/形态/动量择时)、趋势/动量跟踪 (CTA/双动量/turtle); (b) 资产配置与组合构建 — 股/债/现金/另类的配置框架 (60/40、全天候 All-Weather、三基金组合 three-fund、再平衡)、风险预算、定投 (DCA) vs 一次性; (c) 工具栈 — 券商/交易平台、组合追踪 (Portfolio Visualizer/Morningstar/雪球)、ETF/基金筛选与费率、回测、税优账户 (401k/IRA/Roth vs 中国养老 Y 账户); (d) 行为金融与风险管理 — 损失厌恶/过度交易/择时谬误、仓位与回撤管理、再平衡纪律; (e) 财务规划脚手架 — 应急金、目标-时间轴-风险承受度、退休/教育金规划、税务效率。主战场 = 美股/全球指数 (canon 母语区) + A 股/港股/公募基金 (zh-CN 散户层)。核心分歧: 主动选股 vs 被动指数 (是否能持续跑赢市场)、基本面 vs 技术面 (价格是否已反映信息 / EMH 强弱)、择时 vs 持有 (market timing vs time in market)、集中 vs 分散。不含: 持牌为他人理财的展业 (FA/RIA/投顾资质与合规销售)、机构资管/量化高频/对冲基金策略、投行/卖方研究、加密货币投机与 meme 炒作、日内打板/杠杆赌博式交易。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 个人投资理财 (Personal Investing & Financial Planning) (从业者/自主投资者视角) — 个人与家庭自主管理投资组合、做长期财务规划的认知操作系统。覆盖: (a) 四大流派互掐 (本行业最有价值的智识谱系) — 价值投资 (Graham 安全边际 / Buffett·Munger 护城河+能力圈)、被动指数 (Bogle 成本至上+市场组合+定投)、技术分析 (趋势线/形态/动量择时)、趋势/动量跟踪 (CTA/双动量/turtle); (b) 资产配置与组合构建 — 股/债/现金/另类的配置框架 (60/40、全天候 All-Weather、三基金组合 three-fund、再平衡)、风险预算、定投 (DCA) vs 一次性; (c) 工具栈 — 券商/交易平台、组合追踪 (Portfolio Visualizer/Morningstar/雪球)、ETF/基金筛选与费率、回测、税优账户 (401k/IRA/Roth vs 中国养老 Y 账户); (d) 行为金融与风险管理 — 损失厌恶/过度交易/择时谬误、仓位与回撤管理、再平衡纪律; (e) 财务规划脚手架 — 应急金、目标-时间轴-风险承受度、退休/教育金规划、税务效率。主战场 = 美股/全球指数 (canon 母语区) + A 股/港股/公募基金 (zh-CN 散户层)。核心分歧: 主动选股 vs 被动指数 (是否能持续跑赢市场)、基本面 vs 技术面 (价格是否已反映信息 / EMH 强弱)、择时 vs 持有 (market timing vs time in market)、集中 vs 分散。不含: 持牌为他人理财的展业 (FA/RIA/投顾资质与合规销售)、机构资管/量化高频/对冲基金策略、投行/卖方研究、加密货币投机与 meme 炒作、日内打板/杠杆赌博式交易。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「个人投资理财」「个人投资」「理财」「personal investing」「资产配置」

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

Structured planning mode for AI agents working on coding and development tasks. Produces a comprehensive plan BEFORE any code is written or changed, including task decomposition, architecture decisions, risk assessment, and approval gates. Use this skill whenever the user says "/plan", "plan mode", "plan first", "think before coding", "make a plan", or asks the agent to plan before executing. Also trigger when the user describes a complex multi-step development task and would clearly benefit from structured planning before implementation — especially for tasks involving new features, refactors, migrations, infrastructure changes, or multi-file edits. When in doubt, plan. A few minutes of planning prevents hours of rework.

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

Research, expand, and cluster keywords for content strategy. Use when planning content topics, building keyword lists, expanding seed keywords, clustering by topic and intent, or mapping keywords to funnel stages. Triggers on "keyword research," "keyword expansion," "keyword clustering," "content topics," "what to write about," "topic ideation," "content planning," "6 circles method," "seed keywords," "keyword difficulty," "search volume," "intent mapping," "pillar content strategy," or "content calendar planning." For SEO optimization and auditing, see seo-and-aeo-strategy.

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

Unified skill for content strategy and marketing content strategy: content pillars, editorial calendars, keyword research by buyer stage, positioning, messaging hierarchy, trust-building, GEO/AI search optimization, and ROI measurement. Also handles content briefs, SEO briefs, content outlines for writers, on-page SEO optimization, meta descriptions, title tags, keyword density, content research, source discovery, expert sourcing, and information gathering. Use when planning content strategy, creating content briefs for writers, optimizing existing content for SEO, researching topics and sources, or managing editorial operations. Triggers: content strategy, marketing content strategy, content marketing strategy, content planning, editorial calendar, content pillars, messaging hierarchy, content brief, SEO brief, content outline, keyword research, buyer journey content, GEO optimization, AI search optimization, content ROI, content operations, content roadmap, brand messaging, positioning

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

Design a complete lesson study cycle from research question through collaborative planning to research lesson. Use when planning jugyou kenkyuu or collaborative teacher inquiry into practice.

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

CERTIFIED FINANCIAL PLANNER professional providing comprehensive financial planning across all CFP Board practice domains. Integrates retirement, investment, tax, estate, insurance, and education planning following CFP Board Code of Ethics and Standards of Conduct. Use for holistic financial plans, cash flow analysis, net worth statements, insurance needs, estate planning coordination, education funding (529 plans), tax strategies, retirement projections, or CFP Board Practice Standards compliance.

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