'phases' 검색 결과

Build a paid advertising plan around business goals and financial constraints. Define channels, campaigns, audiences, budgets, creative, tracking, and experiments, then organize the work into phases with owners, success measures, and conditions for stopping or reversing changes.

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

• Creating an advertising strategy around business goals
• Planning channel roles and budget allocation
• Defining launch phases, owners, and success measures

Design, implement, tune, and test action combat for web games with clear attack and defense timing. Define reliable hit outcomes, give defensive moves distinct purposes, and verify that visual feedback matches combat results in repeatable scenarios.

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

• Tuning attack, guard, and dodge timing
• Checking hit detection and combat feedback
• Designing boss phases and defensive choices

Build and tune enemy behavior for action games, including targeting, movement, attacks, retreats, and boss phases. Organize decisions into explicit states, make attacks readable to players, and check behavior with repeatable tests and browser encounters.

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

• Implementing enemy detection, pursuit, and retreat
• Tuning attack warnings and combat spacing
• Debugging boss phases and interrupted actions

Trace how AI tooling developed in a Git repository by identifying configuration file origins, monthly commit activity, major changes, and relevant releases. Produce a Markdown report that explains adoption phases and turning points using Git evidence.

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

• Finding when AI configuration files were first introduced
• Reviewing monthly activity around AI tooling changes
• Tracing major integrations and workflow changes

[omh] Decided cross-module refactor to phase: refactor planning - turn a decided boundary-changing refactor into a phased plan - reconnaissance, contracts-first phase order, per-phase verification and rollback, a files table, and an explicit approval gate before any edit. Use when the user says: refactor-plan, refactor plan, plan this refactor, plan the refactor, refactor planning, refactor phases, phased refactor, refactor in phases.

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

Use when a milestone audit reported gaps and you want the fix phases created in one pass. Reads MILESTONE-AUDIT.md, groups gaps into phases, adds them to ROADMAP.md and offers to plan each one.

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

Use when .planning/phases/ has accumulated directories from completed milestones. Shows a dry-run of what moves to .planning/milestones/v{X.Y}-phases/ and archives only after confirmation.

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

Use when designing space missions, computing launch windows, optimizing trajectories, analyzing payload constraints, or planning mission phases and contingencies. Use when "mission design, launch window, trajectory optimization, mission timeline, mass budget, propellant budget, mission phases, porkchop plot, C3, gravity assist, low thrust, mission architecture, LEO, GEO, interplanetary, " mentioned.

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

Writes implementation plans before coding: phases, plan files, specs, definition of done. Use when planning a multi-step feature or breaking a large refactor into phases.

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

Audit a skill by running a paired probe — the same task once with the skill loaded and once without — segment both traces into goal-directed phases, align phases, and emit a SIP report (surface anchoring, template copy, excess planning, task recovery, off-task artifact). Use whenever a skill is created, modified, or proposed for retirement. Pass-rate is BLIND to most skill effects: CTA (arxiv 2605.11946v1) shows a single skill can produce 522 measurable behavioural changes across 49 tasks while pass-rate moves only +0.3%. Triggers: "audit this skill", "is this skill helping", "retire skill", "before shipping skill", "behavioural impact of skill X", or any skill review event.

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

6-phase multi-agent pipeline with approval gates. Orchestrates Plan→Design→Implement→Review→Test→Deploy phases with explicit entry/exit criteria, phase-level agent assignment, and human-in-the-loop approval checkpoints.

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

아직 없는 기능을 조사와 계획부터 테스트 우선 구현, 검토, 커밋까지 진행합니다. 단계별로 ECC 에이전트에 작업을 나누고 계획 승인과 커밋 전 확인을 거칩니다.

• 아직 구현되지 않은 기능 추가
• 테스트를 먼저 작성하는 새 기능 개발
• 인증 기능의 보안 검토

Plan market, competitor, consumer, or financial research with chapter outlines, data requirements, and chart plans. Then turn collected evidence into a structured Markdown report with comparisons, citations, and strategic implications, while clearly identifying missing data.

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

• Planning research chapters and data collection requirements
• Turning market and competitor findings into a report
• Organizing consumer insights and brand strategy analysis

Review implemented features against their requirements, add missing tests, and check performance constraints. Produce documentation, a table linking requirements to code and tests, and evidence showing whether the feature is ready for deployment.

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

• Review an implementation against its specification
• Add tests for uncovered requirements
• Link requirements to code and passing tests

Turn an approved specification into pseudocode, a plain outline of program logic, and an architecture defining module responsibilities and API inputs and outputs. After user confirmation, proceed with implementation and unit tests based on those designs.

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

• Turning an approved specification into pseudocode
• Defining module boundaries and dependency rules
• Designing API inputs, outputs, and error responses

Capture lessons from completed tasks, train patterns from explicit examples, and consolidate accumulated learning into long-term storage. Use SONA and MicroLoRA adaptation tools for individual domains, then verify results in the appropriate stores.

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

• Capturing lessons after a successful task
• Consolidating accumulated task histories
• Creating learning adapters for separate domains

Start AI Engineering from Scratch with a brief interview and placement quiz. Create a persistent LEARNING.md study plan recording your goals, starting phase, pace, and learning path for later sessions with the learn skill.

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

• Creating a study plan when starting the curriculum
• Choosing a starting phase based on current knowledge
• Recording learning goals, available time, and a build goal

Build and review HyperFrames animations using motion recipes, scene templates, and transitions. Find guidance for seven animation runtimes, including GSAP and Three.js, and inspect existing scenes for timing gaps and inconsistent motion.

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

• Combine motion recipes for text and shapes
• Build scenes with several animation phases
• Choose an animation runtime

Organize API documentation work from endpoint discovery to OpenAPI specifications, developer guides, and tested code examples. The workflow also covers interactive documentation, documentation sites, and maintenance, helping select the phases and supporting skills needed for a task.

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

• Create an OpenAPI specification from an existing API
• Write getting-started and authentication guides
• Prepare and test API request examples

Plan AI application development by selecting relevant phases and companion skills. The workflow covers language model integration, retrieval from documents, agents, machine learning pipelines, monitoring, and security, with prompts and quality checklists.

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

• Plan AI features and language model integration
• Organize RAG retrieval design and implementation
• Map agent roles, tools, and memory

Assess a new or existing AI project by examining its code, goals, and constraints. Recommend skills confirmed to exist in the available registry, then outline tasks and implementation phases with dependencies, completion criteria, and checks.

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

• Planning the first steps of a new AI project
• Assessing technical issues in an existing project
• Selecting relevant skills from an available registry

Plan enterprise customer onboarding from contract handoff through rollout and continued use. Provides four phases, readiness checklists, ownership checks, and adoption measures to address stalled communication, weak pilot usage, and declining engagement after launch.

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

• Plan onboarding for a new enterprise customer
• Clarify customer ownership before kickoff
• Investigate stalled communication during implementation

Build a Solution Blueprint for a Dynamics 365 Finance and Supply Chain Management implementation through guided interviews. Define scope and architecture, compare options, and document decisions, their rationale, assumptions, and unresolved questions across working sessions.

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

• Create an architecture blueprint for a new D365 implementation
• Define implementation scope and rollout phases
• Compare data migration and integration approaches

Connect a local CopilotKit agent to Slack through a managed Intelligence Channel. The skill guides dedicated Slack app creation, credential setup, runtime configuration, and checks that a human mention receives an actual reply.

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

• Setting up a dedicated Slack bot for a local agent
• Investigating a Channel stuck waiting for its runtime
• Diagnosing mentions that receive no reply