rationale

Construct hierarchical claim trees to structure code verification arguments.

5|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill rationale-nicholls-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rationale
Source: https://github.com/nicholls-inc/claude-code-marketplace/tree/main/crosscheck/skills/rationale
Command: npx skills add https://github.com/nicholls-inc/claude-code-marketplace --skill rationale-nicholls-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps developers or verification experts systematically construct and evaluate structured adequacy arguments for code, bridging formal and semi-formal verification methods.

Core Features & Use Cases

  • Hierarchical Claim Building: Decompose high-level adequacy claims into specific, verifiable subclaims.
  • Verification Strategy Assignment: Classify each subclaim with formal, behavioral, static, or semantic verification methods.
  • Verification Tracking: Generate test cases, formal specs, or evidence citations and track verification status for each subclaim.
  • Use Case: For a critical module, build an argument tree detailing formal proofs for core functions and tests for edge cases, providing traceability and confidence in correctness.

Quick Start

Use the rationale skill to analyze your function or module for structured verification by specifying the file path and a brief requirements description.

Frequently Asked Questions about rationale

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

FAQPage Schema
How do I build a structured verification argument for code correctness?

To construct a formal verification argument, decompose high-level adequacy claims into verifiable subclaims using a hierarchical claim tree. This bridges formal and semi-formal methods to systematically establish code correctness.

What is a claim tree in software safety assessments?

A claim tree is a hierarchical structure that decomposes top-level safety adequacy claims into specific subclaims. It assigns verification strategies like formal proofs or static analysis to traceably establish confidence.

How do I track verification status for subclaims during a code review?

Assign verification classification strategies like formal, behavioral, static, or semantic methods to each subclaim. Generate test cases, formal specs, or evidence citations to monitor and track verification completion.

Can I use formal methods alongside static analysis for module verification?

Yes, formal methods and static analysis can be combined. The verification strategy assignment classifies subclaims to utilize formal specs, tests, static analysis, and human judgment as integrated verification strategies.

Does this approach work for verifying edge cases in critical modules?

Yes, this approach works for critical modules by building an argument tree that details formal proofs for core functions and behavioral tests for edge cases, providing traceability and confidence in correctness.