'implementation' 검색 결과

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

Execute an implementation plan in one session by assigning a fresh subagent, a separate task-focused agent, to each task. Check specification compliance first, then code quality, and repeat fixes and reviews before proceeding.

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

• Execute an existing plan with mostly independent tasks
• Check specification compliance before reviewing code quality
• Repeat fixes and reviews for each implementation task

Use LitGPT to explore language model implementations and train models on custom data. Covers pretrained model loading, LoRA fine-tuning that updates a small set of parameters, pretraining, and preparing trained models for deployment.

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

• Studying language model architecture through readable code
• Fine-tuning a model on custom instruction data
• Configuring LoRA training for a single GPU

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

Apply Apache ShardingSphere’s written coding standards during implementation or review, covering naming, Java constructs, tests, and Maven dependencies. Also audit a specified scope without editing files, combining automated checks with manual inspection of applicable rules.

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

• Check changed code against written repository standards
• Review Java naming and declaration conventions
• Verify changed Maven dependency declarations

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

Draft and refine Linear or Superset tickets using a consistent structure for context, references, and implementation notes. Clarify the desired outcome, record where requests came from, and add code details when enough context is available.

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

• Draft a bug report or feature request
• Standardize ticket structure across a team
• Record feedback sources and links

Use LitGPT to explore language model implementations and train models on custom data. Covers pretrained model loading, LoRA fine-tuning that updates a small set of parameters, pretraining, and preparing trained models for deployment.

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

• Studying language model architecture through readable code
• Fine-tuning a model on custom instruction data
• Configuring LoRA training for a single GPU

Checks cryptographic code against known attacks and edge cases using Project Wycheproof test vectors, predefined inputs and expected results. Helps load cases, interpret failures, compare implementations, and integrate checks into automated testing.

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

• Testing cryptographic code against known attacks
• Comparing results across cryptographic libraries
• Investigating rejected or incorrectly accepted signatures

Review token contracts and the protocols that accept them for ERC20/ERC721 compliance, privileged controls, and unusual transfer behavior. Produces evidence-based risk assessments and prioritized fixes, with supply and holder analysis when deployed contract details are provided.

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

• Checking ERC20/ERC721 implementations against their standards
• Reviewing support for tokens with unusual transfer behavior
• Assessing administrator powers and upgrade risks

Compare implementation code with a specification, whitepaper, or design document. It checks individual requirements, independently challenges reported mismatches, and writes evidence-based reports covering missing or partial implementation, contradictions, undocumented behavior, and requirements that cannot be judged.

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

• Check an implementation against a specification
• Compare protocol code with a whitepaper
• Verify guarantees stated in a README

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

Compare a Linear issue and its acceptance criteria with implementation evidence. Identify gaps, retain links to tests and pull requests, and update progress only when the relevant implementation, review, or deployment milestone is supported.

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

• Comparing acceptance criteria with implementation evidence
• Checking gaps before updating a Linear issue
• Adding links to pull requests, tests, and releases

Fetch design structure, screenshots, variables, and assets from Figma through MCP, a connection between the agent and Figma. Use these references to guide code implementation within an existing project and troubleshoot connection setup.

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

• Inspecting a specific Figma frame or layer
• Fetching images and SVG assets for implementation
• Adapting a design to existing project components

Coordinate feature development from product direction through architecture, planning, validation, and implementation. Run the whole workflow or start at a selected stage, with saved decisions, review checkpoints, and a final pull request.

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

• Take a feature idea through planning and implementation
• Review architecture before writing an implementation plan
• Validate an existing plan before execution

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

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.

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

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.

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

Authentication & Authorization Implementation Patterns workflow skill. Use this skill when the user needs Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Authentication & Authorization Implementation Patterns workflow skill. Use this skill when the user needs Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

Study a merged or shipped tdmcp implementation and extract reusable learnings: code improvements, runtime/UX lessons, test gaps, docs updates, roadmap items, and harness changes. Use when the user asks to learn from a completed feature/project/PR/build, analyze what can be improved from an implementation, or turn a real installation experience into actionable tdmcp improvements. This is a post-implementation learning harness; it does not replace tdmcp-pipeline for building or tdmcp-quality-audit for broad repo audits.

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