「sign-off」の検索結果

Present a design to a client so they can make a decision rather than react to a picture — the brief restated, the moves explained against it, the options with their trade-offs, and a specific decision requested. Use when asked to present a design to a client, prepare a design review meeting, present concept options, or when a client keeps changing their mind after sign-off. Produces the presentation structure, the brief-to-design traceability, the options with honest trade-offs, the cost and programme position, and the decision record that makes sign-off stick.

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

Guides the periodic DPIA review lifecycle including trigger identification for regulatory changes, new data categories, technology changes, and breach incidents. Covers version control, stakeholder sign-off procedures, and DPIA register management per Art. 35(11). Keywords: DPIA review, PIA update, review cadence, version control, Art. 35(11), periodic review, trigger events, stakeholder sign-off.

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

Manage QA release gates - go/no-go decisions, release sign-off reports, defect triage, and release readiness communication. Use this skill whenever a QA lead or manager needs to formally assess whether a build is ready to ship. Trigger on phrases like "release sign-off", "go or no-go", "is this ready to release", "defect triage", "release gate", "approve the release", "block the release", "release readiness", "quality gate", "sign off on this build", "triage these bugs", or any request to make or document a formal release decision. Also trigger when a release manager or PM asks "what's the QA status?" or "can we ship this?".

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

Generate a User Acceptance Testing plan with scenarios and sign-off criteria. Use when the user says "UAT plan", "acceptance testing", "user testing plan", "how do we test this with users", "test scenarios for business validation", "sign-off criteria", "go/no-go for release", "acceptance test cases", "validate with stakeholders" - even if they don't explicitly say "UAT".

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

QA/QC agent. Reads ALL pipeline artifacts (BA + TechLead + PM + BE + FE + Tester) and produces quality-report.md, compliance-check.md, and sign-off.md. Declares Gate 3: Release Sign-off (advisory only — operator has final authority). Part of the Virtual Team Skill pipeline.

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

Canonical go-live checklist for Agentforce deployments with rehearsed rollback and stakeholder sign-off records. NOT for the technical pre-prod verification behind those sign-off rows — cost telemetry, rate limits, canary rollout, latency benchmarks — use agentforce/agentforce-production-readiness-checklist. NOT for general Salesforce release management — use devops/release-management.

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

Manages end-to-end workflow for multi-organization amicus coalition briefs in appellate courts. Covers single-pen drafting governance, position alignment, conflict resolution, documented sign-offs, FRAP 29/Rule 37.6 disclosures, FRAP 26.1 corporate disclosures, cover formatting for multiple amici, and compliant filing. Use when coordinating coalition amicus briefs, managing sign-offs, drafting joint friend-of-court briefs, handling multi-amici filing, or resolving inter-organization conflicts. Triggers on phrases like "coalition brief," "12 orgs joining this amicus," or "coordinate the amicus."

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

The router for how a change legally happens in this repo — which sign-off gate fires for which kind of change, what counts as approval, how the packages-edit guard works, and how work is allowed to reach main. Use when starting ANY change and unsure which rules apply, when an Edit to packages/* gets BLOCKED, when a pipeline issue sits on status:blocked and you need to know what unblocks it, or when asked "do I need sign-off for this", "how do I get this merged", "can I deploy this", "who approves X", "why won't my approval label/reaction do anything".

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

Multi-stage series — a request for several classrooms that belong together, like 「7 天学 Python」, a four-week onboarding track, a semester unit split across lessons, or "turn this book into a lesson per chapter". Clarifies the series brief, gets the user's explicit sign-off on the full lesson list before spending anything, then builds the stages one at a time into a shared folder. Use when the ask is a sequence of classrooms; not for a single stage, however large.

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

Draft and review professional emails that match your personal writing style. Analyzes your sent emails for tone, greeting, structure, and sign-off patterns via WorkIQ, then generates context-aware drafts for any recipient. USE FOR: draft email, write email, compose email, reply email, follow-up email, analyze email tone, email style.

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

Evaluate a vendor — cost analysis, risk assessment, and recommendation. Use when reviewing a new vendor proposal, deciding whether to renew or replace a contract, comparing two vendors side-by-side, or building a TCO breakdown and negotiation points before procurement sign-off.

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

Orchestrate the QA team through a full testing cycle — qa-lead strategy and test plan, qa-tester case writing, execution, sign-off.

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

Launch readiness across every department: code, content, store, marketing, community, infrastructure, legal, go/no-go sign-offs.

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

Fast first-pass NDA review for {{nda_label}}. Saves a new inbound NDA into {{nda_folder}}, checks it clause-by-clause against our standard NDA positions, drafts redlines on what deviates, and drafts a flag summary for counsel — holding every redline and flag for counsel's sign-off. Never signs or sends.

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

Route a contract issue to the right approver per the escalation matrix in `~/.claude/plugins/config/claude-for-legal/commercial-legal/CLAUDE.md`, and draft the ask. Use when the user says "who needs to approve this", "escalate this", "does this need GC sign-off", "route this for approval", or when another skill finds an issue that exceeds the reviewer's authority.

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

External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining, internal-package-name leakage, and CI/CD configuration exposure. Reconnaissance and identification ONLY — actual package publishing / typosquat attacks are EXTERNAL-OFFENSIVE and require explicit written sign-off because they can affect the entire npm/PyPI ecosystem. Use when the target has a public GitHub org, when their build artifacts/SBOMs are reachable, when their docker images are on Docker Hub/GHCR, or when you find internal package names in their JS bundles.

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

群众路线：从持有真实情况的多方（用户、使用者、代码库、日志、运行结果）收集分散意见，系统化为方案，再带回去对齐与检验，循环改进。当多方意见分歧、需要汇总零散反馈、方案要拿回给真实使用者确认、或你发觉自己在闭门造车时触发；信息源单一且完整、处于执行阶段时不触发。 English: Mass line. Collect scattered input from everyone who holds ground truth (users, operators, codebase, logs, runtime results), synthesize it into a coherent plan, take it back for alignment and validation, and iterate. Trigger when inputs conflict, feedback must be consolidated, a plan needs sign-off from real users, or you sense you are designing in isolation; skip when there is a single complete source and the work is pure execution.

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

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.

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

Freshly judge whether a finished change and its claims meet original acceptance: PASS, FAIL or NOT_PROVEN. Use when: asked for a go/no-go, sign-off or independent verdict.

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

Three modes for CS-conference papers (CVPR/ICCV/ECCV vision, ACL/EMNLP/NAACL NLP, ICLR/NeurIPS/ICML/AAAI ML). DIRECT-EDIT mode (common): the user describes a change in Chinese or English and the manuscript (LaTeX or Markdown) is edited directly through a CS-venue writing toolkit with author sign-off (use for 改这段 / 把中文想法写成 latex / polish / de-AI / translate / compress a passage). REVIEW mode (occasional, pre-submission): harden the paper through an adversarial courtroom review engine (N holistic domain reviewers / contestability routing / two-sided trial / three-way verdict / clerk-converged multi-round loop) with consensus-gated, author-signed revisions (use for review / critique / 审稿 / 评审 / mock-review). AUTO mode (unattended, opt-in via /goal): run the review-revise loop toward a verifiable goal, applying safe fixes under a drift-bounded policy and queueing risky ones. Resolves all inputs at runtime, no hardcoded paths. Not a from-scratch drafter (use ml-paper-writing) and not an official-venue rebuttal.

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

Use when the user needs to bind users or teams to a Mobile Offline Profile so they actually receive offline sync on their devices. Without this, the profile exists in Dataverse but no one's app uses it.

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

RFP creation, distribution, evaluation, and shortlisting for in-house legal teams selecting outside counsel. Draft a new legal services RFP from scratch, evaluate firm responses against weighted criteria, produce a shortlist recommendation with selection rationale for GC sign-off, or design the end-to-end RFP process from scratch. Trigger on: 'draft an RFP', 'run an RFP process', 'evaluate firm responses', 'score the RFP submissions', 'which firms should we shortlist', 'selection recommendation', 'how do we run a panel RFP', 'RFP for legal services', 'pitch process', 'firm selection process', 'compare the proposals', 'we're reviewing our panel', 'panel refresh RFP', 'we need to go to market', 'request for proposal', 'evaluate the pitches', 'which firm won the RFP', 'write a legal RFP', 'RFP evaluation criteria', 'design the RFP process', 'how do we weight the criteria'.

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

Run an attorney-facing knockout/availability trademark search across the United States and Canada. Use whenever a user (founder, client, or attorney) asks whether a brand, mark, name, logo, slogan, or product name is "available," "free to use," "clearable," or "already taken" — or asks Claude to "search the trademark register," "check USPTO," "check CIPO," "do a knockout search," "clearance search," "availability search," or "see if [mark] is trademarked." Trigger even when the user phrases it casually ("can I call my company X?", "is this name taken?"). Covers federal USPTO (TESS/TSDR), federal Canada (CIPO), common-law/web/state, and WIPO Madrid international. Output is a knockout availability memo with green/yellow/red verdict for attorney review. Includes professional-responsibility gating (AI-use disclosure, conflict check, scope confirmation) before substantive analysis. Not legal advice — produces work product for attorney sign-off.

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

Generate an Architecture Review Board (ARB) presentation in Coco Inc's standard 11-slide format. Use when someone asks to "create an ARB deck", "architecture review presentation", "prepare for architecture review board", "ARB slides", or needs to present a product/platform architecture for sign-off. Reads PRD, architecture maps, and project memory to pre-fill technical content. Produces a self-contained HTML slide deck.

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