The method as one self-contained file, with no packaging around it. One file per language:
koordinated-thinking-flatskill-it.md (24 KB) and
koordinated-thinking-flatskill-en.md (24 KB). Install the one
whose language you work in — the two are the same instrument, and which language is which is not
incidental; see Italian and English.
The other two packagings assume a platform: OpenAI/ needs a client that reads a skill directory,
OpenWebUI/ needs a skill store and native function calling. A FlatSkill assumes nothing. It is
Markdown with no front matter, no companion files and no references to a file system, so it goes
wherever an assistant will accept a block of instructions:
- a system prompt, or the instructions field of a project, a custom GPT, a Gem, an assistant;
- a file attached to a conversation, on a platform that reads attachments;
- the first message of a chat, on a platform that offers nothing else;
- an ordinary document, for a human being who wants to practise the method without a model at all.
It is also the form to start from when adapting the method to a platform not covered here: one file to read, with nothing resolved elsewhere.
Sections 1–4 are operational and are to be followed, 5 is the model to fill in, 6 and 7 serve for cases the procedure does not foresee and for answering questions about the method.
Everything is in context, always. There is no lazy loading here: the whole ~24 KB sits in the prompt for
the entire conversation, where the Claude skill pulls a reference file when it needs one and the Open
WebUI package pulls a companion skill with view_skill. On a small context, or where the prompt is
billed at every turn, that is the cost to weigh.
The rationale is condensed, not carried whole. Section 7 states the four pillars, the declared limits and what the method does not claim, in about a page; the other packagings ship the method document itself as their rationale layer, some 48 KB. Where section 7 and the published document appear to diverge, the file states the precedence: the procedure prevails, and the divergence is flagged to the operator.
There is no executable verification. The delivery checks rest on the model's judgement — true of the Open WebUI package too, and unavoidable in any packaging that is only prose.
Paste or attach the whole file. Nothing has to be edited first, and nothing outside it has to be
reachable. If the environment has a file system or a writing tool the procedure will use it, saving each
version as <project-name>-vX.Y.md; if it has neither, the document is delivered as a Markdown block in
the conversation and keeping it is then the operator's job — one note or one file per project,
replaced whole at each version, pasted back when resuming the work. The procedure asks for the
specification rather than reconstructing it from an earlier conversation, because a specification
rebuilt from memory is not a source of truth.
CC BY 4.0, SPDX CC-BY-4.0, like every skill in this
repository whatever it packages for. The notice is at the foot of each file, which matters more here
than anywhere else: a file meant to be pasted travels further from this directory than any other, and
has to say what it is on its own. Attribution text: ../../../method/ATTRIBUTION.md.
The authoritative map for the repository is ../../../LICENSING.md.