'implementation' 검색 결과

Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

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

15-agent hierarchical mesh coordination for v3 implementation. Orchestrates parallel execution across security, core, and integration domains following 10 ADRs with 14-week timeline.

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

Complete security architecture overhaul for claude-flow v3. Addresses critical CVEs (CVE-1, CVE-2, CVE-3) and implements secure-by-default patterns. Use for security-first v3 implementation.

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

Deep agentic-flow@alpha integration implementing ADR-001. Eliminates 10,000+ duplicate lines by building claude-flow as specialized extension rather than parallel implementation.

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

Deliver a small bounded change inside an initialized SDD Composy workspace through the quick path: at most five implementation files, a registered TASK, TDD, evidence, trace, and a verified verdict, escalating otherwise. Use for a precise objective with no existing task — 'ajuste rápido via SDD', 'quick fix under SDD', 'small change to X in the SDD flow'. Do NOT use for an already registered task (sdd-execute), for architecture, migrations, or destructive work, or in repositories without SDD Composy (other plugins' quick).

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

Use when starting feature work that needs isolation from the current workspace, or before executing an implementation plan

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

Use when the user wants a new Product Requirements Document — 'criar um PRD', 'escrever os requisitos de', 'new PRD for', 'documento de requisitos' — through a 12-step interview, one question at a time, ending with an approval gate. Do NOT use to change an existing PRD (prd- refine) or to plan implementation.

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

Execute approved PWDEV Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence. Use after the plan gate is approved or for approved Flow correction tasks.

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

Use when implementing any feature or fixing any bug, before writing implementation code

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

Use when implementation is complete, tests pass, and the work needs integrating - merging, opening a pull request, or being left in place

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

Deliver a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

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

Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation

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

Systematically review pull requests, feature implementations, and code changes to ensure quality, maintainability, security, and adherence to best practices. Use when reviewing code before merging, conducting peer reviews, performing self-reviews, auditing code quality, checking for security vulnerabilities, ensuring consistent coding standards, verifying test coverage, assessing performance implications, evaluating architectural decisions, or providing constructive feedback to improve team code quality.

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

Facilitate ideation, explore alternatives, and refine concepts through structured brainstorming techniques before implementation. Use when starting new projects, designing features, exploring solutions, evaluating tradeoffs, challenging assumptions, generating creative ideas, planning architecture, or refining rough concepts into detailed designs.

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

When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," or "how long should I run this test." Use this whenever someone is comparing two approaches and wants to measure which performs better. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

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

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.

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

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema-markup.

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

Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use /plan-design-review. Use when asked to "audit the design", "visual QA", "check if it looks good", or "design polish". Proactively suggest when the user mentions visual inconsistencies or wants to polish the look of a live site. (gstack)

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

Designer's eye plan review — interactive, like CEO and Eng review. Rates each design dimension 0-10, explains what would make it a 10, then fixes the plan to get there. Works in plan mode. For live site visual audits, use /design-review. Use when asked to "review the design plan" or "design critique". Proactively suggest when the user has a plan with UI/UX components that should be reviewed before implementation. (gstack)

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

Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".

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

Orchestrate complete lifecycle work for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEM as a Cloud Service, from design and implementation through validation, release readiness, and incident troubleshooting.

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

Implement custom AEM Workflow Java components on AEM as a Cloud Service. Use when writing WorkflowProcess steps, ParticipantStepChooser implementations, registering services via OSGi DS R6 annotations, reading step arguments from MetaDataMap, accessing JCR payload via WorkflowSession adapter, reading and writing workflow metadata and variables, and handling errors with WorkflowException for retry behavior.

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

Generate comprehensive technical documentation for developers taking over an AEM Edge Delivery Services project. Analyzes codebase structure, custom implementations, design tokens, and produces a complete developer guide.

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

Guide for implementing code changes in AEM Edge Delivery Services. Handles block development (new or modified), core functionality changes (scripts.js, styles, delayed.js, etc.), or both. Use this skill for all implementation work guided by the content-driven-development workflow.

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