'implement' 검색 결과

Evaluate a proposed software change before implementation. It examines project files and official sources, compares options and trade-offs, and builds a concrete plan covering affected systems, effort, risks, and unresolved questions for the user's approval.

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

• Discuss a major change before implementation
• Compare migration or configuration options
• Estimate affected files and implementation effort

Convert a Notion specification into a linked implementation plan and manageable tasks. Extract requirements and acceptance criteria, record uncertainties, and keep task statuses, checklists, blockers, and milestone updates aligned as the work progresses.

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

• Turn a Notion feature specification into a plan
• Break implementation work into one- or two-day tasks
• Link specifications, plans, and task pages

Create the OpenSpec documents needed to begin implementing a feature or fix. Follow the workflow's dependency order and templates, using completed documents as context until all prerequisites for implementation are ready.

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

• Prepare implementation documents for a new feature
• Turn a fix description into the required documents
• Generate related documents in dependency order

Implement a planned game development task by gathering its specifications and design decisions, then assigning the right programming specialist. Coordinate source changes, tests where required, visual evidence, and session state for subsequent review and closure.

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

• Implementing a ready game development story
• Assigning implementation to the right programming specialist
• Collecting required tests and visual evidence

Implement, fix, refactor, or remove repository code through a defined workflow. It connects each change to an acceptance criterion, checks effects on existing behavior, and guides focused testing, change review, and verification.

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

• Implementing a feature within an agreed scope
• Fixing bugs while preserving existing behavior
• Checking impacts before removing code

Implement Verdaccio fixes, features, or refactoring after checking whether existing settings or plugins already solve the problem. Place changes in the responsible component, reuse helpers, add tests and release notes, and validate affected packages.

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

• Implementing a bug fix with a regression test
• Checking existing settings before adding a feature
• Refactoring code within a defined change

Convert a Notion specification into a linked implementation plan and manageable tasks. Extract requirements and acceptance criteria, record uncertainties, and keep task statuses, checklists, blockers, and milestone updates aligned as the work progresses.

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

• Turn a Notion feature specification into a plan
• Break implementation work into one- or two-day tasks
• Link specifications, plans, and task pages

Build web application features across the interface, API, and database, with authentication, input checks, and safe data handling. The skill guides technical design, implementation, error handling, and component testing in one workflow.

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

• Building data entry and editing forms with matching APIs
• Adding authenticated profile pages
• Designing data flows from database to interface

Generates cryptographic test vectors, inputs with expected outcomes, by deliberately changing implementation code and finding changes existing tests miss. Verifies new vectors across independent implementations and compares detection rates before and after adding them.

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

• Finding coverage gaps in cryptographic test vectors
• Creating invalid inputs that exercise validation checks
• Building test vectors shared across independent implementations

Turn Notion product requirements and feature specifications into linked implementation plans and manageable tasks. Extract requirements, flag ambiguities, and keep task status, milestones, blockers, and decisions aligned as work progresses.

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

• Turn a feature specification into an implementation plan
• Break requirements into one- to two-day tasks
• Link specifications, plans, and task pages in Notion

Guide code changes in iPolloWork by reusing existing implementations, limiting new files and dependencies, and keeping responsibilities clear. Review runtime costs, run focused checks, and audit the final changes for duplication and maintainability issues.

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

• Checking for reusable code before implementing a feature
• Removing duplicate implementations during refactoring
• Reviewing the need for new files and dependencies

Turn a Figma design into code that fits an existing project. Reuse its components and shared style values, follow designer notes and component mappings, and adapt Figma's reference output to the project's framework and conventions.

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

• Implementing a screen from a Figma design
• Reusing existing project components in a design implementation
• Applying designer notes and shared style values

Create the OpenSpec documents needed to begin implementing a feature or fix. Follow the workflow's dependency order and templates, using completed documents as context until all prerequisites for implementation are ready.

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

• Prepare implementation documents for a new feature
• Turn a fix description into the required documents
• Generate related documents in dependency order

Run a research task through five ordered stages: brainstorming, planning, implementation, review, and documentation. The workflow checks that brainstorming and planning files exist before proceeding, then reviews and documents what the implementation stage produced.

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

• Taking a research task from initial ideas to documentation
• Planning and implementing an estimation problem
• Working through a methodological improvement

Carry a research task from brainstorming and planning through code implementation, review, and documentation. Multiple agents handle independent implementation tasks in parallel, then report the resulting files, changes, and findings.

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

• Take a research task from initial ideas through implementation
• Split independent implementation tasks among multiple agents
• Run review and knowledge documentation after implementation

Build causal inference analyses to estimate intervention effects using templates drawn from Causal Inference: The Mixtape. Adapt code across Python, R, and Stata, with checks for method assumptions and guidance on language-specific packages and limitations.

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

• Implement a difference-in-differences analysis
• Set up an event study and check parallel trends
• Build instrumental variable or discontinuity models

Implement core TypeScript modules for claude-flow v3 using domain-driven design, which organizes code around distinct responsibilities. Build task and session domains, connect storage and services, and add unit and integration tests.

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

• Build the core structure for claude-flow v3
• Implement task assignment and status rules
• Connect SQLite storage through dependency injection

Turn a feature request into a minimal implementation plan before coding. Identify which files need changes, explain why, define the smallest required interface, and flag broader effects or expanded permissions for the implementer.

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

• Plan a feature before coding
• Identify files affected by a change
• Review scope and permission changes

AI DevKit · Implementation phase guidance for executing feature plans and checking implementation against design. Use when the user wants to implement planned tasks, update implementation docs, verify code matches design, or run dev-lifecycle phases 5 and 7.

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

Load code-style and task-specific skills, make the change described by the current context, then run post-implementation QA. Use for ad-hoc changes when no plan file or improvements backlog governs the work, and when the user asks to "just implement", "implement directly", "implement without a plan", or "apply the change".

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

Break a trusted implementation plan (or other provided context) into independently-grabbable, atomic work items, written to a single work-items.md file. Use when the user wants to convert a plan into work items, create implementation tickets or tasks, divide a plan into work units, or break the plan down into grabbable pieces. Do not use when there is no implementation plan yet or the plan is not yet trusted — use plan-implementation to produce the plan or iterative-plan-review to harden it first. Does not sequence work into demoable delivery phases — use plan-a-phased-build for that. Does not write code — use tdd to implement a work item.

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

Implement a single Flutter task following this repository's Riverpod, Freezed, AutoRoute, DTO/entity, codegen, and verification conventions. Reads the task definition, PRD, and tech spec, then executes the implementation. When invoked standalone, verifies the change; when invoked by implement-tasks-sequence, writes code only and leaves verification to start-job/build-verify. Use when the user says "implement task X", "work on task X", or wants to execute a specific task from the task list.

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

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to cursor-implementation-loop, this plugin's kernel skill, with verification and honest reporting. Use to fix, build, or own an outcome end to end; investigate-and-fix; "make X work"; or plan-then-execute in one request. A request with an approved plan or equivalently precise spec that needs nothing beyond implementation belongs directly to cursor-implementation-loop. Requires this plugin's cursor-implementation-loop skill; they ship together.

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

Delegate implementation to Codex or to a sandboxed Claude Code (`claude -p`), have a model from the other vendor review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex or a sandboxed Claude to write code, mentions handing off / delegating implementation to one of those backends, asks for a cross-vendor review of delegated code, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.

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