'implementation' 검색 결과

Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.

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

• Checking whether a feature fulfills its requirements
• Comparing implementations of the same specification
• Auditing unit and end-to-end test coverage

Create an implementation plan grounded in code relationships and verified source files, with proposed changes, test scenarios, risks, and a structured handoff for an implementation agent. It can also revisit and strengthen an existing plan.

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

• Planning a new feature
• Assessing a shared API change before implementation
• Strengthening and rechecking an existing plan

Turn a feature idea into a detailed implementation plan through research, interviews, and reviews by Gemini and Codex. Produce self-contained work sections with dependencies and acceptance criteria, plus files for supported automated implementation workflows.

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

• Clarifying requirements before feature development
• Reviewing an implementation plan with multiple AI models
• Splitting development work into self-contained sections

Review an OpenSpec implementation against its specifications, tasks, and design decisions. The skill checks for missing work, uncovered scenarios, and inconsistencies, then produces a prioritized report with concrete recommendations and code references where available.

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

• Review an implementation before archiving
• Find incomplete tasks and missing requirement implementations
• Check whether scenarios have implementation and test coverage

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

Turn feature requests, refactoring work, package upgrades, or infrastructure changes into structured Markdown implementation plans. Each plan defines concrete tasks, dependencies, affected files, and validation criteria for execution by AI agents or people.

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

• Plan the implementation of a new feature
• Break refactoring work into concrete tasks
• Prepare a package upgrade plan

Turn a feature requirements document into a detailed Markdown implementation plan following Epoch’s monorepo structure. Cover frontend components, APIs, database design, security, performance, and deployment, with Mermaid diagrams showing system architecture and data relationships.

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

• Turning feature requirements into an implementation plan
• Mapping frontend, API, and service responsibilities
• Documenting database design and migrations

Carry agreed implementation work through a separate Git worktree, an isolated working directory. After checks and review, it prepares one local commit, a clean branch, and a pull request draft for handoff without publishing them.

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

• Starting agreed implementation in a separate worktree
• Preparing a reviewed local branch with one commit
• Taking over an existing pull request while preserving author credit

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

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.

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

Own goal-first engineering outcomes: investigate, find root cause, design, plan, then delegate implementation unit-by-unit to implementation-loop 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 implementation-loop. Requires implementation-loop and an authenticated backend CLI to execute.

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

모호한 기능 요청이나 영향이 큰 변경의 범위·전제·위험을 정리합니다. 기대 동작과 검증 방법을 명시한 인수 기준이나 인계 자료로 만듭니다.

• 모호한 기능 요청을 정리합니다
• 인증 변경과 데이터 이전 기준을 만듭니다
• 다른 에이전트나 팀에 구현을 인계합니다

Check project dependency versions and consult the relevant official documentation before writing framework-specific code. Produce implementations with source links, identify deprecated APIs, and flag unverified approaches or conflicts between documentation and existing project patterns.

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

• Verify an implementation against version-specific documentation
• Create starter code with documented patterns
• Review code for deprecated APIs

Create a phased implementation plan for a feature or complex development task. It investigates documentation and existing examples, identifies supported APIs, and records concrete tasks, references, and verification checks for each phase.

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

• Planning a feature before implementation
• Checking documented APIs before choosing an approach
• Splitting development work across separate chat sessions

Carry out a phased implementation plan with subagents assigned to implementation, verification, pattern checks, and code review. Each phase must pass verification before changes are committed and pushed, with context prepared for the next phase.

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

• Execute a plan created with make-plan
• Delegate implementation work by phase
• Verify changes and review code before committing

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

Implement pending tasks from an OpenSpec change using its specifications and design documents. The skill updates task checkboxes, confirms progress, supports resuming unfinished work, and pauses when requirements or implementation issues need clarification.

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

• Start implementing a planned OpenSpec change
• Resume partially completed implementation
• Track completed and remaining tasks

Compare an implementation with its OpenSpec specifications, tasks, and design decisions before archiving the change. Get a report on completion, requirement coverage, and consistency, with prioritized issues, actionable recommendations, and explicit limits where evidence is missing.

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

• Check for unfinished tasks before archiving a change
• Find gaps between specifications and implementation
• Review scenario tests and adherence to design decisions

Inspect Figma screens to gather details for implementation, including component variants, spacing, shared design settings, and image assets. It helps an agent understand layouts and design libraries before turning a design into code.

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

• Gathering implementation details from a Figma screen
• Checking component variants and spacing
• Extracting image assets for implementation

Manage coding work from issue intake through implementation, review, deployment, and acceptance checks. Track each completion requirement against fresh evidence, with defined retry limits and explicit escalation when progress needs human input.

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

• Taking a ready issue through implementation and verification
• Coordinating implementation, review, and deployment handoffs
• Checking runtime behavior against acceptance criteria

Turn Airflow Improvement Proposals into practical guides checked against current code, or proposed user stories for design review before implementation. Organize use cases, distinguish verified examples from speculative code, and capture specific design questions.

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

• Create implementation-backed guides for an Airflow proposal
• Explore user stories before a feature is implemented
• Separate implemented features from proposed functionality

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

Review source code for MCP, a protocol connecting AI applications to tools. Check authentication, input validation, unsafe execution, and other security risks, then report findings with file and line references and separate manual follow-ups.

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

• Reviewing an MCP server before release
• Checking authentication and validation on a network-exposed server
• Auditing tool code for unsafe execution paths

Turn implementation plan phases into GitHub Issues with structured titles, descriptions, and labels. Check existing issues first, then create or update one issue per phase using feature or chore templates where available.

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

• Turning implementation plan phases into GitHub Issues
• Updating existing issues to reflect a plan
• Structuring feature and chore work with issue templates