'spec' 검색 결과

Update main OpenSpec specifications from a change's delta specs, which describe specification changes. The skill merges requirement additions, edits, removals, and renames while preserving unrelated content, validates the results, and leaves the change active.

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

• Update specifications while keeping a change active
• Merge new scenarios into existing requirements
• Sync only selected specification files

Keeps CopilotKit documentation aligned with released Inspector panels, the views shown in its local web overlay. It updates reader guidance and panel mappings when panels change, and checks quickstart instructions against supported platforms.

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

• Add documentation guidance for a released Inspector panel
• Update documentation after renaming or removing a panel
• Check Inspector instructions in web quickstarts

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

Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.

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

Archive several OpenSpec changes together after reviewing their documents and task progress. The skill checks code to resolve overlapping specification updates, syncs the selected updates, and reports which changes were archived, skipped, or failed.

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

• Archive several completed changes together
• Resolve overlapping specification updates
• Review unfinished work before archiving

Finalize an implemented OpenSpec change by checking planning files, task completion, and specification differences. Review whether to merge specification updates, verify any requested merge, then archive the change and report its location and outstanding warnings.

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

• Archiving an implemented change
• Reviewing specification updates before archiving
• Checking unfinished work before closing a change

Learn the OpenSpec workflow by completing a small task in a real codebase. The skill explains each stage, creates planning documents, implements agreed tasks, and archives the change to preserve its decision history.

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

• Learn OpenSpec through a real code change
• Find a small improvement for a first practice task
• Understand the roles of proposals, specs, design, and tasks

Develop and debug CopilotKit Inspector interfaces in a dedicated local workbench. It guides baseline screenshots, visual checks after each change, and additional narrow-screen or theme checks when layout or contrast is involved.

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

• Fixing Inspector panes and overlay controls
• Checking narrow-screen layouts and the collapsed rail
• Comparing light and dark theme appearance

Learn the complete OpenSpec workflow through a small task in an actual codebase. The agent explains each stage while creating a proposal, specifications, design, and tasks, then implements the change and archives its records.

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

• Learning OpenSpec through a real code change
• Understanding proposals, specifications, designs, and tasks
• Practicing a complete change cycle with a small fix

Turn a feature idea or fix request into an OpenSpec implementation plan. The skill examines the project and prepares the required proposal, specification changes, design, and tasks for review, without changing project code.

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

• Plan a new feature before implementation
• Turn a fix request into concrete tasks
• Review specification changes and design together

Revise an existing OpenSpec change plan and reconcile related planning documents. Incorporate new decisions, identify contradictions or gaps, and apply proposed document edits after confirmation, while leaving implementation code untouched.

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

• Incorporating new decisions into an existing change plan
• Checking planning documents for contradictions
• Reconciling related documents after an edit

Update main specifications from delta specs, documents describing intended changes. Apply requirement additions, edits, removals, and renames while preserving unrelated content and keeping the change active for further implementation work.

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

• Reflect requirement changes in main specifications
• Add scenarios while preserving existing ones
• Create main specifications for a new capability

Define reusable OpenRig agent setups, roles, and workflows in specification files. Review dependencies that prevent use on another host, distinguish specifications from bundles and extensions, and verify both file structure and actual execution.

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

• Defining reusable agent roles and workflows
• Reviewing specifications for use on another host
• Testing specifications in a clean OpenRig environment

Set up KubeEye in KubeSphere to inspect Kubernetes clusters. Define checks for configurations, nodes, and services, schedule recurring or one-time inspections, and retrieve findings as HTML or spreadsheet reports.

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

• Install KubeEye for cluster inspections
• Create checks for node health and configuration
• Schedule recurring cluster inspections

Analyze signal spectra in MATLAB using nonparametric and parametric estimators. Use when computing frequency content, PSD, power spectrum, spectral peaks, bandwidth, or streaming spectral analysis. Covers pspectrum, pwelch, periodogram, pmtm, pburg, pmusic, rootmusic, plomb, poctave, spectrumAnalyzer, dsp.SpectrumEstimator. TRIGGER: FFT, PSD, power spectrum, spectral analysis, frequency content, bandwidth measurement, spectral leakage, window selection, streaming spectrum, periodicity, resolve close frequencies, multitaper. DO NOT TRIGGER: filter design, spectrogram/time-frequency, audio features.

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

Activate Specification Know-How: load the SpecBook format contract, the SpecBook schema configuration of the project, and the list of specification (SPEC) artifacts into the context, so the specification can be read, queried, explained, and edited ad-hoc in plain conversation. Use *automatically* whenever the user wants to work with the specification files -- asks what the "spec" or "specification" says, wants to "look up", "query", "check", or "explain" specification content, or wants a small ad-hoc change to it -- and no dedicated specification skill (`ase-spec-edit`, `ase-sync-import`, `ase-sync-reconcile`, `ase-sync-export`) is invoked, as those activate the know-how implicitly.

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

全機能の一括Spec化・一括更新。PM として並列サブエージェントにコード分析を委任し、 結果を統合して全機能の要件定義書を一括生成・更新する。 「全部のSpecを作って」「設計書を全部作って」「全機能をドキュメント化して」 「要件定義を全て更新して」「Specを全部更新して」などのリクエストで使用する。 個別のSpec化には spec-feature を使う。init-specは初期セットアップ専用。

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

Draft and revise OpenSpec user documentation using its house style. Organize task guides and reference pages so readers can quickly find answers, commands, file paths, and troubleshooting details, while identifying claims that remain unchecked.

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

• Drafting an OpenSpec task guide
• Reorganizing a command reference
• Revising documentation for easier scanning

Explore ideas, investigate problems, and clarify requirements in an OpenSpec project through discussion grounded in existing code and specifications. Compare approaches, sketch diagrams, and identify open questions, with planning documents saved only within an explicitly approved scope.

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

• Clarify the scope of a loosely defined feature idea
• Compare technical approaches using project evidence
• Revisit design choices when implementation gets stuck

Prepare the OpenSpec documents needed to start implementation in one pass. It examines the project and creates required proposals, specifications, designs, and tasks in dependency order, following the project's configured workflow.

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

• Prepare planning documents for a new feature
• Turn a change description into implementation tasks
• Create missing prerequisite documents together

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

Archive an OpenSpec change after checking its documents, task completion, and specification differences. The skill offers a choice about updating the main specifications, then moves the change into a dated archive and reports the result.

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

• Archive an implemented change
• Check unfinished documents and tasks before archiving
• Review specification differences before updating the main specifications

Start a new prospect's intake, with or without their files in hand — a request naming a new prospect and attaching no documents is a normal starting point, because Step 1 searches the connected tools or asks the advisor to upload. Cleans and normalizes their account files (statements, exports, screenshots) into a consolidated view, then hands back a plain-English prospect summary, a detailed analyst handoff the full proposal gets built from, and a friendly "what to expect" memo, offered as a Gmail draft on approval. Does not produce the proposal, recommend an allocation, or quote fees. Triggers on "prospect intake", "/prospect-intake", "new prospect intake", "clean up [prospect]'s statements", "process [prospect]'s files", "what to expect note for [prospect]" — and on how an advisor raises a new prospect before any file exists: "I met with a potential client/customer", "[name] is interested in becoming a client", "I have a new prospect", "how should I proceed with [name]".

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

Update a product spec from a meeting transcript — extract decisions, open questions, spec changes, and flowchart updates. Use this skill when: - A meeting discussed changes to a product spec and you need to update the local .md + wiki page - The user shares a meeting URL or transcript ID and says "update the spec" - The user says "what needs to change in the spec from this meeting" - After processing a meeting, when decisions affect a spec's content (not just action items) Trigger phrases: "update spec from meeting", "what changed in the spec", "meeting to spec", "sync meeting decisions to spec", "add meeting decisions to spec"

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