「fts」の検索結果

Builds a DRAFT weighted supplier evaluation matrix from supplier responses and the panel's agreed criteria, weights and scale: a provisional score per cell with the quoted evidence and anchor behind it, a register of every missing or partial answer, and calibration and sensitivity flags. Provisional for panel moderation; never recommends, awards or disqualifies. Use when the user asks to score, weight or rank supplier, bid or tender responses against agreed criteria, for example "score these bids", "build the evaluation matrix", "weight the tender responses" or "rank the suppliers against our criteria". Do not use for a side-by-side comparison without scores, use rfp-comparison-pack instead; for writing the criteria, use rfp-requirements-pack instead. Drafts for human review; never approves, authorises or signs off.

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

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.

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

Builds and maintains a DRAFT impact log from notes, messages, status updates and completed work: one row per outcome with its evidence and evidence level, date, who benefited and the source it traces to, plus a gap list of outcomes that still lack evidence, structured so a later review, appraisal or promotion case can draw on it. Use when the user asks to "start an impact log", "add this to my impact log", "log what I achieved this quarter", "pull my wins out of these notes", "turn these messages into evidence for my review" or "what do I have evidence for so far". Do not use for a performance rating, ranking, pay or promotion decision, the skill records evidence and never judges it; for the review narrative itself, use performance-review-drafter; for a role profile built from the work, use job-description-drafter instead. 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.

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

Turns a campaign idea, its objectives and the supporting notes (audience material, offer facts, budget and dates, channel list) into one DRAFT one-page campaign brief: objectives, audience, one single-minded message with sourced proof points, channels and timeline, success measures with baselines, mandatories, risks and numbered open questions for the campaign owner. Use when the user asks to "write a campaign brief", "draft a creative brief for this launch", "turn this idea into a one-page brief", "tighten this brief to one page" or "build the marketing brief from these notes". Do not use for a message house, messaging pillars or a launch narrative on its own, use message-house-builder instead; for laying the campaign onto dated slots, use content-calendar-planner. 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.

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

Turns the text of a regulatory change (new regulation, amendment, rule, guidance or standard revision) into a DRAFT impact note: what changed against the prior text where supplied, who is affected as the text scopes it, an obligations table with dates and owners to confirm, and open interpretation questions for legal. States only what the text says; the rest is UNKNOWN. Use when the user asks to "brief legal on this new regulation", "list what we must do by when under this amendment", "compare the new standard with the version it replaces", "turn this directive into an obligations table" or "what does this rule mean for us". Do not use for assessing existing controls against a requirement set, use controls-gap-pack instead; for gapping a policy against a standard, use policy-gap-review. Drafts for human review; never approves, authorises or signs off.

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

Turns one meeting transcript or recap into a DRAFT action-items document (decisions, owned and dated action items with verbatim source quotes, open questions), a task list ready for the user to enter into their task tracker, and one DRAFT follow-up email per action owner, all returned in the chat for the user to store, create or send. Use when the user shares, names or points to a meeting transcript or recap and asks to "pull the action items from this transcript", "who owns what after today's call", "draft follow-up emails to each owner" or "turn this recap into tasks". Do not use for full minutes, use meeting-minutes-writer instead; a brief before a meeting is meeting-prep-onepager. 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.

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

Builds a DRAFT quiz from the training content the user supplies (slide deck, manual, e-learning script, session transcript, procedure): numbered questions with the correct answer, distractors drawn from the content itself, an explanation quoting the source passage with its location, a difficulty tag (Recall, Apply, Analyse) with its basis, and a coverage table showing which sections and objectives each question tests and which are left uncovered. Use when the user asks to "build a quiz from this deck", "write knowledge check questions for this module", "create an assessment from this training", "test understanding of this procedure" or "which sections does this quiz cover". Do not use for a reader-facing question and answer page built from documents, use faq-builder instead; for writing the procedure itself from notes or a walkthrough, use sop-drafter. Drafts for human review; never approves, authorises or signs off.

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

Synthesises training survey responses and manager notes into a DRAFT training needs report by role: coded needs with record counts per role (n of N), the evidence type behind each count, anonymised quotes cited to record codes, disagreements between what staff report and what managers observe, gaps where a role is under-represented or a required skill has no evidence, and follow-up questions to settle before any course is designed. Never rates an individual, ranks a team or turns a count into a competence verdict. Use when the user asks to "analyse this training survey", "what training do our teams need", "summarise the manager feedback on skills gaps", "build a training needs analysis by role" or "which roles have the biggest skill gaps". Do not use for turning an agreed need into a course, use course-outline-builder instead; for exit interviews, use exit-interview-synthesis. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT course outline from a training need and audience: learning objectives with an observable verb, condition and standard, modules in a stated order with a duration basis and sources, activities and an assessment plan aligned objective by objective, and a coverage table showing what each objective still lacks. Never sets a pass mark, declares learners competent or invents content. Use when the user asks to "build a course outline", "design a training programme for", "turn this need into modules and objectives", "draft the curriculum for this workshop" or "what should this training cover". Do not use for quiz items from finished content, use training-quiz-builder instead; for needs from surveys and manager notes, use training-needs-synthesis; for a new starter's first weeks, use onboarding-plan-builder. 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.

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

Builds a DRAFT month-end, quarter-end or year-end close checklist and status table for a finance team from the close calendar, the open items list and last month's close issues that the user attaches, pastes or the agent can reach, marks every task on time, due, late, at risk or blocked, and flags dependency chains and repeat issues. Use when the user asks to "build the close checklist", "where are we on the month-end close", "what is late or blocked in the close", "refresh the close tracker as of today" or "prepare the close status note". Do not use for a project tracker or weekly project status, use project-status-tracker instead; for corrective actions from audits or NCRs, use corrective-action-tracker. Drafts for human review; never approves, authorises or signs off.

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

Turns an engineer's notes, a ticket history or a chat thread into a draft step-by-step runbook with preconditions, stop conditions, numbered steps with checks, verification, rollback and escalation, for the team to validate before use. Commands verbatim, placeholders marked, every gap UNKNOWN; never executes a step or fills a gap from general knowledge. Use when the user asks to "write a runbook from these notes", "turn this resolved ticket into a runbook", "document the steps we ran" or "check this runbook for gaps". Do not use for a business process without commands, use sop-drafter instead; for a knowledge article or known-error record, use knowledge-article-drafter; for the post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT content calendar for a stated period from the themes, channels, cadence rules, fixed dates and owners the user provides: one dated row per planned item with theme, channel, format, working title, owner, status and source, plus a cadence check with its arithmetic, theme balance, owner load and the slots left open. Use when the user asks to "build the content calendar for Q4", "lay these themes onto dates", "plan a month of posts across our channels", "extend the editorial calendar" or "check this calendar against our cadence". Do not use for deciding what the campaign says or why it runs, use campaign-brief-builder instead; for writing the items themselves, use announcement-drafter or internal-newsletter-drafter. 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.

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

Builds a DRAFT structured interview scorecard from a job description: five to eight competencies traced to it, past-behaviour and situational evidence questions with probes, four-level rating anchors written as observable behaviours, a blank scoring sheet, a panel plan and the items the hiring manager must confirm. Use when the user asks to "build an interview scorecard for this job description", "write competency questions for this role", "draft the interview guide for the panel", "set up a rating scale for the interviewers", "put together a structured interview kit" or "create a hiring rubric from the JD". Do not use for writing or fixing the job description itself, use job-description-drafter instead; for the new hire's first 90 days, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Prepares a change request pack (description and justification, scope, schedule, implementation plan, risk as stated, rollback, test evidence as provided, communications, approvals route) from an engineer's notes, ticket or pull request description, with UNKNOWN for anything not provided and a question list for the engineer. Never rates risk or marks a change tested or approved. Use when the user asks to "write the change request for this", "fill in the change ticket from my notes", "prepare the CAB submission" or "turn this pull request into an RFC". Do not use for the step-by-step procedure with commands and rollback, use runbook-drafter instead; for release notes describing what shipped, use release-notes-writer. Drafts for human review; never approves, authorises or signs off.

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

Produces a DRAFT 30-60-90 day onboarding plan for a new hire from the role, the team context and the systems list: phase outcomes traced to the role, activities with a named owner and due window, an access and equipment request table, learning items, manager checkpoints and the items the manager must confirm. Use when the user asks to "build an onboarding plan for our new hire", "draft the induction plan for this role", "write a first 90 days plan", "put together a new starter plan with owners", "create a ramp plan from this job description" or "plan the integration of an internal mover". Do not use for writing the job description itself, use job-description-drafter instead; for interview questions or a scorecard, use interview-scorecard-builder. 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.

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

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.

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

Turns plain-language requests (emails, chat messages, form submissions, meeting asks, voicemail or call notes) into one intake record per request (what is asked, who asks and for whom, urgency as evidenced, category, suggested owner, missing information with draft clarifying questions) and a triage table sorted for the operations lead to act on. Use when the user asks to "log these requests", "triage this pile of asks", "turn this message into an intake record", "who should own this request", "what is missing before we can start" or "build today's intake list". Do not use for customer support tickets, use ticket-triage-pack instead; for clearing a personal mailbox by reply bucket, use inbox-triage. Drafts for human review; never approves, authorises or signs off.

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