reckon

Reason from first principles to establish truth and needs in complex problems.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/tesserine/groundwork --skill reckon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reckon
Source: https://github.com/tesserine/groundwork/tree/main/skills/reckon
Command: npx skills add https://github.com/tesserine/groundwork --skill reckon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

First-principles cognitive discipline — position and reasoning as one act. Use when creating specs, architectures, processes, solutions, or methodologies. Use when analyzing costs, structures, strategies, or decisions. Use when reframing problems. Use before accepting any frame, cost, constraint, or convention without verification. Establishes what is actually needed and what is true (position), then reasons forward from verified constraints and navigational principles with every inference earning its chain (momentum). Dead reckoning: advance from an established fix using trusted constants.

Core Features & Use Cases

  • Positioning and grounded reasoning: orient, decompose, verify, reconstruct, compare, and default to the reckoned design to ensure traceability.
  • Traceability of inferences: every inference links back to a ground or principle, preventing drift.
  • Use Case: define specs, architectures, processes, or strategies with defensible reasoning and documentation.

Quick Start

Orient the problem, decompose constraints, verify them, reconstruct a solution, and trace every inference to ground or principle.

Frequently Asked Questions about reckon

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

FAQPage Schema
How do I reason from first principles to create defensible software architectures?

First-principles reasoning decomposes a problem into verified ground truths and constraints, reconstructing an architecture through explicit, traceable inferences to prevent logical drift and ensure defensible design.

What is the best way to establish ground truth when framing complex software engineering problems?

Establish ground truth by orienting the problem, verifying every constraint, and reconstructing solutions using trusted constants, ensuring every inference links back to a verified principle or ground fact.

How do I ensure traceability of inferences when defining project specs and methodologies?

Traceability of inferences is enforced by linking every reasoning step back to a verified ground truth or navigational principle, preventing undocumented assumptions from entering your specs and methodologies.

When do I need first-principles reasoning for cost analysis and decision-making?

You need first-principles reasoning for cost analysis and decision-making when reframing complex problems or verifying constraints, ensuring your conclusions are built on verified facts rather than unchallenged conventions.

Can I use grounded reasoning to challenge existing technical constraints and conventions?

Grounded reasoning is designed to verify constraints and challenge conventions by decomposing them into foundational truths, allowing you to reject any frame or limitation that cannot be verified against ground reality.

Does this methodology work for both software architecture and general problem framing?

This methodology applies across software architecture, cost analysis, and problem framing by establishing what is actually needed, then reasoning forward from verified constraints to produce a complete ground-to-conclusion chain.