1,580 件 ・ 関連度順
概要と使いどころ
Use for every coding task. Enforce strict TDD workflow: activate Serena, investigate first, clarify+confirm requirements, write per-task REQUIREMENTS.md in .requirements/<datetime>_<feature_name>/, verify APIs via web search, then implement in tiny test-verified steps.
日本語の概要は準備中です。原文の説明を表示しています。
Write accessibility requirements. TRIGGERS - Use when user needs help with accessibility-requirements related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Auto-activates when analyzing GitHub issues to extract functional requirements, non-functional requirements, acceptance criteria, and user stories.
日本語の概要は準備中です。原文の説明を表示しています。
Generate Product Requirements Documents (PRDs) in Markdown format. Use when users want to create a PRD, spec out a feature, document requirements, or plan new functionality. Triggers on requests like "create a PRD", "write requirements for", "spec out this feature", or "document this feature idea".
日本語の概要は準備中です。原文の説明を表示しています。
Write a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".
日本語の概要は準備中です。原文の説明を表示しています。
Write a Business Requirements Document. Use when the user says "write a BRD", "business requirements", "document the business need", "vision and scope document", "business case for this feature", "what does the business need", "strategic requirements", "document why we need this" - even if they don't explicitly say "BRD".
日本語の概要は準備中です。原文の説明を表示しています。
BA (Business Analyst) agent. Analyzes requirements and produces 4 artifact files: requirements.md, user-stories.md, acceptance-criteria.md, business-rules.md. Use --spec <path> to load requirements from any markdown file. Part of the Virtual Team Skill pipeline.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when defining patient engagement portal requirements for Health Cloud: appointment scheduling, secure in-portal messaging, health assessments, patient education, and self-service features. NOT for care team workflows, SDOH barriers and care gaps — use admin/care-coordination-requirements. NOT for patient portal licensing and cloud topology — use architect/health-cloud-multi-cloud-strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when designing HIPAA-compliant workflow requirements for Health Cloud: minimum necessary access design, audit trail requirements mapping, access control patterns, and BAA dependency identification. NOT for org-level HIPAA architecture or Shield encryption configuration — use architect/hipaa-compliance-architecture. NOT for care team and SDOH process design — use admin/care-coordination-requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when designing the checkout experience for a Salesforce B2B or D2C Commerce storefront — covering runtime model selection (LWR Managed Checkout vs Aura Flow Builder), cart and line-item requirements, payment option scoping, shipping rule definition, and guest vs. registered buyer experience design. Trigger keywords: checkout flow design, checkout UX requirements, LWR vs Aura checkout, guest checkout design, payment options design, shipping rules, checkout experience planning. NOT for configuring the checkout in Setup once designed — use admin/commerce-checkout-configuration. NOT for choosing B2B vs D2C Commerce — use admin/b2b-vs-b2c-requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when designing the FSC client onboarding process — mapping document collection touchpoints, approval steps, compliance checkpoint sequencing, and welcome journey handoffs. Trigger keywords: client onboarding design, onboarding workflow requirements, document collection flow, compliance checkpoint, welcome journey, intake process design. NOT for configuring the Action Plan template itself — use admin/fsc-action-plans. NOT for OmniScript screen and branching requirements — use admin/omniscript-flow-design-requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.
日本語の概要は準備中です。原文の説明を表示しています。
AI compliance analysis for EU AI Act, ISO 42001, NIST AI RMF, GDPR, OECD, financial services regulations (SEC, FCA, FINRA, DORA, MiFID II), and other frameworks. Use when asked to generate a compliance checklist for an AI tool or use case, determine if a risk assessment is required, score an AI tool's risk level, identify where an AI tool or use case could run afoul of regulatory requirements, perform a gap analysis, recommend remediation steps, assess a vendor, draft an acceptable use policy, map training requirements, or review jurisdiction-specific AI rules. Triggers on phrases like "compliance checklist", "risk assessment", "risk score", "does this comply", "EU AI Act", "ISO 42001", "NIST AI RMF", "AI governance", "gap analysis", "vendor assessment", "acceptable use policy", "MNPI", "AI training requirements", or any request to evaluate an AI tool or use case for regulatory compliance or risk.
日本語の概要は準備中です。原文の説明を表示しています。
Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).
日本語の概要は準備中です。原文の説明を表示しています。
【非推奨】requirement-management に統合された。新規の要件定義には requirement-management を使用すること。既存の docs/sdd/requirements/ を保守・参照する場合にのみ使用する。EARS記法によるMarkdownの要件定義書（ユーザーストーリー・受入基準・非機能要件）を作成・編集する。Do NOT use for 新規プロジェクトの要件定義（requirement-management を使用すること）。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Ensure requirement docs define scope, terminology, acceptance criteria, edge cases, and non-functional requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Write accessibility requirements. TRIGGERS - Use when user needs help with accessibility-requirements related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
開発作業の要件定義書（requirements.md）を単体で生成・再生成します。全ドキュメントの一括生成には generate-working-docs（新規機能開発）または generate-performance-docs（パフォーマンス改善）を使用してください。
開発作業の要件定義書（requirements.md）を生成します。このスキルは単独で使用することも、generate-working-docsから呼び出されることもあります。
共有のレビュー手順と補助スクリプトを使い、対象リポジトリ固有の要件も踏まえてコードを確認するスキル。OpenClawの共通インストールを参照します。
OpenClawのセキュリティ勧告を確認・修正し、非公開フォークの未完了PRや公開条件を検証。承認を経た公開と、公開後の状態確認まで扱うスキル。
機能の実装後やマージ前に、別のエージェントへコードレビューを依頼します。変更内容と要件、対象のコミットを渡し、指摘の重要度に応じて修正を進めるスキルです。