Results for “document-signing”

UAT Sign-off

Sign build artifacts (binaries, packages, containers) with GPG, Sigstore, and platform-specific tools to ensure integrity and authenticity throughout the software supply chain.

在要求写结构化的 spec、规格文档、行为规格或验收标准时使用。

Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

Agents can sign plugins, rotate credentials without losing identity, and publicly attest to behavior.

Comprehensive legal document review specialist for contracts, litigation documents, and real estate agreements — summarizing documents, flagging risk clauses, comparing contract versions, and checking compliance across any law firm size or practice area

Bind pre-downloaded Jetson reference docs (developer guide, design guide, pinmux, schematics) into the active profile documents block. Use after staging docs on disk; not for downloading.

Author a new docs-native canonical or working document by choosing the correct location, filename, viewpoint template, metadata header, stable claims, and embedded rationale without creating spec.md.

Create, edit, and verify agent skills using test-driven development to ensure agents follow documented procedures correctly.

Write legal memoranda with analysis and conclusions. TRIGGERS - Use when user needs help with legal-memo related tasks.

Write memoranda of understanding for partnerships. TRIGGERS - Use when user needs help with mou-writer related tasks.

Use when creating new skills, editing existing skills, or verifying skills work before deployment

Draft a legal document — a pleading, motion, brief section, or contract clause — with verified citations, flagged assumptions, and mandatory supervisor review before filing.

Adversarial one-question-at-a-time questioning to verify deep reading comprehension of alignment pages, specs, or any document

用户要求基于技术交底书撰写或修改中国发明、实用新型专利申请文件，或者审查已有权利要求书时使用。典型触发包括“专利撰写”“专利申请”“技术交底书”“权利要求”“说明书”“实用新型”“发明专利”。专利检索、FTO/侵权分析、无效宣告、审查意见答复、商标或著作权是相邻业务：用户只提这些时不适用本流程；与撰写需求混在一起提出时，撰写照常进行，但最终回复必须对其中每一项其他诉求逐一说明处理情况——漏掉任何一项，这次交付就是不完整的。