sententia

Verify task completion status against fresh verification command evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Milovan-Crowley/Consilium --skill sententia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sententia
Source: https://github.com/Milovan-Crowley/Consilium/tree/main/generated/claude/skills/sententia
Command: npx skills add https://github.com/Milovan-Crowley/Consilium --skill sententia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that any claim of completion or readiness is backed by fresh verification evidence, preventing dishonest assertions and unnecessary rework.

Core Features & Use Cases

  • Verify completion status only after running a defined verification command and reviewing the full output.
  • Apply to code changes, documentation updates, and task readiness across development workflows.
  • Use in PRs and releases to prevent premature claims and improve auditability.

Quick Start

Before declaring completion, run the verification command, review its full output, and report the evidence.

Frequently Asked Questions about sententia

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

FAQPage Schema
How do I verify task completion with evidence in a CI-CD pipeline?

Run the defined verification command and review its full output before declaring any task complete. Evidence-first verification prevents premature claims and unnecessary rework in software development workflows.

What is evidence-first completion in software testing?

Evidence-first completion requires confirming task readiness only after running verification commands and reviewing fresh output. It ensures claims of readiness are backed by proof rather than assumptions.

How do I prevent premature completion claims in pull requests?

Prevent premature claims by running the full verification command, inspecting all outputs, and confirming success only when evidence supports the claim. This improves auditability and prevents dishonest assertions in PRs and releases.

Does evidence-based verification work for documentation updates and code changes?

Yes, evidence-based verification applies to code changes, documentation updates, and task readiness across development workflows. It requires running verification commands and confirming success based on fresh output evidence.

What's the best way to enforce quality assurance claims before a release?

Enforce quality assurance by requiring fresh verification evidence before allowing completion claims. Run the full verification command, inspect all outputs, and confirm success only when the evidence supports release readiness.

Why does task verification fail without fresh output evidence?

Task verification fails without fresh evidence because claims are not backed by recent proof. Running verification commands and inspecting full outputs ensures completion status is honest and prevents unnecessary rework.