to-doc
Skill4 starsChanged 4 months agoApache-2.0View on GitHub
Create new Living Entity Wiki-classified non-ADR documents under docs/ using the classification, naming, placement, and Wiki rules defined by the repository schema.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- helderberto/agent-skillstheir own version, first seen Nov 1, 2026
- samuhs/mad-sciencetheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- helderberto/agent-skills★ 19same name
- samuhs/mad-science★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-remediationSkill
- attentionSkill
- classify-docSkill
- codebase-designSkill
- codebase-memory-mcpSkill
- codegraphSkill
- coding-standardsSkill
- contract-ledgerSkill
- conventional-commitsSkill
- database-migrationsSkill
- deduplicate-codeSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- format-codeSkill
- github-issue-dependenciesSkill
- graphifySkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implement-ticketSkill
- improve-codebase-architectureSkill
- project-delivery-managementSkill
- project-trackingSkill
- prototypeSkill
- repowiseSkill
- researchSkill
- resolving-merge-conflictsSkill
- review-architectureSkill
- review-specSkill
- setup-matt-pocock-skillsSkill
- spec-contractSkill
- spec-merge-cleanupSkill
- tddSkill
- teachSkill
- to-adr-docSkill
- to-specsSkill
- to-ticketsSkill
- triageSkill
- verify-architectureSkill
- verify-codeSkill
- verify-spec-closureSkill
- verify-specSkill
- verify-ticket-closureSkill
- verify-ticket-decompositionSkill
- wayfinderSkill
- wiki-lintSkill
- wiki-syncSkill
- wiki-synthesizeSkill
- writing-great-skillsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
32 rules. About 0 are common, 16 are distinctive, and 16 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈16
Distinctive · estimate
This author's own choices. Worth a look.
16
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 33
Use this skill only for a new non-ADR document inside the Living Entity Wiki document universe.
- Very specific: line 35
If the content warrants an ADR, use $to-adr-doc.
- Very specific: line 36
If the document already exists, use $classify-doc.
- Very specific: line 37
If the requested path is matched by docs/.wikiignore, it is outside this skill's ownership.
- Distinctive: line 38
Do not recreate an existing document merely to bypass reclassification or reference migration.
- Very specific: line 65
If current vs proposed is genuinely unclear, follow the schema fail-safe and use proposed.
- Very specific: line 69
Read docs/.wikiignore when present and apply only the exclusion grammar defined by wiki/_schema.md.
- Distinctive: line 71
If the requested path is explicitly excluded:
- Distinctive: line 73
do not classify it;
- Distinctive: line 74
do not apply Living Entity Wiki naming rules.
- Very specific: line 75
do not invoke $wiki-sync solely because it was created.
- Very specific: line 78
Do not infer exclusions for unfamiliar directories and do not invent new .wikiignore entries merely to make a requested path legal.
- Very specific: line 84
When an active wiki/index.md exists:
- Distinctive: line 86
use the owning Entity ID when the document primarily belongs to one entity.
- Very specific: line 87
use platform- only for genuinely cross-cutting documents.
- Very specific: line 88
do not entity/platform-prefix process documents.
- Very specific: line 90
Use wiki/index.md as the source of active Entity IDs.
- Distinctive: line 92
Do not invent new IDs.
- Distinctive: line 96
If no active entity registry exists yet, use:
- Distinctive: line 102
Do not invent entity prefixes before bootstrap.
- Distinctive: line 108
Use the canonical folder for its class:
- Distinctive: line 118
Create only the required directory if missing.
- Distinctive: line 120
Write the file directly at its canonical destination.
- Distinctive: line 124
create it temporarily at the repository root.
- Very specific: line 125
leave it loose under docs/.
- Distinctive: line 130
If the Living Entity Wiki has not been bootstrapped, no synchronization is required.
- Distinctive: line 140
Do not duplicate that evaluation here.
- Distinctive: line 144
Do not turn the index into a complete document inventory.
- Very specific: line 150
If document creation also causes wiki/index changes, keep those changes consistent with the caller's commit strategy and $wiki-sync's …
- Very specific: line 152
Do not create a separate commit merely because $to-doc or $wiki-sync ran.
- Very specific: line 169
create or manage documentation matched by docs/.wikiignore.
- Very specific: line 171
create or manage ADRs — use $to-adr-doc.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
To Doc
$to-doc owns creation-time placement and naming of new Living Entity Wiki-classified non-ADR documents under docs/.
Its responsibility is:
content
↓
classify
↓
name
↓
write
↓
sync when requiredClassification, naming, and the docs/.wikiignore exclusion boundary are owned by wiki/_schema.md.
For an existing classified document, use $classify-doc.
For an ADR, use $to-adr-doc.
1. Confirm Scope
Use this skill only for a new non-ADR document inside the Living Entity Wiki document universe.
- If the content warrants an ADR, use
$to-adr-doc. - If the document already exists, use
$classify-doc. - If the requested path is matched by
docs/.wikiignore, it is outside this skill's ownership; use the workflow or repository owner responsible for that documentation tree. - Do not recreate an existing document merely to bypass reclassification or reference migration.
2. Classify the Document
Apply the non-ADR classification rules in wiki/_schema.md.
Possible project-owned classes are:
current
proposed
research
reference
processClassification comes from folder placement.
Do not add:
doc_class:
Doc-Class:to the document.
If current vs proposed is genuinely unclear, follow the schema fail-safe and use proposed.
3. Respect the Wiki Exclusion Boundary
Read docs/.wikiignore when present and apply only the exclusion grammar defined by wiki/_schema.md.
If the requested path is explicitly excluded:
- do not classify it;
- do not apply Living Entity Wiki naming rules;
- do not invoke
$wiki-syncsolely because it was created; - route creation to the workflow or repository owner responsible for that documentation tree.
Do not infer exclusions for unfamiliar directories and do not invent new .wikiignore entries merely to make a requested path legal.
4. Name the Document
Apply the naming and cross-cutting-document rules in wiki/_schema.md.
When an active wiki/index.md exists:
- use the owning Entity ID when the document primarily belongs to one entity;
- use
platform-only for genuinely cross-cutting documents; - do not entity/platform-prefix
processdocuments.
Use wiki/index.md as the source of active Entity IDs.
Do not invent new IDs.
Before Wiki Bootstrap
If no active entity registry exists yet, use:
<slug>.mdDo not invent entity prefixes before bootstrap.
Later normalization belongs to $classify-doc.
5. Place and Write the Document
Use the canonical folder for its class:
current → docs/current/
proposed → docs/proposed/
research → docs/research/
reference → docs/reference/
process → docs/process/Create only the required directory if missing.
Write the file directly at its canonical destination.
Do not:
- create it temporarily at the repository root;
- leave it loose under
docs/; - duplicate classification or entity-registry metadata inside it.
6. Living Entity Wiki Follow-Through
If the Living Entity Wiki has not been bootstrapped, no synchronization is required.
Otherwise:
- new
currentdocuments → invoke$wiki-sync; - new
proposeddocuments → invoke$wiki-sync; - new
research,reference, orprocessdocuments → do not invoke$wiki-syncsolely because they were created.
Let $wiki-sync determine whether a current or proposed document contributes durable entity knowledge or exposes [source-conflict].
Do not duplicate that evaluation here.
For genuinely cross-cutting platform- documents, maintain any required discovery entry in wiki/index.md according to wiki/_schema.md.
Do not turn the index into a complete document inventory.
7. Commit Ownership
$to-doc does not require its own commit when called inside a parent workflow.
If document creation also causes wiki/index changes, keep those changes consistent with the caller's commit strategy and $wiki-sync's semantic logging rules.
Do not create a separate commit merely because $to-doc or $wiki-sync ran.
8. Report
Report:
- created path;
- classification;
- primary entity or
platformattribution where applicable; - whether
$wiki-syncran; - whether
wiki/index.mdchanged; - any
[source-conflict]or unresolved entity-boundary issue.
Out of Scope
$to-doc does not:
- create or manage documentation matched by
docs/.wikiignore; - modify or reclassify existing documents — use
$classify-doc; - create or manage ADRs — use
$to-adr-doc; - own classification, naming, or exclusion policy — see
wiki/_schema.md; - decide entity topology — use
$wiki-sync; - resolve
[source-conflict]; - maintain
linked_docs; - perform a full wiki audit — use the
$wiki-lintskill.
Its job is to ensure a new classified non-ADR document starts in the correct place, with the correct name, and the correct lifecycle follow-through.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

