Results for “specification”

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.

The English summary is being prepared. Showing the original description.

Create and maintain OpenAPI 3.1 specifications from existing code or initial designs. Use these API descriptions to prepare documentation, generate client SDKs—libraries for calling an API—and check whether implementations match their specifications.

• Create API documentation from existing code
• Define an API specification before implementation
• Generate client SDKs from API specifications

Turn a specification file into a GitHub feature request issue. The skill extracts requirements, checks existing issues, and creates or updates one issue covering the specification, using a template to organize the problem, solution, and context.

• Turn a specification into a feature request issue
• Check existing issues before registering a request
• Update an existing issue with specification requirements

Draft a patent specification from claims and invention disclosure materials. The skill prepares sections from background to detailed embodiments and abstract, then checks whether the description supports each element of the claims.

• Drafting a patent specification from existing claims
• Checking written support for every claim element
• Preparing drafts for CN, US, or EP requirements

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

Retrieve translated patent description (specification) text from Nexscope. Triggered when users request patent specification translation, patent full text in other languages, translated patent full text, or want to view patent specifications in Chinese, English, or Japanese, patent specification translation, patent description translation, Nexscope, or patent translation. Also triggered when users provide a patent ID or publication number and request specification/description content in another language, or mention "patent specification translation," "description translation," "translated full text," or similar intent.

The English summary is being prepared. Showing the original description.

要件定義と実装の間を埋める技術仕様書を体系的に作成するスキル。 画面設計、API設計、DB設計、シーケンス図、状態遷移図をMermaid形式で生成し、 IEEE 830/ISO 29148準拠の仕様書を出力する。Use when creating functional specifications, API design documents, database design documents, screen design specifications, or sequence/state diagrams from requirements. Triggers: "technical specification", "functional spec", "API design", "database design", "screen design", "画面設計書", "API設計書", "DB設計書", "技術仕様書", "シーケンス図", "状態遷移図"

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Explain why counterexamples violate specifications by analyzing formal specifications (temporal logic, invariants, pre/postconditions, code contracts), informal requirements (user stories, acceptance criteria), test specifications (assertions, property-based tests), and providing step-by-step traces showing state changes, comparing expected vs actual behavior, identifying root causes, and assessing violation impact. Use when debugging test failures, understanding model checker output, explaining runtime assertion violations, analyzing static analysis warnings, or teaching specification concepts. Produces structured markdown explanations with traces, comparisons, state diagrams, and cause chains. Triggers when users ask why something failed, explain a violation, understand a counterexample, debug a specification, or analyze why a test fails.

The English summary is being prepared. Showing the original description.

Retrieve patent description (specification) data from the Nexscope patent database by patent ID or publication number. Triggered when users mention patent specification, patent full text, patent technical description, patent embodiment details, Nexscope specification data, patent specification, patent full text, technical description, embodiment details, Nexscope, or patent detailed description. Even if the user does not explicitly say "Nexscope," this skill should be triggered whenever they need to view the complete specification/description content of one or more patents.

The English summary is being prepared. Showing the original description.

Turn a feature idea into a structured specification before coding. Review requirements, system connections, constraints, and failure scenarios, define testable acceptance criteria, and save the specification in memory for later development phases.

• Defining requirements before building a new feature
• Writing testable acceptance criteria
• Documenting constraints and failure scenarios

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

Turn a product's visual and interaction goals into DESIGN.md and EXPERIENCE.md. Through guided discussion, capture appearance, screen structure, behavior, accessibility, and user journeys as specifications that can guide later design and development work.

• Define a product's appearance and interaction behavior
• Document screen structure and user journeys
• Update UX specifications after design changes

Assess Airflow Improvement Proposals by comparing Confluence specifications with pull requests, commits, and codebase files. Produce evidence-backed progress reports showing delivered items, remaining work, and specification updates needed across one or more proposals.

• Check implementation progress for an Airflow proposal
• Compare specification deliverables with shipped code
• Compile a progress report across multiple proposals

Create or repair a JSON specification for an editable PowerPoint deck. Define exact object positions, sizes, styles, and layering, alongside reading order and image descriptions, so the build process follows an explicitly authored layout.

• Specifying exact positions for PowerPoint slide objects
• Repairing margins, gaps, and overlaps in a slide specification
• Keeping labels and values editable as native objects

Create structured Markdown specifications that AI agents can read and use. Organize requirements, constraints, interfaces, acceptance criteria, and testing plans into a self-contained document with clear definitions and examples.

• Writing specifications for AI-assisted implementation
• Defining requirements and acceptance criteria
• Documenting APIs and data contracts

Turn an existing GitHub Actions workflow into a structured specification for maintenance and AI reference. Document its purpose, triggers, job dependencies, inputs, outputs, permissions, and failure handling, focusing on expected behavior rather than implementation details.

• Documenting an existing GitHub Actions workflow
• Reviewing job order and dependencies
• Organizing permissions and failure handling

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

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

Review skill and agent definitions for structural issues and whether their instructions meet expected behavior. Four modes cover structure, test specifications, category criteria, and coverage reports that reveal missing specifications or checks.

• Check one skill or all skills for structural issues
• Compare skill or agent instructions with a test specification
• Review definitions against category criteria

Turn an unclear idea into a specification with testable completion criteria. The skill supports discovery interviews, drafts from existing code, completeness checks, and records of decisions and verification in a shared project document.

• Clarifying an idea through questions
• Defining testable project completion criteria
• Drafting a specification from existing code

Design consistent API specifications with OpenAPI 3.0 and 3.1. Define requests, responses, authentication, and reusable data structures, then guide specification checks, documentation, and generation of client libraries or starter server code.

• Define an API contract before implementation
• Standardize authentication and error responses
• Check API specifications in CI

Create a detailed specification for a dashboard, covering its purpose, panels, data sources, refresh schedules, and interactions. Use a reusable structure to document what each panel shows and how users and external systems interact with it.

• Define requirements before building a dashboard
• Document data sources and refresh schedules for each panel
• Specify navigation and external system connections

Write a specification section that a contractor can price accurately and a site can build from — performance stated, products defined, workmanship and tolerances given, and the coordination with the drawings made explicit. Use when asked to write a specification, spec a material or system, prepare an NBS-style section, or when a specification produced wildly different tender prices. Produces the scope and interface definition, the performance requirements, the product or system definition, execution and tolerance requirements, and the submittals and testing schedule.

The English summary is being prepared. Showing the original description.