「criteria」の検索結果

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

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

Feature specification creation from codebase research. Produces requirements, acceptance criteria, architecture decisions, implementation plans, and risk analysis.

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

Migrate Hibernate 5 to Hibernate 6 with Spring Boot 3. Use when fixing HQL/JPQL query parsing issues, removing deprecated Criteria API, updating ID generation strategies, or diagnosing N+1 query behavior changes. Covers breaking changes, type mappings, and performance monitoring.

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

Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.

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

Refine a draft task specification into a fully planned, implementation-ready task with acceptance criteria, architecture, per-step sub-task files and verifiable phases

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

Draft a structured preregistration document (OSF, AsPredicted, or AEA RCT Registry style) from a research spec or free-form study description. Output is a Markdown file with hypotheses, design, sampling plan, analysis plan, exclusions, and inference criteria — annotated with MUST / SHOULD / MAY clarity flags. Use when user says "preregister", "draft a preregistration", "OSF preregistration", "AsPredicted", "AEA RCT registry", "PAP", "preanalysis plan", or before launching an experiment / data collection / analysis on data the analyst has not yet seen. NOT a registry submission tool — produces a document the user uploads to OSF / AsPredicted / AEA themselves.

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

The screenwriting business and career (编剧行业与生意经) — merged from Diamond & Weissman's Bulletproof (buyer's-eye workflow, three Cs, one-page nine-step, set pieces, submission, notes, resilience), Eric Bork's The Idea (PROBLEM seven-element idea test, 60/30/10, television differences), Neill Hicks (market four entities, six criteria, WGA, agents, option, credit arbitration, gross vs net, step deals), Richard Walter (query letter, agents, package, option, spec, release, copyright, guild, gatekeepers, professionalism, 66 principles), Wendy Henson (breaking in), Blake Snyder (logline pitch, genre, agents), Julian Hoxter (industry terms), Mei Feng's Oscar analyses, and the Hollywood masterclass (pitching, notes, credits, TV vs film). Use when evaluating whether an idea is sellable, writing a logline/query/pitch, preparing a submission, handling notes and rewrites, understanding options/credits/WGA/agents/net profit, choosing between film and TV, or building a career strategy.

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

Use when preserving product intent, acceptance criteria, decision memory, open loops, roadmap context, or the product-manager continuity layer of an agent team.

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

Recover source-bound buyer jobs, struggling moments, desired progress, forces, workarounds, information acts, journey states, criteria, constraints, roles, locales, and authentic language. Use on approved ICP hypotheses plus customer, search, review, forum, procurement, support, or public-market evidence before designing an AI-visibility prompt architecture.

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

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.

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

Build, refresh, report, or probe an accessibility coverage matrix across criteria, surfaces, and evidence methods. Use when assessing coverage with the accessibility runtime harness and generated evidence bundle.

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

Design LLM-as-Judge evaluators for subjective criteria that code-based checks cannot handle. Use when a failure mode requires interpretation (tone, faithfulness, relevance, completeness). Do NOT use when the failure mode can be checked with code (regex, schema validation, execution tests); use `write-code-eval`. To validate an existing judge, use `validate-evaluator`.

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

Build a playable prototype in about an hour to answer one question — is it fun? — with greybox primitives, a hard timebox, and explicit keep/kill criteria. Use when prototyping a mechanic, making a vertical slice or MVP, greyboxing/blockout, or judging throwaway vs keep.

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

Prepare a promotion defence (晋升答辩) for a level-based promotion process common at Chinese technology companies: the materials, the presentation structure, the evidence for the next level, and a rehearsal of the committee's questions. Use when asked 帮我准备晋升答辩, 晋升述职, 晋升 PPT, how do I prepare for my promotion committee, or 答辩问题. Produces a level-gap analysis against the target level's criteria, the defence presentation outline in Chinese, a timed talk track, and a question bank with answer points, then a mock committee round.

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

Use when asked 写8D报告, 客户投诉8D, 质量问题8D, 客诉回复报告, 8D 怎么写, 根本原因分析报告, or write an 8D problem-solving report for a customer complaint or internal quality issue in a Chinese factory. Produces a bilingual (Chinese and English) 8D report from D0 to D8 with the problem described by 5W2H, dated containment actions and suspect-stock quantities, root cause for both occurrence and escape (流出) with 5 Why and fishbone evidence, verified corrective actions, prevention through updated PFMEA, control plan and SOP, and closure criteria, in the format customers expect.

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

Use when asked 5S 检查表, 6S 管理, 现场管理检查, 5S 评分标准, 车间 6S 稽核, 做一份 5S 推行计划, or design a 5S or 6S audit for a workshop, warehouse or office in a Chinese factory. Produces an audit checklist for the area with scored criteria for 整理, 整顿, 清扫, 清洁, 素养 (and 安全 for 6S), a scoring guide with photo evidence rules, a results summary and red-tag list, a corrective-action tracker with owners and dates, and an audit rota, in Chinese.

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

Run a consulting client discovery session — uncover the real problem, scope, and decision process. Use when asked to prepare for a client discovery call, qualify a consulting lead, scope an engagement, or run a kickoff. Produces a discovery plan — the questions that surface the real problem (not the stated one), budget/authority/timeline qualifiers, success criteria, red flags, and a follow-up that leads to a proposal.

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

Interview the user with sharp, one-at-a-time questions to turn a vague request into a tight, complete brief any other skill can run on. Use when a request is fuzzy, under-specified, or 'help me think this through', or before running a skill that needs inputs the user hasn't given. Produces a structured brief (goal, audience, constraints, success criteria) and hands off to the right skill — by interrogating, not guessing.

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

Take a board game idea from 'wouldn't it be cool if' to a playtestable prototype — core loop, tension source, components you can make tonight, balance starting-points, and a real playtest protocol with kill criteria. Use when someone says 'I have a board game idea', 'design a game about X', 'my game drags in the midgame', or 'how do I playtest this'. Produces a design one-pager, a print-and-play prototype spec, and a 3-session playtest plan.

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

Write a PRD for an AI-powered feature, covering the things normal PRDs miss. Use when asked to spec an AI/LLM feature, write a PRD for a feature that uses a model, or plan an AI capability (assistant, summarizer, generator, classifier). Produces an AI feature PRD — problem & UX of uncertainty, model approach, eval criteria, guardrails, fallback behaviour, the data flywheel, and cost/latency budget.

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

Turn product requirements into scoped tasks with dependencies and acceptance criteria. Use for implementation planning and prioritization.

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

Deep Codex-native Amazon FBA product validation using LaunchFast MCP and the LegacyX criteria. Use when the user wants a serious viability review for a keyword, niche, or adjacent niche expansion.

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

Use Superloopy's lightweight strict-evidence loop for Codex tasks that need durable progress, criteria, and artifact-backed completion.

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

Refine an existing Agiflow task into an unambiguous, testable specification without expanding its intended outcome. Use when a task is vague, lacks acceptance criteria, has unclear scope or dependencies, or is not ready for backlog grooming.

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