A research aid for collecting and comparing court or administrative decisions on a legal question. It examines what each decision actually decided, where cases differ, and how far the sample can support a conclusion.
A guide for comparing European Union law, European Court of Human Rights case law, and other legal systems with Ukrainian needs. It identifies each source’s legal status, date, scope, and how it was implemented.
A formatting guide for turning already-approved legal-monitoring content into a DOCX or PDF report. It specifies a seven-section layout, blue labels, Times New Roman, footnotes, page numbers, and a final comparison table.
A structured review of how a law or regulation works in practice, from the public problem it addresses through its mechanism, implementation, results, and impact. It is intended for complex regulatory evaluation rather than a simple legal answer.
A setup process for a new legal matter or research assignment. It turns an unstructured request into a defined question, scope, data classification, plan, sources, deadline, and completion criteria.
A method for analyzing statistical, administrative, and financial data for legal questions. It defines measures, checks data quality and comparability, and separates correlation from proof of cause.
A data-safety checklist for removing sensitive information before material is searched, shared, or sent outside the project. It also records what was removed and whether approval is needed.
A way to preserve the important state of a coding session across branches, worktrees, and handoffs. A handoff is a short note that tells the next person what changed, what was checked, what remains, and what could block the work.
A source register and checking process that links each important piece of evidence to its origin, version, retrieval time, exact location, and handling conditions. Evidence provenance means being able to retrace a claim to the source material that supports it.
A research workflow for determining which Ukrainian laws and regulations applied on a specific date. It checks official wording, versions, effective dates, transitional rules, legal hierarchy, authority, and official sources.
Use when the user wants to turn repeatable office work into a workflow, script, or automation scenario and you need a proper spec before implementation.
Use when the task involves website, CRM, Notion, email, calendar, spreadsheets, or other business systems and you must plan the integration before writing it.
Use when the user needs a structured office document set such as a summary, proposal, listing packet, follow-up, meeting packet, or multi-part deliverable.
Use when the user brings a raw office request, fuzzy brief, or half-formed business idea that must be turned into a structured task before implementation starts.
Use before pushing, sharing, archiving, or exposing the project outside the local workspace so you can check for secrets, missing docs, and unsafe leftovers.
Use when the source material is a transcript, call notes, meeting text, or YouTube/video transcript and the user needs summary, actions, or reusable office outputs.
Use when the project has grown messy and you need to review skills, scripts, roles, registries, and process design to simplify the office operating contour.
Project instructions for an office-operations framework built around rules, roles, skills, scripts, templates, and workflows. They describe how to understand business work, automate repeatable tasks, and handle integrations safely.