Create a qualitative risk register and mitigation plan using a Probability x Impact matrix. Use when a project needs structured risk identification, scoring, ownership, and response planning.
日本語の概要は準備中です。原文の説明を表示しています。
テスト設計、脆弱性診断、品質保証(1.3万 件)
Create a qualitative risk register and mitigation plan using a Probability x Impact matrix. Use when a project needs structured risk identification, scoring, ownership, and response planning.
日本語の概要は準備中です。原文の説明を表示しています。
Run a structured Azure incident response workflow for triage, diagnosis, mitigation, and root cause analysis. Use when operations or security teams need guided incident handling for Azure service symptoms.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP CI/CD Top 10 knowledge base for identifying, assessing, and remediating CI/CD pipeline security risks.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP MCP Top 10 knowledge base for identifying, assessing, and remediating Model Context Protocol security risks.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP Docker Top 6 knowledge base for identifying, assessing, and remediating Docker container security risks.
日本語の概要は準備中です。原文の説明を表示しています。
Retrieves and groups GitHub code scanning alerts by rule and severity using the gh CLI
日本語の概要は準備中です。原文の説明を表示しています。
Software supply chain security reference for OpenSSF Scorecard, SLSA, Sigstore, SBOM, and posture/backlog taxonomies.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP Top 10 for Web Applications (2025) knowledge base for identifying, assessing, and remediating web application security risks.
日本語の概要は準備中です。原文の説明を表示しています。
Format specifications and data contracts for the security reviewer orchestrator and its subagents.
日本語の概要は準備中です。原文の説明を表示しています。
Security planning and plan-drift analysis for STRIDE, standards, controls, backlog handoff, current findings, and TM7 generation.
日本語の概要は準備中です。原文の説明を表示しています。
Secure by Design principles knowledge base for assessing security-first design, development, and deployment across the software lifecycle.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP Agentic Security Top 10 knowledge base for identifying, assessing, and remediating AI agent system security risks.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP Infrastructure Top 10 knowledge base for identifying, assessing, and remediating internal IT infrastructure security risks.
日本語の概要は準備中です。原文の説明を表示しています。
OpenVEX v0.2.0 specification reference plus VEX management playbooks - Brought to you by microsoft/hve-core.
日本語の概要は準備中です。原文の説明を表示しています。
Shared work-item templates and conventions for ADO and GitHub backlog handoff across the RAI, Security, SSSC, Accessibility, and Privacy planners
日本語の概要は準備中です。原文の説明を表示しています。
Microsoft Cloud Security Benchmark (MCSB v2) control-domain taxonomy and NIST 800-53 / CIS Controls crosswalk for planning and reviewing Azure cloud resources.
日本語の概要は準備中です。原文の説明を表示しています。
OWASP Top 10 for LLM Applications (2025) knowledge base for identifying, assessing, and remediating large language model security risks.
日本語の概要は準備中です。原文の説明を表示しています。
Authors Vally conformance tests for prompts, instructions, agents, and skills, and refuses jailbreak, prompt-injection, harmful-elicitation, TOS, CoC, and PII-extraction stimuli
日本語の概要は準備中です。原文の説明を表示しています。
Performance, load, and reliability (SLO/SRE) planning for production readiness. Use when defining service level objectives, load characterization, capacity, latency budgets, stress/soak/spike test plans, false-positive baselines, and reliability targets. USE FOR: SLO/SLA definition, load testing plan, performance budget, capacity planning, reliability/SRE backlog, latency targets, error-budget policy. DO NOT USE FOR: executing load tests (use Azure Load Testing tooling), security threat modeling, RAI assessment, privacy/compliance planning, or authoring/restating PRD requirements (cite the PRD's existing NFR/FR ids instead).
日本語の概要は準備中です。原文の説明を表示しています。
Capture VS Code screenshots and self-contained browser animation scenes through Playwright. Use for editor evidence, slide imagery, or silent WebM scene clips.
日本語の概要は準備中です。原文の説明を表示しています。
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or unreliable test failures, or when the user mentions flaky tests, test smells, brittle tests, test isolation issues, mock overuse, slow tests, or test maintenance problems.
日本語の概要は準備中です。原文の説明を表示しています。
Applies the scientific method to debugging by helping users form specific, testable hypotheses, design targeted experiments, and systematically confirm or reject theories to find root causes. Use when a user says their code isn't working, they're getting an error, something broke, they want to troubleshoot a bug, or they're trying to figure out what's causing an issue. Concrete actions include isolating failing components, forming and testing hypotheses, analyzing error messages, tracing execution paths, and interpreting test results to narrow down root causes.
日本語の概要は準備中です。原文の説明を表示しています。
Guides the red-green-refactor TDD workflow: write a failing test first, implement the minimum code to make it pass, then refactor while keeping tests green. Use when a user asks to practice TDD, write tests first, follow red-green-refactor, do test-driven development, write failing tests before code, or phrases like 'make the test pass', 'test coverage', or 'unit tests before implementation'.
日本語の概要は準備中です。原文の説明を表示しています。