72건 · 관련도순
Coordinate QA agents to plan testing for a game development sprint or feature. Produce test cases, collect results from human testers, document bugs and visual evidence, and prepare a sign-off report based on recorded findings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Draft professional emails, replies, proposals, and follow-ups using the recipient context and your usual writing patterns. With WorkIQ, it examines sent messages for tone, greetings, structure, and sign-offs, then produces a draft for review and revision.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a game launch checklist covering code, content, quality, stores, legal preparation, infrastructure, marketing, and operations. Tailor checks to the project's stage and release requirements, then summarize blockers, accepted risks, missing confirmations, and required sign-offs.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Use Git changes to generate Conventional Commits messages, a format that labels each change by type, and create commits. The skill suggests splitting unrelated changes and supports explicit scope, type, sign-off, and amendments to the previous commit.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan and build a connected series of lessons around learners’ experience and goals. After the user approves the complete lesson list, it creates lessons in order, checks continuity, and organizes them in one folder.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinate month-end reconciliation, owner sign-off, and a 30/60/90-day cash forecast based on closed books. Combine the results into a reporting packet with financial explanations and open items, with approval required before external delivery.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Evaluate vendor proposals, renewals, or competing offers by comparing costs, risks, performance, and business fit. Produce a structured review with total ownership costs, a recommendation, and concrete points for contract negotiations.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan a prospective clinical study by ranking endpoints, estimating participant numbers and statistical power, and assessing feasibility. Outputs include assumptions and named reviewers, providing material for expert review before a protocol is finalized.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a first-pass review of incoming NDAs, or confidentiality agreements, against a team's standard positions. The skill saves the document, drafts suggested clause changes, and prepares a counsel summary without signing or sending anything.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Identify who should approve a contract issue using the team’s approval matrix and contract guidelines. The skill checks authority limits and exceptions, then drafts a request with the relevant wording, options, recommendation, and decision deadline.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Inspect public repositories, build artifacts, and container images for software supply chain risks. The skill identifies exposed internal package names, unsafe workflow configurations, and leaked secrets, while requiring build evidence before treating unclaimed package names as exploitable.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
群众路线：从持有真实情况的多方（用户、使用者、代码库、日志、运行结果）收集分散意见，系统化为方案，再带回去对齐与检验，循环改进。当多方意见分歧、需要汇总零散反馈、方案要拿回给真实使用者确认、或你发觉自己在闭门造车时触发；信息源单一且完整、处于执行阶段时不触发。 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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.