「criteria」の検索結果

Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews integration completeness including design-implementation consistency, review/test coverage, and completion criteria. Use when performing integration review in Construction Phase.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when writing sprint contracts in VCSDD strict mode. Provides grading criteria patterns, dimension weight guidelines, and pass threshold formulation for the 5 review dimensions.

日本語の概要は準備中です。原文の説明を表示しています。

Run Phase 6 (convergence check) for the active VCSDD feature. Validates four-dimensional convergence: finding diminishment, finding specificity, criteria coverage, and duplicate detection.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when evaluating VCSDD grading dimensions during adversarial review. Provides concrete evaluation checklists for each of the 5 dimensions and convergence signal detection.

日本語の概要は準備中です。原文の説明を表示しています。

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.

日本語の概要は準備中です。原文の説明を表示しています。

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

日本語の概要は準備中です。原文の説明を表示しています。

Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "create an agent", "write a subagent", "generate agent definition", "add agent to plugin", "write agent frontmatter", "create autonomous agent", "build subagent", needs agent structure guidance, YAML frontmatter configuration, invocation criteria with examples, or wants to add specialized subagents to Claude Code plugins with proper capabilities lists and tool access definitions.

日本語の概要は準備中です。原文の説明を表示しています。

MATLAB R2026a testing, validation, and CI workflow for matlab.unittest, MATLAB Test, Simulink Test, coverage, artifact generation, GitHub Actions, and open-source reproducibility. Use whenever MATLAB work needs verification, regression tests, CI, GitHub publication, or acceptance criteria.

日本語の概要は準備中です。原文の説明を表示しています。

Assesses a research paper outline (.qmd file) against structured criteria from Kosuke Imai's empirical research guide. Evaluates the abstract and section outline for: research question clarity, stated contributions, hypotheses and testable implications, data description, planned results and inferential approach, and robustness checks. Detects causal papers from the abstract and conditionally assesses identification strategy only when causal framing is present. Produces a structured markdown report with PASS/PARTIAL/FAIL assessments and actionable suggestions. Use when asked to assess, evaluate, review, or check a paper outline, abstract-and-outline, or research plan in a .qmd file.

日本語の概要は準備中です。原文の説明を表示しています。

"Apply the Resource-Based View (Barney, 1991) and VRIO framework to evaluate whether a firm's resources and capabilities confer sustained competitive advantage. Use this skill when the user needs to assess internal resources for strategic value, determine if a competitive edge is sustainable, audit resource portfolios for VRIO criteria, or when they ask 'what makes our advantage sustainable', 'which resources matter most', or 'can competitors replicate this'.".

日本語の概要は準備中です。原文の説明を表示しています。

Auto-activates when analyzing GitHub issues to extract functional requirements, non-functional requirements, acceptance criteria, and user stories.

日本語の概要は準備中です。原文の説明を表示しています。

Validate user stories against INVEST criteria and suggest improvements

日本語の概要は準備中です。原文の説明を表示しています。

Use when a user asks for or clearly wants to be grilled, interviewed, or to stress-test a plan or design, including when they mention "grill me". Resolve material decisions one at a time until scope, success criteria, and resources are explicit.

日本語の概要は準備中です。原文の説明を表示しています。

Build structured vendor/tool evaluation matrices with weighted scoring, TCO analysis, and recommendation memos. Covers criteria definition, deal-breaker identification, and negotiation points. Use when selecting SaaS tools, evaluating technology vendors, or making build-vs-buy decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Create structured employee onboarding plans using the 30-60-90 day framework aligned with SHRM best practices. Cover pre-boarding, Day 1, Week 1, and monthly milestones with task owners, success criteria, and buddy assignments. Use when hiring new employees or revamping the onboarding process.

日本語の概要は準備中です。原文の説明を表示しています。

Write structured job descriptions with clear requirements, responsibilities, and employer value proposition. Follows SHRM BASK competency framework. Adapts tone to employer brand and industry context. Use when creating new positions or updating existing JDs. Do not use for internal performance criteria or career ladder definitions.

日本語の概要は準備中です。原文の説明を表示しています。

Frontend specification planning frameworks. Use when a spec touches UI components, forms, client state, or user-facing flows. Covers UI-state completeness (loading, error, empty, success), component boundaries, form validation contracts, state ownership, and measurable UI success criteria.

日本語の概要は準備中です。原文の説明を表示しています。

Write a comprehensive product or engineering specification before implementation. Use when the user asks for `/spec`, PRDs, feature specs, API specs, refactor specs, acceptance criteria, user stories, edge cases, or open decision tracking before code is written.

日本語の概要は準備中です。原文の説明を表示しています。

End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue properly", or /gaia-issue-resolver. Works any gaia-research org repo — gaia-skill-tree, gaia-research, gaia-skill-heaven — while the issue itself lives on the headquarters tracker, gaia-research/gaia-skill-tree. Assumes the issue is already triaged and carries a P0–P4 label; if it does not, run /gaia-triage first.

日本語の概要は準備中です。原文の説明を表示しています。

Frames a structured, testable threat-hunting hypothesis: grounding it in adversary behavior and available telemetry, defining the data sources and detection logic, and setting success criteria and outcomes. Activates for requests to start a threat hunt, write a hunt hypothesis, or plan a hypothesis-driven hunt.

日本語の概要は準備中です。原文の説明を表示しています。

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.

日本語の概要は準備中です。原文の説明を表示しています。

Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.

日本語の概要は準備中です。原文の説明を表示しています。