'plan' 검색 결과

명세나 요구 사항을 변경 파일, 함수 정의, 테스트와 검증 절차가 명확한 구현 계획으로 정리합니다. 코드를 쓰기 전에 작업을 나누고 다른 담당자에게 인계할 수 있게 합니다.

• 코드 작성 전 기능 구현 계획 수립
• 요구 사항을 테스트 가능한 작업으로 분할
• 다른 담당자나 에이전트에게 구현 인계

구현 전 UI/UX 계획을 디자이너의 관점에서 검토하고 항목별로 평가합니다. 대화로 빠진 설계 결정을 구체화해 개선 사항을 계획에 직접 반영합니다.

• 구현 전 UI/UX 계획을 점검할 때
• 빠진 설계 결정을 찾고 싶을 때
• 디자인 검토 의견을 계획에 반영할 때

연간 마케팅 계획과 신제품 발표를 성장 및 영업 기회 창출과 연결해 설명하고, 구성과 본문, 시각 표현을 갖춘 잡지 스타일 HTML 슬라이드로 만듭니다.

• 연간 마케팅 계획 승인 자료 제작
• 신제품 출시 계획 설명
• 활동 예산과 성장 목표 연결

Turn a math or science video idea into a detailed scene plan. Research the topic, clarify the audience, and outline visuals, narration, transitions, and implementation notes for Manim, an animation tool.

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

• Turn a rough explainer idea into a scene plan
• Plan intuitive math and science visuals
• Adapt video depth to the audience

Execute a written work plan by assigning implementation and verification to subagents. Track progress, isolate work in Git worktrees, record test evidence, and require independent verification before marking tasks complete, with optional pull request delivery.

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

• Executing a saved work plan
• Assigning independent tasks to parallel agents
• Resuming work with recorded progress and evidence

Review AWS spending and identify savings through resource sizing, unused resource cleanup, discount commitments, and storage policies. It also guides budget alerts and recurring cost reviews so teams can track spending and plan changes using usage data.

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

• Investigating an unexpected AWS bill increase
• Preparing cost reviews with engineering and finance
• Comparing Savings Plans and Reserved Instances

Follow Conductor's development plans using test-driven development: write a failing test, implement the change, then improve the code. Manage phase verification, progress updates, and focused git commits as tasks move toward completion.

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

• Implementing tasks from plan.md
• Following the test-driven development cycle
• Verifying completion at phase checkpoints

Turn an understood task into an ordered implementation plan in Codewhale. Clarify the goal and constraints, identify which steps depend on others, and record verification methods, risks, and open questions before broader implementation begins.

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

• Planning implementation for a clearly defined task
• Ordering steps that depend on one another
• Adding verification to risky steps

Analyzes one .NET project to plan integration tests for an Oracle-to-PostgreSQL migration. Identifies database access methods, prioritizes migration risks, and documents test cases, seed data, and coverage, including empty strings, NULL values, and timezone behavior.

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

• Identifying database access methods that need integration tests
• Prioritizing tests for Oracle-specific behavior
• Planning checks for empty strings, NULL values, and timezones

Turn feature requirements and technical plans into a structured GitHub project plan. Break work into linked issues, define acceptance criteria, dependencies, priorities, and estimates, and outline board settings and automated progress tracking.

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

• Breaking feature requirements into GitHub Issues
• Mapping dependencies and setting work priorities
• Preparing sprint estimates and completion criteria

Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.

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

• Deliver an issue from requirements clarification through verification
• Turn an initial idea into a reviewed implementation plan
• Resume interrupted work from its saved phase

Design autonomous AI agents that break goals into tasks, use tools, and review their own work. Covers reasoning and action loops, separate planning and execution, and reliability measures such as cost limits, validation, and logging.

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

• Choosing how an agent plans and executes tasks
• Breaking goals into constrained steps
• Adding self-review and correction to an agent

Organize complex tasks with three Markdown files for plans, findings, and progress. Keep goals, decisions, errors, and test results available across sessions so the agent can review its position and continue work with a clear next step.

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

• Planning and tracking a task with multiple phases
• Saving findings during a research project
• Recording implementation progress and test results

Turn a Factory work item into a phased implementation plan grounded in current code and project history. Document scope, changes, tests, risks, and assumptions, then hand the plan to the execution stage.

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

• Planning implementation after issue triage
• Defining changes and verification for each phase
• Recording design choices and rejected alternatives

Examine a plan by imagining it has failed twelve months later. Identify weak assumptions, linked dependencies, and commitments that are hard to reverse, then outline validation steps and criteria for continuing, changing direction, or stopping.

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

• Reviewing a plan before committing major resources
• Checking assumptions before a board or investor presentation
• Examining plans that receive only positive feedback

Size support and operations teams using demand ranges and queueing calculations, which estimate how work waits for service. Assess workload imbalance and service target risks, then build a quarterly hiring plan that accounts for training time and attrition.

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

• Estimate staffing for support and operations queues
• Check workload imbalance and service target risks
• Build quarterly hiring plans with ramp time and attrition

Turn a research experiment plan into training and evaluation code, run a small setup check, and launch GPU experiments. Collect initial metrics and update progress records so the results are ready for further review.

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

• Implementing experiments from a written plan
• Checking a small run before full GPU experiments
• Collecting baseline and main-method results

View and edit whiteboards embedded in 飞书 cloud documents. Export previews, SVG vector images, diagram source code, or structural data, and update boards using Mermaid, PlantUML, SVG, or the native OpenAPI format.

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

• Exporting whiteboards as images
• Retrieving diagram source code
• Updating boards from Mermaid or PlantUML code

Review code changes in Plannotator’s browser interface and have the agent address returned comments. Choose the current working directory, another checkout, or a pull or merge request URL, with options to focus on a specific comparison base.

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

• Review changes in the current working directory
• Review a separate working directory
• Review a pull or merge request by URL

Prepare and publish a Plannotator release with contributor credits, coordinated version updates, ordered builds, and tag-triggered publishing. The workflow also checks package contents, security scan results, and evidence showing how release files were built.

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

• Draft release notes with contributor credits
• Update versions consistently across package files
• Check builds and package contents before release

Guide feature development from a human-reviewed plan to testable requirements, implementation, and independent verification. Record each requirement with a concrete proof, then have a separate agent check the work and produce a verification report.

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

• Prepare a feature plan for human review
• Turn approved requirements into checks with concrete proof
• Implement a feature against agreed checks

Guide new feature work from requirements and planning through revisions and implementation. Create Markdown plans with acceptance criteria, track progress, and ensure frontend tasks have a UI design before development begins.

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

• Turn a feature idea into an implementation plan
• Revise a plan based on feedback
• Start implementation from an agreed plan

Turn specifications into a detailed implementation plan before coding. Break work into small tasks with exact file paths, code, test commands, and interfaces so another developer or agent can follow the plan.

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

• Planning a feature before coding
• Preparing a development handoff
• Breaking requirements into testable tasks

Apply improvement plans from skill-quality-reviewer to Claude Skills. Groups edits by file, handles conflicting recommendations by priority, backs up originals, and verifies the updates before producing a report of changes and verification results.

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

• Applying recommended fixes from a skill quality review
• Updating SKILL.md and reference files from a plan
• Resolving conflicting improvement recommendations