「ownership」の検索結果

Generates structured U.S. art law summaries with Bluebook citations, doctrinal analysis, and stakeholder guidance. Use when researching art law precedents, advising on art transactions, preparing for art market litigation, or surveying a doctrine or statute across ownership, provenance, copyright, VARA, NAGPRA, authentication, NFTs, or AI-generated art.

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

Produces litigation-grade case summaries for animal law disputes including cruelty/neglect prosecutions, ownership/custody, dangerous animal designations, veterinary malpractice, and service/assistance animal accommodations. Builds exhibit-cited factual timelines, maps evidence to statutory elements, evaluates expert evidence, and assesses remedies with jurisdiction-specific legal research. Use when summarizing animal law cases, analyzing animal cruelty charges, pet custody disputes, dangerous dog hearings, veterinary malpractice claims, or assistance animal accommodation matters. Also trigger for animal forfeiture, bite liability, wildlife possession, or animal-related court filings.

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

Drafts adverse possession complaints and quiet title pleadings. Structures jurisdictional foundations, legal property descriptions, and element-by-element proof of actual, open, continuous, exclusive, and hostile possession. Use when filing adverse possession claims, quiet title actions, or prescriptive ownership pleadings.

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

Set up a parallel agent team for COMPLEX tasks: creates worktree structure, an ownership map, and an initialized task queue. Use when a task is decomposed into parallel subtasks.

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

Inspect scoped Autodesk data, compare versioned BOMs, and prepare ownership-aware drafts or approved custom-property changes. Not for implicit PLM release, membership changes or CAD geometry editing.

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

Agile product ownership toolkit for Senior Product Owner including INVEST-compliant user story generation, sprint planning, backlog management, and velocity tracking. Use for story writing, sprint planning, stakeholder communication, and agile ceremonies.

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

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use when writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing the backlog.

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

Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows.

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

Kit de ferramentas de product ownership ágil para Senior Product Owner, incluindo geração de histórias de usuário compatíveis com INVEST, planejamento de sprints, gerenciamento de backlog e rastreamento de velocidade. Use para escrita de histórias, planejamento de sprints, comunicação com stakeholders e cerimônias ágeis.

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

Divides records into geographic or account-ownership territories. Use when the user provides records with location or account data and wants consistent territory assignments with unresolved locations flagged.

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

Establish or audit a structural quality contract for any agent-operated engineering repository: app, library, CLI/tool, plugin, harness, or meta repo. Use when a repo needs charter clarity, docs/decision ownership, type-native validation gates, evidence paths, safe action policy, cold-start legibility, maturity proof, repair-loop routing, consumer/producer owner-boundary routing, command surface evolution, evolutionary simplicity (see references/evolutionary-simplicity.md), or a repo ecology pass to decide what should be compressed, merged, removed, updated, created, retired, or moved to checks.

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

Upgrade or synchronize Agent Skills, or determine a Skill's source and ownership across runtimes and roots. Use only for those lifecycle decisions. Do not use for installation, creation or editing, validation, inventory, usage statistics, general audits, cleanup, packaging, publishing, or ordinary file and package work.

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

GStack document generation method for turning implementation, product, or operational work into durable docs with clear audience and ownership.

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

Create and integrate the machine-level core of a new EMULATORS emulator, including Computer and Emulator derivatives, memory and port maps, chip ownership and wiring, clock coordination, model configuration, commands, formatters, executables, and Visual Studio projects. Use when scaffolding a machine namespace, adding a model or regional variant, assembling existing components into a computer, or making a new emulator build and start.

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

Audit and harden Convex authorization: identity-from-arg impersonation, missing per-document ownership checks, PII-leaking public queries, and writes into containers the caller doesn't own. Deterministic scan + canonical requireIdentity/requireOwner fix + tsc verify. Use for 'secure my app' / 'audit auth' / 'who can access this data', not generic code review.

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

Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.

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

Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.

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

Audit and harden a Convex app's authorization: identity-from-arg impersonation, missing per-document ownership checks, public queries leaking data by a client-supplied id, and writes into a parent/container the caller doesn't own. Scans for the 4 shapes, applies requireIdentity/requireOwner, verifies with tsc. TRIGGER on 'secure my app', 'audit auth/authz', 'who can access this data'. SKIP when there is no convex/ directory.

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

Agile product ownership for backlog management and sprint execution. Covers user story writing, acceptance criteria, sprint planning, and velocity tracking. Use for writing user stories, creating acceptance criteria, planning sprints, estimating story points, breaking down epics, or prioritizing ...

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

Review framework vs host ownership for permissions, approvals, grants, native execution, storage, daemons, and Clawix integration.

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

Work from a registered surface or transverse route by inspecting nodes, neighbors, edges, contracts, owners, tests, and gaps before editing.

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

Knowledge base from the Expanded Guidance for NASA Systems Engineering (NASA/SP-2016-6105-SUPPL, Volume 1, March 2016) — the practitioner-depth supplement to the NASA SE Handbook. Use for the load-bearing mechanics the handbook compresses: the SE Engine's per-phase cadence and the iterative-vs-recursive distinction, the AS9100 crosswalk, life-cycle tailoring vs. customization and the Compliance Matrix, the recursive system-design consistency loop (ConOps vs. Operations Concept, requirement flow/type/ownership, successive refinement), product realization (verify/qualify/accept/certify cardinality, protoflight, 'test the way we fly' coverage, two-form transition), and the crosscutting technical-management procedures (six-step scheduling, cost-estimating method selection, JCL, interface document family, RIDM/CRM, CM baselines, EVM arithmetic, MOE/MOP/KPP/TPM, the three required leading indicators, and the decision-analysis method catalog). This is the DEPTH layer — it deliberately does NOT restate the base definitions; pair it with the nasa-se-handbook pack. Scope: NASA space-flight SE practice (Vol 1 Practices); thin on the Vol 2 process-appendix detail, on non-NASA/commercial life cycles, and on software-engineering methodology.

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

Reads a risk register together with meeting notes and incident reports and returns a draft update pack: existing risks whose exposure, controls, ownership or status the sources say have changed, new risk candidates, closure candidates, and the one owner decision each item needs. Never assigns or changes a likelihood, impact, score or colour and never edits the register; owners decide. Use when the user asks to "update the risk register from these minutes", "refresh the register with the incidents since the last review", "reconcile the register against the notes" or "what changed on our risks". Do not use for writing up an incident itself, use incident-postmortem-drafter or data-incident-impact-brief instead; to track actions from minutes, use corrective-action-tracker. 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.

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