examinare

Orchestrates delegated, evidence-based tasks with scored, auditable workflows for codebase reviews and migrations.

Updated May 20, 2026
One-click install
npx skills add https://github.com/watmin/datamancy.dev --skill examinare
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: examinare
Source: https://github.com/watmin/datamancy.dev/tree/main/examinare
Command: npx skills add https://github.com/watmin/datamancy.dev --skill examinare

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Examinare orchestrates delegated, grounded work by weighing findings against the living disk, preventing unverified claims and ensuring transparency.

Core Features & Use Cases

  • Map the work into discrete strikes and designate executors
  • Write disconfirming probes and define STOP triggers to surface gaps early
  • Produce briefs, probes, and scores to create auditable, repeatable campaigns
  • Useful for reviews, migrations, builds, research sweeps, and governance-heavy workflows

Quick Start

Map the lair, write a disconfirming probe, and draft the strike brief before making any changes.

Frequently Asked Questions about examinare

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I ensure delegated code reviews are grounded against the live codebase?

Ensure delegated code reviews are grounded by mapping tasks into discrete strikes and weighing findings against the live codebase. This approach prevents unverified claims by requiring crawl-first planning and explicit briefs for auditable outcomes.

What is a disconfirming probe and when do I need it for a code migration?

A disconfirming probe surfaces gaps early by testing assumptions against the codebase. You need it for code migrations to define STOP triggers and produce auditable, repeatable campaigns with traceable outcomes.

How do I create an audit trail for delegated research sweeps?

Create an audit trail for delegated research sweeps by producing briefs, probes, and scores. This scoring mechanism ensures traceable outcomes by mapping work into strikes and designating executors for transparent, governance-heavy workflows.

Can I use a crawl-first planning approach for complex build verification?

Yes, you can use a crawl-first planning approach for complex build verification. By mapping the lair and drafting a strike brief before making changes, you ensure builds are evaluated with disconfirming probes for grounded decisions.

What is the best way to manage governance-heavy workflows with delegated work?

The best way to manage governance-heavy workflows with delegated work is to orchestrate campaigns using explicit briefs and a scoring mechanism. Weighing findings against the living disk ensures transparency and prevents unverified claims.