'specification' 검색 결과

Turn an OpenAPI or Swagger specification into an MCP server, a bridge that lets AI assistants call an API. Covers tool generation, authentication, local testing, and deployment to mcp-use cloud.

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

• Make an internal API callable from Claude
• Generate MCP tools from a Swagger specification
• Test API calls locally before cloud deployment

Route requests for idea exploration, rough planning, time-boxed technical investigation, phase specifications, or thought capture to the appropriate GSD skill. It selects and invokes a skill based on the intended task.

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

• Explore an idea or opportunity
• Sketch a rough design or plan
• Run a time-boxed technical investigation

Open documents, text configuration files, HTML, URLs, or folders in Plannotator for browser review. The agent responds to returned annotations and can use an approval session when you need to accept a plan, specification, or document.

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

• Adding document feedback in a browser
• Reviewing text configuration files or HTML
• Approving a generated plan or specification

Create a single-column HTML email for a product launch, with a centered brand wordmark, hero image block, headline, copy, action button, specifications, and footer. Table-based layout and inline colors support compatibility with email clients.

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

• Creating an email to announce a new product
• Combining product specifications and an action button
• Building a branded HTML newsletter

Execute an implementation plan by assigning each independent task to a fresh helper agent in sequence. Review specification compliance and code quality after each task, track decisions in files, and finish with a review of the entire branch.

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

• Execute a plan with separate implementation and review roles
• Check specification compliance and code quality after each task
• Resume work using a persistent progress ledger

Turn cryptographic code or specifications into sequence diagrams showing who sends each message, which cryptographic operations occur, and where failures stop the exchange. Outputs include Mermaid source, a plain text diagram, and a protocol summary.

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

• Visualizing handshake and key exchange steps
• Extracting message flows from RFCs and papers
• Diagramming ProVerif or Tamarin models

Create dictionaries of keywords and identifying byte sequences for fuzzing, or testing with generated inputs. Extract useful entries from code, binaries, or specifications, then configure fuzzers to explore parsing paths beyond initial input validation.

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

• Build a dictionary for JSON or XML parser fuzzing
• Add protocol keywords to generated test inputs
• Test image parsers with file signatures and chunk names

Inspect DWARF, the debug information stored with compiled code, to find functions and types, check structural integrity, and clarify specification details. Also helps write parsing tools using libraries such as pyelftools, libdwarf, or gimli.

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

• Finding functions and types in debug information
• Checking DWARF structural integrity
• Comparing debug-information quality metrics

Review smart contract projects against Trail of Bits development guidelines. Examines architecture, upgrade mechanisms, implementation, dependencies, and tests, then provides system documentation, identifies gaps, and recommends improvements in priority order with code references.

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

• Review smart contract architecture
• Check upgrade and proxy designs
• Identify gaps in specifications and documentation

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

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

Turn an agreed specification or ticket into a checklist with specific tests or commands for each requirement. Implement the work, run the checks, and have a separate agent verify the entire feature.

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

• Implement a feature from an agreed specification
• Extract verifiable requirements from a ticket
• Verify every requirement with a separate agent

Clean up DeepChat's specification-driven development documents after implementation and validation. Review feature, issue, and architecture files, remove completed or obsolete material when evidence supports deletion, and preserve maintained specifications while checking references.

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

• Remove issue documents after confirming a bug is resolved
• Clear old plans from completed feature work
• Update or remove architecture documents after replacement

Coauthor proposals, specifications, and other structured documents through context gathering, section-by-section drafting, and revision. Test the finished draft with a fresh Claude conversation to identify unclear assumptions, missing information, and contradictions.

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

• Turning background notes into a proposal
• Drafting a technical specification or PRD
• Documenting a decision and its rationale

Learn Ouroboros through a short, hands-on interview about your own project idea. Turn your answers into a sample specification with goals, constraints, and checkable outcomes, then learn the commands for execution, evaluation, and next steps.

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

• Trying Ouroboros for the first time
• Clarifying a vague project idea
• Learning how a Seed specification works

Execute an existing Ouroboros Seed, a specification containing a goal and acceptance criteria, as a background job. The workflow checks each criterion, normally queues formal evaluation, and follows a bounded improvement loop if evaluation rejects the result.

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

• Executing an existing Seed specification
• Checking whether each acceptance criterion is met
• Following execution, evaluation, and improvement results

Run repeated Ouroboros execution and improvement cycles as a background job, starting from a Seed specification or continuing an existing lineage. The loop stops on a quality check pass, convergence, cancellation, or the generation limit, and reports the outcome.

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

• Starting repeated improvement from a Seed specification
• Continuing an existing improvement lineage
• Following meaningful background progress

Extract structured product records from Amazon URLs across regional sites, including price, stock, specifications, rating breakdowns, sellers, and visible variants. Use the records for competitor research, catalog audits, or tracking product prices and availability.

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

• Collect product specifications for competitor research
• Prepare records for a brand catalog audit
• Check prices and stock for selected products

Extract details from an open eBay listing into JSON, a structured data format. Collect prices, availability, sales counts, seller feedback, specifications, and image links for product comparisons and catalog checks across regional eBay sites.

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

• Comparing prices and availability across eBay listings
• Checking seller feedback and item locations
• Collecting product identifiers and specifications

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

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

Co-write proposals, technical specifications, and decision documents through context gathering, section-by-section drafting, and revision. A fresh AI reader then tests the document to reveal unclear explanations, missing context, and contradictions before it is shared.

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

• Drafting a proposal through discussion
• Organizing the structure of a technical specification
• Writing a document that explains a decision

Write feature specifications as requirements and user stories with acceptance criteria, focusing on business value and testable conditions.

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

Convert requirements into structured technical specifications with architecture decisions

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