'spec' 검색 결과

Monitor local network traffic for ARP spoofing, where false address mappings can redirect traffic. Use ARPWatch, Wireshark, switch inspection settings, and Python monitoring to flag address changes, duplicate IP claims, gateway impersonation, and unusual ARP volumes.

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

• Investigating suspected interception on a local network
• Monitoring changes in IP-to-MAC address mappings
• Checking duplicate IP claims and gateway impersonation

Draft prospect emails and follow-up sequences using the sender’s established writing style and specific facts about each recipient. Present messages for approval, prepare approved sends when connected, and record contact history in HubSpot or a file.

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

• Draft a cold email in the sender’s own style
• Prepare outreach to a referred prospect
• Write follow-ups after a customer meeting

Build targeted company and contact lists with Common Room's Prospector. Refine criteria through conversation, distinguish new companies from existing accounts, and prioritize existing accounts using available activity signals and scores.

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

• Build a new target company list by industry, size, and location
• Prioritize existing accounts using activity signals
• Find companies with attributes similar to a reference company

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

Helps build custom code exporters from json-render UI specifications. Covers walking the UI tree, collecting components, state references, and actions, and formatting property values for JSX, the markup syntax used in React.

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

• Build a custom exporter for Next.js or Remix
• List components and actions used in a UI specification
• Convert property values into JSX attributes

Clarify what a development phase should deliver before discussing implementation. Through structured questions and ambiguity scores, the skill produces SPEC.md with testable requirements, explicit scope boundaries, and acceptance criteria for judging completion.

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

• Clarifying phase requirements before discussing implementation
• Defining scope boundaries and acceptance criteria
• Drafting a specification with recommended defaults

Design an OpenRig agent team around a project goal. Create team and agent specifications, role guidance, and collaboration rules, then validate the setup and diagnose problems with startup instructions or agent coordination.

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

• Designing an implementation and QA pair
• Creating a team with development and independent review
• Writing role guidance and team collaboration rules

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

Query ProteomeXchange through its PROXI API to inspect datasets, libraries, proteins, peptide forms, and spectra. Receive concise summaries focused on a dataset or identifier, and save complete responses when more detail is needed.

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

• Inspect a dataset by its identifier
• Check proteins, peptide forms, and spectrum matches
• Retrieve spectra and USI identifier examples

Plan and implement features with a workflow that adapts to their complexity. It connects testable requirements to tasks, tests, and small commits, then checks the finished work against the specification through an independent verification pass.

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

• Define testable requirements for a new feature
• Implement a large feature through small, verified tasks
• Check whether an implementation meets its specification

Develop and fix Nexent features by connecting written specifications, acceptance criteria, implementation, and verification evidence. Plan unit tests and appropriate staged checks, maintain their links to requirements, and fill confirmed test gaps after development.

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

• Planning and implementing features from acceptance criteria
• Fixing bugs using existing specifications and tests
• Refactoring while preserving required behavior

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

Create a structured specification in plain language from a feature description and multi-AI research. Define actors, behaviors, constraints, dependencies, and acceptance conditions, while checking completeness and keeping unresolved user decisions visible for later review.

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

• Write a specification for a new feature
• Define authentication behaviors and edge cases
• Document performance and security constraints

Set up and inspect periodic prompts that continue a specific Codex thread after idle checks pass. It supports App-native automation and a headless fallback, with controls to inspect status and enable or disable scheduled prompts.

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

• Periodically continuing an idle Codex thread
• Keeping automated prompts visible in Codex App
• Inspecting thread and automation status

Guides general use of AWS messaging and streaming services. Covers Amazon SQS, Amazon SNS, Amazon EventBridge, Amazon MQ, Amazon Kinesis Data Streams, Amazon Data Firehose, Amazon Managed Service for Apache Flink, and Amazon Managed Streaming for Apache Kafka (MSK). Use when reasoning about messaging and streaming patterns. Also identifies which AWS service owns each customer communication channel: email (Amazon SES), and WhatsApp, SMS, MMS, RCS, voice and mobile push (the AWS End User Messaging family of services). Routes the request to the specialized skill for that channel. Defers to the channel's specialized skill when the user already named a specific channel. In general, use specific skills or documentation searches for detailed service-specific questions. Do NOT use for MSK or Managed Service for Apache Flink questions, prefer specific skills. Does not configure customer communication channels; defers to specific skills.

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

Use when SLCI code inspection has failed due to compatibility issues and you need to diagnose the incompatibilities. Traces inspection failures back to root-cause incompatibility settings or known limitations by matching failed code lines against known incorrect code generation patterns and documented limitation scenarios. Hands off to slci-compatibility-analysis for fixes. Trigger keywords: inspect, inspection failed, trace inspection errors, why did inspection fail, SLCI verification failures, limitation.

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

Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.

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

Orchestrates Spec Driven Development by coordinating spec, plan, and task skills. Use when running the full speckit workflow from spec to implementation.

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

Check behavioral consistency between high-level hardware specifications and RTL implementations. Use when asked to check RTL consistency, verify RTL against spec, check hardware specification compliance, validate RTL implementation, find spec violations in RTL, check behavioral consistency, or when working with hardware designs that need verification against protocol specifications, timing requirements, or functional specifications in Verilog, VHDL, or SystemVerilog.

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

Keeps specification documents and code in agreement. Audit mode finds every divergence when an implementation is claimed complete; sync mode detects spec drift in staged changes and updates the spec after user approval, so each commit is a reconciled snapshot of spec, tests, and code. Use when an implementation is claimed complete against a spec, before committing changes that may drift from the spec, or after approving decisions that must flow back into it.

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

When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," or "qualified leads." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.

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

Condense any input — an idea, brief, PRD, transcript, or mixed notes — into a short spec: one kernel file plus supporting files that downstream skills build from. Also updates and validates existing specs. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec"

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

Use as the follow-up to brainstorm-beagle when a spec has an Open Questions section (or quietly carries latent gaps) that need closing before planning or implementation can begin. Triggers on: "resolve the open questions", "close the gaps in this spec", "research the open items", "finalize my spec", "make this spec implementation-ready", "answer the TBDs". Also triggers whenever the user points at a brainstorm-beagle spec and asks for research, proposals, or answers to unresolved items. Orchestrates parallel research subagents when available (falls back to inline sequential research otherwise), proposes answers one at a time for user approval, then rewrites the spec in place so it arrives at planning with no known gaps. Does NOT write code, design implementation, or create plans — it only produces a complete spec.

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

Use when you have a finalized brainstorm-beagle spec at `.beagle/concepts/<slug>/spec.md` and need a bite-sized, TDD-driven implementation plan before any code is written. Triggers on: "write a plan", "plan this spec", "turn the spec into a plan", "now plan the implementation", "write-plan". Reads the spec, designs the file structure, decomposes work into 2-5 minute TDD steps with exact paths and commands, self-reviews against the spec, gets user approval, then writes to `.beagle/concepts/<slug>/plan.md` and offers to generate an execution handoff prompt via the subagent-prompt skill. Does NOT brainstorm specs, write code, or execute the plan — produces the plan document (and an optional handoff prompt) only.

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