「returns」の検索結果

Pre-tests one message (email, announcement, intranet post, town hall script, customer notice or slide) against two to six role personas the user supplies and returns a DRAFT panel report: each persona's likely first reaction, objections, unanswered questions, misreadings and what they would do next, every point tied to the passage that triggers it, plus suggested edits that add no fact the message does not already hold. Use when the user asks to "pre-test this message", "how will the team read this", "run this past the personas", "what objections will this raise", "find the holes before I send" or "check this lands with managers and field staff". Do not use for an in-character review of a proposal or business case by one executive archetype, use the executive-review family (cfo-reviewer, frontline-skeptic-reviewer and siblings) instead; to write the message in the first place, use announcement-drafter. Drafts for human review; never approves, authorises or signs off.

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

Triages an incoming non-disclosure agreement against the organisation's written standard NDA positions and returns a DRAFT triage pack: a clause-by-clause deviations table with a severity band, a suggested response per clause quoted from the positions document, open questions and a governing-law flag, all for counsel to decide. Never gives legal advice or an acceptability call. Use when the user asks to "triage this NDA against our standard positions", "screen this confidentiality agreement before it goes to legal", "red-flag this mutual NDA", "first-pass the counterparty's NDA" or "is this NDA standard or does it need counsel". Do not use for a full review of an MSA, SOW, licence or any whole contract, use contract-review-pack instead; for one clause lined up across several documents, use clause-comparison-table. Drafts for human review; never approves, authorises or signs off.

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

Abstracts one contract into a key-terms table with clause references, compares each term against the user's playbook of standard positions, and returns a DRAFT contract review pack: deviations and issues, open questions and a reviewer checklist. Flags governing law and never gives legal advice or enforceability or acceptability calls. Use when the user asks to "review this contract", "abstract the key terms", "summarise this MSA", "pressure-test this SOW against our playbook" or to compare an agreement with their standard positions. Do not use for a first pass on a stand-alone NDA, use nda-triage instead, or for one clause lined up across several documents, use clause-comparison-table instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews one employee software request (tool, purpose, users, data handled, cost, urgency) against the approved-tools list and the policies the user provides and returns a draft review for the reviewer: match state on the list with the row quoted, approved tools the list itself describes as covering the same need, policy clauses that bear on the request with quoted text, questions for the requester and the reviewer, and one suggested decision with its basis. Never approves, procures, installs or adds a tool to the list. Use when the user asks to "review this software request", "is this tool on the approved list", "check this request against our software policy", "do we already have something approved that does this" or "prepare the decision note for this tool request". Do not use for a full vendor security assessment, use vendor-risk-screening-brief instead; for sorting mixed requests, use request-intake-triage. Drafts for human review; never approves, authorises or signs off.

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

Reads a purchase order extract (spreadsheet, CSV or pasted table) and returns a DRAFT question sheet for the buyer: possible split orders, round amounts, amounts just under an approval threshold, first-seen or near-duplicate vendors, duplicate orders and missing or self approvals, each a neutral question naming the PO numbers, never a finding. Use when the user asks to "review these purchase orders", "screen the PO log", "spot anomalies in this spend extract", "sanity-check the PO register" or "prepare buyer questions before the audit". Do not use for an expense claim or travel request checked against policy, use expense-policy-precheck instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews one SKILL.md against the format rules and returns a findings table: strict YAML front matter with exactly name and description, name equal to the folder, description as the trigger, the eight-heading skeleton, capability-neutral wording, safety boundaries. Each finding carries severity, rule identifier, location, quoted evidence and replacement text; the verdict READY, REVISE or BLOCKED is an apparent state and the owner decides. Use when the user asks to "review this SKILL.md", "check my skill file before upload", "lint this skill description", "validate the front matter of this skill" or "score this skill folder". Do not use to write an agent's instructions field, use agent-instructions-drafter instead; for injection or leakage exposures use agent-instructions-red-team; for launch tests use agent-evaluation-plan. Drafts for human review; never approves, authorises or signs off.

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

Reviews a set of knowledge files or a knowledge base listing and returns a draft hygiene table, one row per file: duplication signals with the matching file, staleness signals, conflicts between files on the same topic with both passages quoted, missing or unverified owners, and one proposed action per file (Keep, Update, Merge into, Retire, Assign owner, Confirm with owner) for the owner to decide. Never edits, merges, moves or deletes a file. Use when the user asks to "review our knowledge base for duplicates", "which KB articles are stale", "find conflicting articles", "which articles have no owner" or "run a hygiene check on these files". Do not use for review-date sweeps of a document library with owner reminders, use sharepoint-review-sweeper instead; for writing one article, use knowledge-article-drafter. Drafts for human review; never approves, authorises or signs off.

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

Prepares the contents of a dated backup of a custom skills folder and drafts a session journal entry, both for the user to save, so work can be resumed after a crash, a context loss or a skills wipe. Returns the copy action list, backup manifest, journal entry, resume summary and a restore plan whose steps the user confirms one by one and carries out. Use when the user asks to "back up my skills folder", "checkpoint this session", "write the session journal", "where did we leave off last time", "restore my skills from the last backup" or "take a safety copy before I edit this skill". Do not use for holding individual file changes for approval during ordinary work, use no-delete-guardrail instead. Drafts for human review; never approves, authorises or signs off.

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

Sweeps a SharePoint library listing (an export or a listing the agent can reach, with file name, link, review-date column and owner column) for documents past their review date and returns a dated DRAFT review sweep report (Overdue, Due soon, No review date, Summary) plus one ready-to-paste reminder per document owner for the user to send. Never changes metadata, sends a message or invents a document, date or owner. Use when the user asks to "find the documents past their review date", "run the review sweep on the policies library", "which documents are overdue for review", "audit the review dates in this library export" or "draft reminders to owners about stale documents". Do not use for duplicate, conflict and ownership checks across knowledge files, use knowledge-base-hygiene-review instead; for gaps in an engineering deliverables register, use master-document-register-check. Drafts for human review; never approves, authorises or signs off.

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

Drafts the instructions field of a declarative agent that orchestrates a set of custom skills, under a character cap (default 8,000), from the skills' names and descriptions: role and scope, one routing rule per skill, workflow order, gates written as workflow holds, global rules, output format and what the agent never does. Returns the text in a fenced block with its character count labelled counted or estimated, plus a skill inventory, routing table, gate table, rules trace and open questions for the owner. Use when the user asks to "write the instructions for my agent", "draft a system prompt that ties these skills together", "tighten these agent instructions to fit the cap", "how should the agent route between these skills" or "revise my agent's orchestration text". Do not use to review a single SKILL.md, use skill-file-reviewer instead. Drafts for human review; never approves, authorises or signs off.

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

Answers an employee's or manager's HR policy question strictly from the policy documents the user supplies or the agent can reach as knowledge: a DRAFT answer that quotes the governing clause with its document, version and clause reference, lists the conditions and exceptions the text states, returns UNKNOWN where the documents are silent and names the role to ask. Never invents a rule, fills a gap from general practice or decides an individual's case. Use when the user asks to check a policy, for example "what does the policy say about", "am I entitled to", "how many days of leave do I get", "what is the process for requesting", "does the handbook allow" or "which clause covers". Do not use for comparing two policy versions or briefing a change, use policy-change-briefing instead. Drafts for human review; never approves, authorises or signs off.

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

Builds a one-page meeting preparation brief from the calendar invite, recent mail threads with the attendees, chat messages and shared files: purpose, what each attendee likely wants, open threads, key files, talking points and risks. Returns it in the chat as a DRAFT Markdown document capped at 450 words. Use when the user asks to "prep me for my next meeting", "what do I need to know before the vendor call", "one-pager for tomorrow's steering meeting" or "brief me on my 2pm". Do not use for minutes or action items after a meeting, use meeting-minutes-writer or transcript-to-actions instead. Drafts for human review; never approves, authorises or signs off.

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

Reads two or more supplier, bid or tender responses against a requirements list and returns a DRAFT comparison pack: a requirement-by-supplier matrix, gaps per supplier, clarification questions and neutral observations, for an evaluation panel. Never scores, weights, ranks or recommends a winner; the award stays with the panel. Use when the user asks to "compare these bids", "matrix the tender responses against our requirements", "collate the RFQ replies", "show me where each supplier falls short" or "draft clarification questions for the bidders". Do not use for scoring or weighting against agreed criteria, use supplier-evaluation-matrix instead, or for writing the requirements, use rfp-requirements-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews the instructions text and skills of a declarative agent, with its stated capabilities, knowledge sources and audience, for prompt-injection exposure, data-leakage paths, over-broad permissions and missing refusals, and returns an attack-surface map, a findings table with severity, quoted evidence and attack path, one pasteable fix per finding, a probe pack the owner can run and a refusal-coverage table. Use when the user asks to "red-team this agent", "check these instructions for prompt injection", "could this agent leak data", "review the permissions on my agent" or "what should this agent refuse". Do not use for checking a SKILL.md against the format rules, use skill-file-reviewer instead; do not use for designing the launch test set, use agent-evaluation-plan instead. Drafts for human review; never approves, authorises or signs off.

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

Reads a contract list (spreadsheet, CSV or pasted table) and returns a DRAFT renewal radar: each active contract's end date, notice deadline with its arithmetic, days remaining, renewal type, owner and the decision it needs as options, sorted by urgency, with owner action lists and a deadline calendar. Never renews, terminates, serves notice or recommends. Use when the user asks to "build a renewal tracker", "tell me what comes up for renewal", "work out when notice is due", "show me which contracts auto-renew" or "run the quarterly contract review". Do not use for reviewing one contract's full text or clauses, use contract-review-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Checks an extracted PFD register as a process model and returns findings and unknowns only: connectivity closure, stream numbering, presence of design conditions, equipment duty text, phase and service labels, package and off-sheet scope, boundaries, operating cases, and agreement between the drawing and attached process documents, then holds at gate G2. Creates no design values. Use when the user asks to "check the process model", "verify connectivity" or "is the PFD ready for enrichment" after gate G1 and before enrichment. Do not use for extraction from the drawing, use pfd-intake-and-extraction instead; do not use to propose lines or instruments, use piping-enrichment. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or vendor contract in character as a Head of Procurement archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, commercial risks, what would change the verdict and five interrogation questions. Use when the user asks to "review this from a procurement angle", "what would procurement say about this proposal", "pressure-test this vendor contract commercially", "find the holes before the sourcing committee" or "check the renewal terms like a Head of Procurement would". Do not use for liability, IP, regulatory or signing-authority questions, use general-counsel-reviewer instead; for whether the spend fits the budget, use cfo-reviewer; for vendor security, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reads a project or processing description and returns a DRAFT data protection impact assessment pack: processing description, necessity and proportionality questions, a risk table with blank rating cells, mitigations to consider and open questions. Never rates risk, determines the lawful basis or judges adequacy; the DPO assesses and signs. Works from descriptions, never personal data. Use when the user asks to "start a DPIA for the new monitoring tool", "draft a data protection impact assessment", "scaffold a DPIA from this processing description" or "what would the DPO need for a DPIA on this". Do not use for redacting or de-identifying a document, use document-deidentification-pass instead; do not use for working out what data an incident exposed, use data-incident-impact-brief instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as an Investor archetype and returns a DRAFT review in the chat with a verdict whose conditions read as terms, findings that cite the exact passage, capital-allocation risks, what would change the verdict and five interrogation questions. Use when the user asks to "run an investor review", "what would an investor say about this", "pressure-test the capital case" or "prepare me for the investment committee". Do not use for internal budget, cost or finance-function review, use cfo-reviewer instead; for revenue forecast and pipeline, use cro-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Chief Financial Officer archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, finance risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a CFO review", "pressure-test the numbers in this business case", "what would a CFO say about this", "challenge the payback and run costs" or "prepare this for the investment committee". Do not use for delivery or capacity questions, use coo-reviewer instead; for architecture or vendor questions, use cto-reviewer; for positioning or demand, use cmo-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Checks a master document register extract for gaps and returns a DRAFT question list for document control: missing or out-of-sequence revisions, overdue or slipping deliverables, numbering that breaks the project convention, duplicates and incomplete rows, each with row, test and quoted evidence. Never edits the register, re-baselines a date or marks a deliverable complete. Use when the user asks to "check the MDR", "find the gaps in the deliverables list" or "prepare questions on the drawing register". Do not use for drafting a transmittal from a document list, use transmittal-drafter instead. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck, plan or contract summary in character as a General Counsel archetype and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage or clause, legal risks, what would change the verdict and five interrogation questions. Meeting preparation, not legal advice. Use when the user asks to "run a general counsel review", "what would legal say about this", "pressure-test the legal exposure in this deal" or "prepare me for the deal committee". Do not use for price, term, renewal or vendor leverage, use procurement-reviewer instead; for lawful basis and data flows, use cdo-reviewer; for security controls, use ciso-reviewer. Drafts for human review; never approves, authorises or signs off.

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

Reads a process flow diagram (image, PDF or native export) with its job header and returns a provenance-tagged extraction register: equipment, streams, tags, connectivity, instruments already shown, notes and legends, connectivity findings and an explicit UNKNOWN list, then holds at gate G1. Extracts and records only; never enriches, tags or proposes. Use when the user asks to "start a PFD to P&ID job", "read in the attached PFD", "extract the equipment and streams from this PFD" or "read this PFD into a register". Do not use for checking the model, use process-model-check instead; do not use to propose lines, instruments or tags, use piping-enrichment or instrumentation-and-control-enrichment after gate G2. Drafts for human review; never approves, authorises or signs off.

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

Reviews a proposal, business case, deck or plan in character as a Customer Advocate archetype, the seat for paying customers not in the room, and returns a DRAFT review in the chat with a verdict, findings that cite the exact passage, customer-side risks, what would change the verdict and five interrogation questions. Use when the user asks to "run a customer advocate review", "do a voice-of-the-customer pressure-test", "what would our customers say about this" or "what does this plan really ask of paying customers". Do not use for the product evidence or roadmap case, use cpo-reviewer instead; for revenue or pricing strategy, use cro-reviewer; for the staff who operate the change, use frontline-skeptic-reviewer. Drafts for human review; never approves, authorises or signs off.

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