「methodology」の検索結果

RAID log methodology with decision extraction from emails and meeting notes. Use when asked to identify risks, log assumptions, track issues, extract decisions from correspondence, create or update a RAID log, escalate a risk to an issue, assess project risks, validate or challenge assumptions, or capture scope-relevant decisions. Also triggers when the user pastes email chains and asks what decisions were made, or needs to find buried decisions and untested assumptions in correspondence. Trigger on: 'risk report', 'RAID log', 'what are the risks', 'what decisions were made', 'update the risk register', 'what assumptions are we making', 'what could go wrong', 'flag any issues', 'extract decisions from these emails'.

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

Research, drafting, and analysis involving the International Criminal Court (Rome Statute system). Enforces a verification-first methodology — every case-law, decision, filing, warrant, and statement citation is verified against an authoritative primary source (icc-cpi.int, legal-tools.org) in the current conversation before it appears in an output. Foundational texts (Rome Statute, Elements of Crimes, RPE, Regulations of the Court) may be cited from project knowledge when present. Use whenever the user is working with ICC case law, OTP statements, ASP documents, or ICC procedure.

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

Elite incident response and legal compliance guidance for data breaches under GDPR Articles 33 & 34. Use when: (1) User reports a data breach or security incident — including "is this even a personal data breach?" triage, (2) User asks about breach notification obligations or deadlines, (3) User mentions "72 hours", Art. 33, Art. 34, or notification requirements, (4) Discussion involves security incidents affecting personal data, (5) User needs breach risk assessment using ENISA methodology, (6) User mentions "Data Breach" or "Incident" or "Data Leakage" or "Ransomware" or "Exfiltration", (7) User needs to determine Controller vs Processor obligations, (8) Cross-border breach scenarios requiring Lead SA determination, (9) User needs a mitigation playbook or immediate response recommendations, (10) User needs audit-ready breach documentation (.docx) or an EDPB-template-aligned breach notification / evidence file — including follow-up and withdrawal notifications, (11) Breach involves an AI system requiring AI Act Art. 73 serious incident screening.

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

AI co-counsel for divorce and family-law attorneys — a jurisdiction-portable scaffold spanning the full matter lifecycle. Eight operating modes mirror how a matter actually moves: intake and onboarding, financial disclosure, children and support, property division and QDRO, discovery and document review, drafting, negotiation and mediation prep, and court prep — plus post-judgment modification and enforcement. The methodology is jurisdiction-agnostic: it forces real, verifiable research for every local form, formula, or rule rather than inventing one, handling common-law, community-property, civil-law, and MENA personal-status regimes as variables. Built around one non-negotiable: privilege. It drafts, analyzes, organizes, and pressure-tests. It is not the lawyer.

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

Collaboration platform configuration methodology for legal matter sites. Site architecture, workflow identification, dashboard design, data quality governance, and user adoption for SharePoint, Teams, and equivalent platforms. M365 is the reference implementation — outputs are platform-agnostic enough to brief IT or build simple automations without becoming a Power Automate manual. Use when setting up a matter site, identifying workflows to automate, designing reporting dashboards, managing platform data quality, or driving user adoption. Trigger on: 'set up the matter site', 'configure SharePoint', 'build a dashboard', 'what should we automate', 'brief IT on this workflow', 'nobody is using the platform', 'data quality is poor', 'set up Teams channel', 'matter site structure', 'alerts and notifications', 'user training', 'platform governance', 'status dashboard', 'what workflows can we automate', 'matter site template'.

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

Argentine Supreme Court citation network analysis using JurisRank — a peer-reviewed PageRank algorithm with temporal decay for measuring jurisprudential authority. Ranks precedents by citation influence, traces doctrinal evolution, and detects constitutional drift. Published methodology: JCLLT (DOI: 10.47852/bonviewJCLLT62027951). Activate with: which cases to cite, rank precedents, case authority, doctrinal evolution, Argentine Supreme Court, CSJN jurisprudence, citation network, leading case, legal research Argentina.

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

When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian file-based, or manual mode). Async-first output. Six modes — setup (scaffold a new board for a business), triage (Eisenhower-sort the backlog), next (pick the next thing to work on, single board or across all), status (paste-ready async snapshot), unblock (diagnose Review/Blocked column), weekly (Friday pulse + week planning). Triggers on "/pm," "/pm setup," "/pm triage," "/pm next," "/pm status," "/pm unblock," "/pm weekly," "what should I work on next," "kanban status," "Eisenhower this," "triage my backlog," "what's blocked."

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

Apply STRIDE methodology to systematically identify threats. Use when analyzing system security, conducting threat modeling sessions, or creating security documentation.

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

Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.

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

Build a five-level rubric with coherent logic for a learning target within a developmental band. Use for Manning methodology programmes where Competent = success. For general curriculum rubrics, use criterion-referenced-rubric-generator instead.

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

Leveraged buyout model for A-share and China-market LBO scenarios. Adapts the standard LBO-model methodology for Chinese debt markets, CAS accounting, and AkShare data. Use instead of the original lbo-model skill when analyzing leveraged buyouts involving Chinese targets or China-based sponsors.

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

Three-statement financial model for A-share stocks. Adapts the standard 3-statement-model methodology for Chinese accounting standards (CAS), Chinese GAAP differences, and AkShare-sourced financials. Use instead of the original 3-statement-model skill when building integrated IS/BS/CF models for Chinese listed companies.

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

Generate SuperSigs (supervised mutational signatures) from single nucleotide variants in the cancer genome. Functions included in the package allow the user to learn supervised mutational signatures from their data and apply them to new data. The methodology is based on the one described in Afsari (2021, ELife).

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

Beta testing strategy for iOS/macOS apps. Covers TestFlight program setup, beta tester recruitment, feedback collection methodology, user interviews, signal-vs-noise interpretation, and go/no-go launch readiness decisions. Use when planning a beta, setting up TestFlight, collecting user feedback, or deciding if ready to launch.

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

April Dunford's 10-step positioning methodology for B2B tech products. Use when customers don't understand the product, sales cycles are long because reps must "explain it," prospects compare you to wrong competitors, or you face price pressure despite a good product. Covers competitive alternatives, unique attributes, value themes, target market characteristics, market category (Head to Head / Big Fish Small Pond / New Game), and trend layering.

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

Applies Neil Rackham's SPIN methodology (Situation/Problem/Implication/Need-payoff questions) to major B2B sales. Use for complex multi-call sales cycles, enterprise deals where the customer must justify the decision to others, when objections are mounting, when calls end in vague continuations instead of advances, when traditional closing techniques are backfiring on large deals, or when designing discovery-call structure. Triggers include 'my deal isn't closing', 'too many objections', 'B2B sales coaching', 'discovery call structure', 'stuck in the middle of the sale'. Not for transactional sub-$50 sales, pure consumer impulse, or PLG self-serve products.

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

Detailed review process, v2 validation checklist, and scoring methodology for agent definition reviews

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

Speculative parallel implementation methodology — dispatch N candidate implementations, audit all, score, pick best. Auditability mandate: ALL candidates logged (not just winner).

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

Advanced architecture stress analysis methodology for designing systems that survive unknown stresses. Load when --residuality flag is used or when designing high-uncertainty, mission-critical systems.

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

Deep knowledge for Outside-In TDD - double-loop architecture, ATDD integration, port-to-port testing, walking skeletons, and test doubles policy

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

Methodology for minimizing test count while maximizing behavioral coverage - behavior definition, anti-pattern catalog, consolidation patterns, stopping criterion, coverage-preserving validation

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

Source reputation tiers, cross-referencing methodology, bias detection, and citation format requirements

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

Teaches agents how to run a timeboxed spike - throwaway code that validates one assumption before DESIGN

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

Research output templates, distillation workflow, and quality standards for evidence-driven research

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