Web version
Free and installable. Its source is available under the FSL-1.1-ALv2 licence: you may read, change and use it, except to build a competing service. Your GitHub token stays in your browser, sealed by a passkey if the project requires it.
Your product’s specification, versioned like its code.
Skanon reads and writes a reference of business rules in your GitHub repository. The client reads it; the team evolves it through scopings reviewed in pull requests.
Three things, and the link between them
specification
What the product does today: domains, features, business rules. One text for the client and for the team.
scopings
What changes, and why: the goal, the user journey, each decision with the options set aside, the rules it touches.
history
The timeline of a rule, the specification as it stood on a past date, the functional diff of a scoping. What sets Skanon apart from a wiki.
Files you own.
One repository per project, Markdown files with YAML front matter. Skanon goes through the GitHub API, with no clone. History, authorship and review are the platform’s: the record outlives the tool.
A GitHub Action checks every scoping pull request — a rule with no statement, an impact pointing nowhere — and projects its rules into the specification on merge.
rules/RG-statuts-cadrage.md
---
id: RG-statuts-cadrage
fonctionnalites: [cycle-vie-cadrage]
statut: actif
cree_par: 2026-001
modifie_par: [2026-002, 2026-014, 2026-017,
2026-032, 2026-045]
---
A scoping goes through four states…Try Skanon
Desktop app
For macOS, Windows and Linux, under licence. The GitHub token in the system’s keychain, skanon: links that open a scoping in one click, and updates delivered to valid licences.