'implementation' 검색 결과

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

Add a text-to-speech engine to Voicebox through dependency research, backend implementation, interface updates, and packaging. The workflow covers development checks and verification of the packaged application before handing the build over for local testing.

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

• Integrate a new speech synthesis engine into Voicebox
• Audit model dependencies before implementation
• Add engine choices and language settings to the interface

Delegate a feature, bug fix, or substantial code change and carry it through implementation, review, and verification. Start from a task description or issue link, with options for the workflow route and review depth.

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

• Delegating implementation of a new feature
• Fixing a bug described in an issue
• Choosing review depth for a substantial code change

Delegate code analysis and implementation in a selected project to Claude Code without an interactive session. The skill reads structured results, reports failures, and supports comparing its findings with another coding agent.

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

• Request a code review without changing files
• Delegate implementation to Claude Code
• Compare findings from different coding agents

Delegate code analysis and implementation to Codex CLI without an interactive session. The skill reads ordered output events, extracts the final agent response, and reports errors, with a read-only sandbox used by default.

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

• Review code in a read-only sandbox
• Delegate implementation to Codex
• Get a second coding agent's assessment

Delegate a clearly scoped repository analysis or implementation task to Pi without an interactive session. The skill limits the working directory and available tools, then checks structured output for errors before using the result.

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

• Delegate a read-only code diagnosis to Pi
• Assign Pi an explicitly authorized implementation task
• Check Pi's structured output for model or tool failures

Delegate scoped repository analysis or implementation to DeepSeek Harness without opening its interactive interface. Collect its final text, check the exit status, and inspect repository changes when the task requires read-only work.

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

• Diagnose a failing test without editing files
• Delegate a scoped repository investigation
• Request implementation in a specified project

Review changed code against project rules and report missing tests, unused code, typing problems, and style violations. It also checks API design and data isolation, helping developers identify issues after implementation.

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

• Reviewing changes after implementation
• Finding missing tests and unused code
• Checking Python types and API design

Coordinate a development task from planning through implementation and review. Choose whether to proceed after seeing the plan, then receive a report covering commits, verification results, review findings, and any work left unfinished.

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

• Plan, implement, and review a feature
• Review a plan before authorizing implementation
• Start implementation from an existing plan

Create and maintain OpenAPI 3.1 specifications from existing code or initial designs. Use these API descriptions to prepare documentation, generate client SDKs—libraries for calling an API—and check whether implementations match their specifications.

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

• Create API documentation from existing code
• Define an API specification before implementation
• Generate client SDKs from API specifications

Create and maintain project documents in conductor/ covering the product, technology stack, development workflow, and work units. Extract context from existing code, check document consistency before implementation, and update documentation as the project evolves.

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

• Set up context documents for a new project
• Document an existing codebase for onboarding
• Check project documents before implementation

Organize feature development across multiple agents by dividing work, assigning one owner per file, and agreeing on interfaces before implementation. Provides strategies for shared files, branches, and integration so agents can build separate parts of the same system.

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

• Dividing a large feature among multiple agents
• Assigning file ownership to avoid conflicting edits
• Agreeing on APIs before parallel implementation

Clarifies missing product or implementation decisions through one focused question at a time. It records answers and produces a short brief or specification once enough is known, while investigating facts that can be found directly.

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

• Clarifying an incomplete product request
• Choosing an implementation approach
• Turning interview answers into a brief specification

Plan Codewhale changes by locating the existing implementation and its callers, defining one reviewable change, and choosing verification before editing. Use it for features, upgrades, and refactoring to avoid duplicate implementations and unfinished migrations.

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

• Locate existing code before adding a feature
• Define a reviewable scope for refactoring
• Choose checks before implementation

Compare project documentation with existing code to identify missing core features. Rank the gaps and create GitHub issues with practical specifications, implementation plans, acceptance criteria, effort estimates, and dependencies.

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

• Find documented features missing from the implementation
• Prioritize gaps in core product functionality
• Turn feature gaps into actionable GitHub issues

Create Markdown documents for time-limited technical investigations before implementation. Define the decision to resolve, research tasks, success criteria, and deadlines, then record evidence, recommendations, and follow-up actions in a consistent structure.

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

• Investigating API capabilities before integration
• Comparing architecture options before implementation
• Planning experiments to check performance assumptions

Compare specification requirements with the codebase and create GitHub issues for unmet requirements. Check existing issues for duplicates, then include requirement IDs, implementation guidance, context, and acceptance criteria in each new issue.

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

• Finding requirements missing from an implementation
• Turning unmet requirements into GitHub issues
• Checking for duplicate issues before creating tasks

Map the code relevant to a task before implementation. Identify files to change, direct dependencies, related tests, and existing patterns, then organize the findings and potential risks into a structured document for review.

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

• Identifying affected files before a code change
• Finding related tests and dependencies
• Locating existing implementation patterns

Map an existing codebase into seven documents covering its technology, structure, architecture, conventions, integrations, tests, and concerns. Link findings to file evidence, mark unknowns, and highlight differences between stated plans and the actual implementation.

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

• Get oriented in an unfamiliar codebase
• Prepare documentation for a project handover
• Compare documented architecture with implementation

Coordinate a small AI development team with planning, implementation, and optional independent testing roles. Adapt the process to the work’s complexity, prepare pull requests, and preserve decisions and next steps so later sessions can continue.

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

• Starting development or taking over an existing project
• Coordinating implementation and independent testing
• Comparing perspectives on product or architecture decisions

Analyze a codebase to document its technologies, architecture, dependencies, and implementation patterns. Produce a Markdown reference with optional diagrams, code examples, and guidance for adding features consistently with the existing design.

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

• Understand an unfamiliar codebase's architecture
• Document components, dependencies, and data flow
• Create guidance for adding features consistently

Turns vague development requests into reviewed plans through planning, architecture, and quality-review agents. It compares alternatives, defines testable acceptance criteria, and records decisions, stopping before implementation unless execution has been explicitly approved.

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

• Defining the scope of a vague development request
• Comparing implementation approaches before coding
• Planning migrations or security-sensitive changes

Send questions, review requests, or implementation tasks to a supported local AI command-line tool through one shared command. The wrapper handles provider-specific options and saves the result as a Markdown file for later reference.

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

• Requesting a security review of a patch
• Seeking UX suggestions for a user flow
• Drafting an implementation plan for an issue

Develop an implementation plan through sequential Planner, Architect, and Critic reviews. Compare options, document risks and acceptance checks, and preserve the plan and review records for a later handoff to `$ultragoal`.

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

• Compare approaches before implementation
• Plan testing and failure scenarios for high-risk changes
• Review a plan without starting implementation