'specification' 검색 결과

Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.

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

Create a new specification through an adaptive interview process with proactive recommendations and optional research. Use when user says "create spec", "new spec", "generate spec", or wants to start a specification document.

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

Guide requirement writing, user story creation, and feature specification. Use when: writing requirements, user stories, issues, feature planning. Keywords: requirement, user story, issue, feature, specification, 需求, 功能規劃, 規格.

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

Verify that implementation code faithfully implements its specification — checks function contracts, API contracts, and protocol compliance against source specifications

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

Extract comprehensive site specifications from simple descriptions. Use when analyzing a user's theme request to determine site type, audience, tone, layout requirements, and typography.

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

Use when starting a new feature, product, or system design. Eliminates the spec-implementation gap by making specifications the primary artifact that drives code generation. Keywords: SDD, spec-driven, PRD, feature spec, user stories, implementation plan, specification, acceptance criteria, Given-When-Then.

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

Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.

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

Use when creating, configuring, reviewing, or debugging TypeScript project standards across frontend apps, libraries, SDKs, CLIs, monorepo packages, tsconfig, strictness, module/moduleResolution, path aliases, project references, declaration files, package exports, public API types, DTOs, advanced generics, discriminated unions, type guards, type narrowing, or type-level regressions. Prefer framework project skills for React/Vue/Next/Nuxt component architecture; Chinese triggers include TypeScript project specification, TS project specification, TypeScript type safety, type modeling, generics, discriminative unions, type narrowing, tsconfig, declaration files.

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

Use when the user says "write a spec", "create RFC", "write a PRD", or "document this decision". Writes technical specifications, PRDs, RFCs, and ADRs with clear structure.

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

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

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

reqordデータ（Requirement, Specification）の新規作成。対話的にデータを作成し、初期品質を確保する。

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

reqordデータ（Requirement, Specification, ProjectContext）の編集・改善を統合的に行う。reqのSMART品質改善、specのdesign.md技術設計書の生成・更新、contextの充実化をカバーする。

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

Reqordのデータモデル（Requirement, Specification, ProjectContext, Feedback）とCLI操作ルールの共通知識ベース。

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

Signpost (not a knowledge pack) for OMG modelling specifications — UML, SysML, BPMN, UAF, SoaML, MOF, OCL, XMI, DDS. Contains NO source content: it only points to where the official specs live and what each is for. Use when you need an OMG modelling/architecture specification — the OMG licence forbids redistributing or transforming the text, so these cannot be reconstituted into a pack; download them from OMG directly.

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

Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025). Use for model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders, requirements, structure and V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Scope is bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation). Does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10-17, or reproduce the OMG SysML specification.

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

Unity カジュアルゲームを仕様駆動開発（Specification-Driven Development）で作成する。仕様を先に確定させ、設計・実装・テストを行うことで手戻りを最小化する。「ゲームを作って」「仕様駆動開発」「SDD」「ゲーム企画書」「機能仕様書」「技術仕様書」「テスト仕様書」「タスクリスト」「Unityゲーム開発」「カジュアルゲーム」といったリクエスト時に使用。Phase 1（企画書）からPhase 8（リリース）まで段階的にドキュメントを作成し、仕様に基づいて実装・テスト・検証を行う。

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

Plan UX patterns and design specifications. Use when the user says "lets create UX design" or "create UX specifications" or "help me plan the UX"

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

Flutterプロジェクトの画面定義書（screen specification）を作成・管理するスキル。 「画面定義書を作成したい」「〇〇画面の定義書を作って」などの発言で発動し、 プロジェクト構造を解析してテンプレートをセットアップし、個別の画面定義書を生成します。

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

Extract and analyze Figma designs to create structured design specifications. Use this skill when you need to analyze Figma nodes, extract design properties (layout, spacing, typography), classify components using Atomic Design principles, and generate design specification documents that can be used for implementation.

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

Generate production-ready Next.js/React components from design specifications. Use this skill when you have a design specification document and need to create React/TypeScript components with Tailwind CSS styling, Vitest tests, and Storybook documentation.

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

Generates DDD Specification for PHP 8.5. Creates reusable business rule objects for validation, filtering, and querying with composite pattern support. Includes unit tests.

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

Create GitHub Issue for feature request from specification file using feature_request.yml template.

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

Create GitHub Issues for unimplemented requirements from specification files using feature_request.yml template.

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

Create a formal specification for an existing GitHub Actions CI/CD workflow, optimized for AI consumption and workflow maintenance.

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