'implement' 검색 결과

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

Turn an accepted feature proposal into an implementation specification grounded in existing code. Define scope, explain design decisions, track unresolved questions, and document migration steps and tests, with implementation tasks added when the work is approved for building.

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

• Turn an accepted proposal into an implementation specification
• Record design choices and unresolved questions
• Plan migration stages and test coverage

Execute implementation within EPICs following test-first development, continuous SoT updates, and code traceability during PRD v0.7 Build Execution. Triggers on requests to start building, implement an epic, begin coding, or when user asks "start building", "implement epic", "coding", "development", "build execution", "implementation", "write code". Consumes EPIC- (context), TEST- (acceptance criteria). Updates existing IDs and creates code. Outputs working code with @implements traceability tags.

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

Execute a Carmack Council plan task by task. Use when explicitly asked to implement a plan, do a "council implement", "carmack implement", "council build", or invoke /council-implement. Reads the output of /council-plan and builds each task sequentially, loading the relevant expert's reference document per task. Verifies after each task. Produces an implementation log for /council-review. Stack: Next.js App Router / React / TypeScript / tRPC / Prisma / Neon / Clerk.

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

Execute the tasks from an already-created feature plan in .unikit/code/plans/ — read the plan manifest (the PLAN.md file in the plan folder), work through the uncompleted tasks in order, write the code, mark progress, and resume across sessions. Supports selective runs by phase or by task numbers, and continuing from where the last session stopped. Use whenever a plan exists and the user wants to build it, e.g. "implement", "implement the plan", "start coding", "execute the plan", "run the plan", "do the next task", "implement phase 3", "implement tasks 2.1 and 2.3", "continue implementation", "continue where we left off", "keep going on the feature". To create the plan first, use the planning skill — this one carries an existing plan out.

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

Delegate implementation work to a dedicated implementer subagent, then review its diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants a separate model to write code, mentions handing off / delegating implementation, asks to work through a plan or spec unit-by-unit with a subagent 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 self-reports success, must not run the full test suite by default, must not touch git, and its report is a claim rather than evidence. Cursor port of implementation-loop. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the cursor-engineering-mode skill (it ships in this same plugin).

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

Use this skill when the implementation status column of a statement of applicability may not match reality, and the team asks "is our SoA accurate", "check the implemented column", "do we have evidence for every implemented control", "reconcile the SoA with our evidence", "pre-audit evidence check" or "the auditor found a control marked implemented with no records". Samples the records behind every control marked implemented, grades the evidence, proposes a corrected status for each row and writes a reconciliation table plus an evidence gap list with owners.

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

같은 세션에서 기존 구현 계획을 작업별로 실행합니다. 테스트의 실패와 성공, 진행 상황과 판단을 기록하고 마지막에 브랜치 전체를 검토합니다.

• 작성된 개발 계획 구현
• 별도 구현 에이전트 없이 작업 진행
• 진행 기록을 바탕으로 작업 재개

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

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

프로젝트의 프레임워크와 라이브러리 버전을 확인하고 공식 문서에 따라 구현합니다. 판단의 출처를 제시하고 사용이 권장되지 않는 API와 확인하지 못한 방법도 표시합니다.

• 사용 버전의 공식 문서로 구현 확인
• 출처가 있는 기본 코드 작성
• 사용 중단이 권고된 API 점검

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 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

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

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

Implement database action handlers for syncable entities in Twenty server internals. It covers create, update, and delete operations, with conversion from universal identifiers to database IDs before each action is executed.

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

• Implement create, update, and delete handlers for a new entity
• Convert universal relation identifiers into database IDs
• Check runner implementation before the integration step

Implement PR review actions already selected for fixes, run relevant checks, and create focused commits. Post progress and completion replies, resolve applicable threads, and update the action records and their Markdown summary.

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

• Implement review actions already approved for fixing
• Limit review fixes to selected action IDs or files
• Post completion replies and resolve review threads

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

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

Review personal data handling against GDPR requirements, covering processing records, legal grounds, individual rights, breach procedures, and international transfers. Produce findings by article and a prioritized improvement roadmap with responsibilities, estimated costs, and timelines.

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

• Preparing evidence for a regulatory audit
• Reviewing privacy requirements for a new system
• Assessing GDPR gaps during acquisition due diligence

Turns Figma screens and components into code that follows an existing project’s conventions. Uses design specifications, screenshots, and assets to guide implementation, reuse existing components, and check the finished interface against the design.

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

• Implement a button from a Figma design link
• Build a dashboard from Figma frames
• Adapt a design to existing project components

Adapt an AI agent’s approach to brainstorming, implementation, debugging, review, teaching, or release preparation. Defines how each mode should ask questions, prioritize work, and present results, with automatic mode selection and explicit switching examples.

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

• Explore several ideas before implementation
• Investigate a bug through hypotheses and checks
• Organize review findings by severity

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