Tools

Tools

Small instruments that apply Koòrdinated Thinking with what exists today, before the application does it natively. They are useful on their own and are not prototypes of it.

They live in tools/ and are licensed Apache 2.0.

The Claude skill

Available in both languages: Italian · English. They are the same instrument, each carrying its own language's reference files.

The method stated as instructions for an agent rather than as a discursive document. Install it by placing the directory where the client looks for skills.

It governs the drafting phase, and what it changes is the shape of the exchange:

• it opens a project by drawing out the general purpose, deriving verifiable objectives, proposing the actors and declaring the discipline, then writing v0.1 with the annexes already in place — what is undecided becomes an open point rather than silence;
• each iteration runs four phases: analysis, numbered consolidation questions each carrying a reasoned recommendation, contestation by the Critic, then drafting;
• it proposes drafting when a threshold is reached — two unrecorded decisions, an open point at risk of being lost, a contradiction with an earlier decision, a change of theme — instead of rewriting the document at every exchange or waiting to be asked;
• it enforces additivity literally. Replacing a section with "unchanged from v0.3", tabulating only the new decisions, or abbreviating the change log are named as prohibited, because each is a way of losing content while appearing not to.

The document it maintains has a fixed structure: purpose and nature of the document, actors, discipline, general purpose, objectives, descriptive chapters, then annexes A–F — open points, decision log, glossary, references, change log, parent and sub-specifications.

Three reference files ship with it. Two are readable on their own as a description of how the method is practised: references/document-template.md, the document model with all its annexes, and references/actors.md, the operational definition of the actors and the Critic's intervention formulas.

The third is the method document itself, carried as the skill's rationale layer: the skill prescribes, the document explains and justifies. The skill states the precedence — where the two appear to conflict SKILL.md prevails, and a divergence is flagged to the operator rather than resolved by amending either one. It also states when to read it, rather than loading it every session: when the operator asks what the method is or why it works, when a choice needs the reason behind a rule, when the fit of the method to an unusual problem has to be judged, or when an exact term or citable source is needed.

That copy is kept byte-identical to the source in the repository by check-version.sh, and stays under CC BY 4.0 rather than Apache 2.0: content does not change licence by being copied next to code.

One environment-specific detail when adapting it: drafting output is written to /mnt/user-data/outputs/, a claude.ai path. Elsewhere it needs changing.

Repository scripts

tools/scripts/ — POSIX shell, no dependency to install.

Script	What it enforces
check-version.sh	The Markdown source and every HTML rendering must declare the same version. It compares the declared version, not the texts — only a person can do that
check-selfcontained.sh	No published page may load anything from the network, and each must carry its Content-Security-Policy. Hyperlinks in the text are not resource loads and are deliberately untouched

Both run in CI on every change under method/.

The second one is worth a note beyond its function. The renderings carry their typefaces embedded and make no external request, so no reader's address is disclosed to a third party for the sake of a font. That property is held in place by two mechanisms rather than by good intentions: a Content-Security-Policy inside each document, which makes the browser block a remote resource added by mistake, and this check, which catches it earlier, at push time, where it is cheap to fix.