kesslernity

Drafts a nonconformance report from inspection notes, test results and the governing specification or procedure: what was observed, where, the evidence with references, the requirement cited quoted verbatim with the departure from it, and containment proposals for the quality lead to decide. Never classifies severity, dispositions the item, names a root cause or closes the report. Use when the user asks to "write up this nonconformance", "draft an NCR from my inspection notes", "formalise this deviation" or "turn this snag into a defect report". Do not use for tracking the actions an NCR raises, use corrective-action-tracker instead. Drafts for human review; never approves, authorises or signs off.

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

Summarises one sprint from the board export, sprint report and review or stand-up notes the user provides into a one-page DRAFT sprint review summary: the sprint goal as written, items delivered, items not delivered with the reasons the sources state, carry-over, impediments, metrics exactly as given, and numbered questions for the retrospective, every row referenced to a work item or note fragment and every missing fact marked UNKNOWN. Use when the user asks to "summarise the sprint", "write the sprint review", "what did we deliver this sprint", "list the carry-over and blockers" or "draft the sprint recap". Do not use for the retrospective write-up or themed lessons across several sprints, use lessons-learned-synthesis instead; for a weekly project status report, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.

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

Reviews the text and structure of a document, slide deck or web page against the accessibility rules the user supplies, or a default set covering heading structure, image alternative text, colour used as the only cue, link text, reading order, tables and language, and returns numbered findings with location, rule, severity and a ready-to-apply fix for the author, plus proposed alt text and a list of checks that need a tool or a person. Use when the user asks to "check this document for accessibility", "review the alt text in this deck", "is this page accessible", "run an accessibility check on these slides", "find accessibility issues before I publish" or "check my headings and link text". Do not use for brand or template compliance of slides, use branded-deck-builder instead. Drafts for human review; never approves, authorises or signs off.

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

Prepares the trend update for a recurring emailed report: identifies report emails not yet processed, extracts the configured metrics from their spreadsheet, CSV or PDF attachments, returns new rows for an append-only trends sheet and writes a DRAFT summary with period-on-period deltas and flagged anomalies. Use when the user asks to "update the trends for the weekly report", "analyse the latest monthly report", "what changed in the latest report", "do the latest numbers look unusual" or "set up tracking for a report that arrives by email". Do not use for a single file with no trend state, use dataset-insight-pack instead. Drafts for human review; never approves, authorises or signs off.

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

Produces a draft controls and gap pack from a requirement, regulation, standard or policy and the organisation's control descriptions: obligations broken out of the source text, the controls that appear to address each, apparent coverage, gaps, questions for control owners and actions to assess. Never concludes compliance or that a control is effective; owners and audit assess. Use when the user asks to "map this regulation to our controls", "run a controls gap analysis", "break this standard into obligations" or "where is our control coverage thin". Do not use for comparing a policy document against a standard, use policy-gap-review instead; to draft evidence requests from the mapped controls, use control-evidence-request-pack. Drafts for human review; never approves, authorises or signs off.

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

Reviews marketing, packaging, web or sustainability text against the environmental-claim rules the user supplies (house policy, regulator guidance extract, industry code) and returns a DRAFT claims review: every environmental claim quoted verbatim with location and family, the evidence the text or evidence pack offers for it with date and scope, the supplied rule passages that bear on each claim, observations as read, and separate question lists for legal and for marketing. No compliance, greenwashing or substantiation verdict. Use when the user asks to "review these green claims", "check this copy against our environmental claims policy", "what evidence do we have for carbon neutral here", "list the sustainability claims in this brochure" or "prepare questions for legal on this eco campaign". Do not use for mapping general factual claims to evidence, use claims-evidence-map instead. Drafts for human review; never approves, authorises or signs off.

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

Drafts an account plan from the CRM notes, emails, meeting notes and contracts the user provides: situation, stakeholder map, opportunities as recorded, risks, open commitments and proposed next actions, every line traced to a source and gaps marked UNKNOWN. Returns a DRAFT Markdown document in the chat. Use when the user asks to "build an account plan", "refresh the key account plan", "what do we know about this account", "account review for <customer>" or "what should happen next on this account". Do not use for preparing a first call with a prospect, use discovery-call-prep instead; for scoring inbound leads against a rubric use lead-qualification-scorer. Drafts for human review; never approves, authorises or signs off.

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

Converts a priced estimate spreadsheet into a DRAFT statement of work populated from the user's own SOW template, after checking that line items, hours, rates, subtotals and the grand total add up. Returns the populated SOW and a validation report as Markdown, flags every discrepancy and marks missing fields TBC. Use when the user asks to "turn this estimate into an SOW", "build the statement of work from the pricing workbook", "convert the quote into a scope document", "populate our SOW template from the estimate" or "draft the engagement document from the rate card". Do not use for reviewing or editing an existing SOW, use contract-review-pack instead; for a proposal before pricing is fixed use proposal-skeleton; for RFP or tender answers use rfp-response-drafter. Drafts for human review; never approves, authorises or signs off.

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

Builds a DRAFT proposal skeleton from a discovery summary (call notes, discovery brief, CRM record, emails) and the organisation's own proposal template: every template section in order, pre-filled only where the discovery material supports it with the source beside each line, and every section still needing a human input marked HUMAN INPUT with the owner role and the question to answer. Use when the user asks to "start the proposal for <prospect>", "build the proposal skeleton from the discovery notes", "pre-fill our proposal template", "what do we already have for the proposal" or "first cut of the proposal". Do not use for answering a formal RFP, RFQ or tender question set, use rfp-response-drafter instead; for turning a priced estimate into a statement of work use estimate-to-sow. Drafts for human review; never approves, authorises or signs off.

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

Pre-fills a customer's or prospect's security or third-party risk questionnaire from the organisation's own answer sources (prior questionnaires, answer library, policies), returning one row per question with a draft answer marked Reused, Adapted, Missing or Routed, its source, date, scope match and owner, plus the Missing list by owner. Never invents an answer, certification or control and never submits. Use when the user asks to "pre-fill this security questionnaire", "take a first pass at the customer's due diligence form", "answer this vendor assessment from our previous responses", "populate the third-party risk questionnaire" or "which questions can we reuse answers for". Do not use for screening a vendor's own answers, use vendor-risk-screening-brief instead; for RFP or tender answers use rfp-response-drafter. Drafts for human review; never approves, authorises or signs off.

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

Maintains four living project files (overview and progress log, decision log, RAID log, links) from the mail, channel posts, documents and meeting notes the user attaches or the agent can reach, returns each touched file complete in the chat for the user to save, and builds a weekly DRAFT status report from those files. Use when the user asks to "set up tracking for project X", "catch the project files up", "log this decision against the project", "add this risk to the RAID log", "save this link to the project" or "write this week's status report". Do not use for reviewing an existing RAID log for stale or ownerless entries, use raid-log-review instead; for an HTML status page, use project-dashboard-builder; for minutes of one meeting, use meeting-minutes-writer. Drafts for human review; never approves, authorises or signs off.

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

Drafts answers to the questions in a received RFP, RFQ or tender from the organisation's past responses, answer library, case studies, policies and other documents provided: one row per buyer question with a draft answer marked Reused, Adapted or Missing, its source and date, and a legal or pricing review flag on every answer touching terms, liability, warranties, insurance, data protection or price. Use when the user asks to "draft our RFP response", "answer this tender from our past proposals", "pre-fill the bid questions", "first pass at the RFQ answers" or "reuse our previous bid content". Do not use for writing the buyer's own RFP or requirements, use rfp-requirements-pack instead; for security or due diligence questionnaires use vendor-security-questionnaire-prefill; for scoring received supplier responses use rfp-comparison-pack. Drafts for human review; never approves, authorises or signs off.

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

Turns a control list and an audit scope into draft evidence requests grouped by control owner, each with the control as stated, the audit period, evidence examples (commonly requested) and a proposed due date derived from the fieldwork dates. Never judges whether evidence is sufficient, never selects the sample and never sends a request; the auditor decides. Use when the user asks to "prepare the evidence requests", "draft the PBC list", "build the evidence request pack for the audit" or "what do we need to ask each control owner for". Do not use for document requests and interview questions built from an audit plan, use audit-prep-pack instead; to check claims in a report against sources, use claims-evidence-map. 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.

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

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.

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

Builds a DRAFT change-communication plan from a change description: audience map, key messages per audience traced to the description, channels, sequence with dates or day offsets, owners, feedback loop and open questions, plus drafts of the first messages for the sponsor to approve. Use when the user asks to "plan the comms for this change", "who needs to hear about this and when", "draft the announcement sequence", "build a communication plan for the rollout", "write the first message to managers about this change" or "how do we tell people about this". Do not use for a clause-by-clause comparison of a changed HR policy with its previous version, use policy-change-briefing instead; for a new hire's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

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

Turns a business need and its constraints into a DRAFT RFP requirements pack: traced functional and non-functional requirements with priorities, mandatory gates, evaluation criteria with weights left to the business owner, and fact-seeking supplier questions. Solution-neutral; never names a supplier or product. Use when the user asks to "write the RFP requirements", "turn this business case into tender requirements", "draft the supplier questionnaire", "structure our RFQ from this brief" or "set up evaluation criteria before we go to market". Do not use for responses already received, use rfp-comparison-pack to compare them or supplier-evaluation-matrix to score them 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.

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

Turns process notes, a walkthrough or interview transcript, a transcript of a meeting recording or a stale existing procedure into a draft standard operating procedure: purpose and trigger, scope, definitions, roles with a RACI table, numbered steps with the check that closes each one, records produced, controls as stated, and open questions for the process owner. Every step traces to the source or reads UNKNOWN. Use when the user asks to "write an SOP from these notes", "turn this walkthrough into a procedure", "document how we do this", "draft the standard operating procedure for", "build a RACI for this process" or "tidy up this old procedure". Do not use for technical runbooks with commands and rollback, use runbook-drafter instead; for meeting minutes and action lists, use transcript-to-actions. Drafts for human review; never approves, authorises or signs off.

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

Applies a change-safety review to any requested file, mail or calendar change: lists every create, modify, move, rename, archive or delete before proposing it, marks destructive items as requiring the user's typed confirmation, proposes versioned file names instead of overwrites, declines to draft bulk destructive operations, and drafts a change journal entry for the user to keep. Use when the user asks to "clean up this folder", "delete the old versions", "reorganise these files", "archive everything older than a year", "rename and move these documents" or "make sure nothing gets overwritten while we work", or when any task is about to create or modify files, emails or calendar items. Do not use for backing up, journalling or restoring a skills folder, use skills-backup-keeper instead. Drafts for human review; never approves, authorises or signs off.

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

Synthesises exit interview notes or leaver survey responses into a DRAFT themed report: coded themes with record counts and shares, anonymised verbatim evidence, breakdowns by broad group only for groups that meet a minimum group size, referred items and open questions for the people team, without naming or identifying any individual. Use when the user asks to analyse, summarise, code, theme or report on exit interviews, leaver feedback, attrition interviews or departure surveys, or says "what are our leavers telling us", "theme these exit interviews" or "summarise the leaver survey". Do not use for customer or product feedback, use customer-feedback-theme-synthesis instead; for redacting one document with no theming, use document-deidentification-pass. 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.

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

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.

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

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.

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