2,022 件 ・ 関連度順
概要と使いどころ
Create and manage tickets — initiatives, epics, stories, bugs. Use when the user says "create a new initiative", "slice this initiative", "split this epic up", "break this into stories", "incept this epic", "make a ticket", "refine this ticket", "what's ready", "status of a story", "publish ticket changes", "validate these tickets", "set up the ticket store".
日本語の概要は準備中です。原文の説明を表示しています。
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief
日本語の概要は準備中です。原文の説明を表示しています。
Smithy the Toolsmith builds, converts, reviews, packages, validates and migrates BMad skills, agents and modules. Use when the user wants a skill, agent, persona, command or module made, changed, reviewed or packaged; a prompt or rule from another tool turned into a skill; a skill mined from session logs; an old module migrated; or asks for Smithy. Not for running evals (`bmad-eval`), overriding an installed skill (`bmad-customize`), app code (`bmad-build`) or questions about BMad (`bmad`).
日本語の概要は準備中です。原文の説明を表示しています。
Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD
日本語の概要は準備中です。原文の説明を表示しています。
Work out and record the architecture decisions that keep separately built parts of a system consistent, in a short architecture document. Creates, updates, or validates one; works from a spec, a raw idea, or an existing codebase. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design"
日本語の概要は準備中です。原文の説明を表示しています。
Verify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.
日本語の概要は準備中です。原文の説明を表示しています。
Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.
日本語の概要は準備中です。原文の説明を表示しています。
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
日本語の概要は準備中です。原文の説明を表示しています。
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
日本語の概要は準備中です。原文の説明を表示しています。
Environment-aware pre-flight check. Use when starting work in a new environment, switching machines, or when 'works on my machine' bugs surface. Validates OS, runtime versions, installed tools, port availability, env vars, and disk space BEFORE coding starts. Like sentinel but for the environment, not the code.
日本語の概要は準備中です。原文の説明を表示しています。
Validates agent claims against evidence trail. Use when verifying an agent has actually done what it claims — auto-fires at workflow end. Catches 'done' without proof, 'tests pass' without output, 'fixed' without verification. Called by cook and team.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-commit quality gate that catches 'almost right' code. Use when about to commit — auto-fires before commit to validate logic correctness, error handling, regressions, and completeness. Goes beyond linting.
日本語の概要は準備中です。原文の説明を表示しています。
Database workflow specialist. Generates migration files with rollback scripts, detects breaking schema changes, and validates query parameterization.
日本語の概要は準備中です。原文の説明を表示しています。
Protects complex business logic from accidental deletion or overwrite. Use when editing payment, trading, state-machine, or other load-bearing business logic where a single deleted line can cause silent data corruption. Maintains a logic manifest, enforces pre-edit gates, validates post-edit diffs.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate and resolve Course Management Platform CloudWatch alert issues end to end. Use when Codex is asked to inspect a CMP GitHub alert issue, pull dev or production AWS logs, diagnose 5xx responses or failed background work, fix an incident with test-driven development, validate a fix in dev, or deploy and verify an authorized production fix.
日本語の概要は準備中です。原文の説明を表示しています。
Build, deepen, validate, index, and maintain a private hierarchical career knowledge graph from supplied career materials. Use when the user asks to create or update a VitaeGraph, model education with nested courses or thesis work, enrich projects from Git repositories, or supply deep selected career context to another VitaeContext skill.
日本語の概要は準備中です。原文の説明を表示しています。
Remix v2 data loading and mutations. Use when writing loaders, actions, deferred data, revalidation logic, or pending state. Triggers on loader, action, useLoaderData, useActionData, json(), defer(), <Await>, shouldRevalidate, useRevalidator, useNavigation, useTransition (v1 holdover).
日本語の概要は準備中です。原文の説明を表示しています。
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
日本語の概要は準備中です。原文の説明を表示しています。
Validate hooks configuration and scripts. Use after adding or editing hooks in settings.json, before committing hook changes, or when a hook fails to fire.
日本語の概要は準備中です。原文の説明を表示しています。
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
日本語の概要は準備中です。原文の説明を表示しています。
Validate CLAUDE.md structure and completeness
日本語の概要は準備中です。原文の説明を表示しています。
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
日本語の概要は準備中です。原文の説明を表示しています。
Act as an end-to-end data scientist: turn business questions into defensible analysis, validated models, and decision-ready reports. Use whenever the user asks to analyze, explore, or profile a dataset or CSV/Parquet/Excel file; asks what drives a metric or why a number changed ("why did churn go up?"); wants to test whether a difference is real (A/B tests, experiments, "is this significant?", "how many samples do I need?"); wants a predictive model (churn, forecast, scoring, segmentation, classification, regression); asks to review an existing analysis, notebook, or model for flaws; or needs results written up for decision-makers. Triggers in any language ("phân tích dữ liệu", "xây model dự đoán", "kiểm định A/B"), even when they never say "data science" or "statistics".
日本語の概要は準備中です。原文の説明を表示しています。
The low-level on-chain probes for identifying what an owner address is — cast code → EOA / EIP-7702-delegated EOA / contract, VERSION() → Gnosis Safe, read-only get-owner-ica.ts derive → ICA derivation, getAccountInfo → Sealevel account existence — with how to interpret each result. The primitive layer beneath validate-owners / resolve-artifacts / update-owners, which each apply their own per-chain or per-artifact policy on top.
日本語の概要は準備中です。原文の説明を表示しています。