t1k:docs
| Field | Value |
|---|---|
| Module | t1k-base |
| Version | 3.6.6 |
| Effort | low |
| Tools | — |
Keywords: documentation, generate docs, init docs, readme, summarize, update docs
How to invoke
Section titled “How to invoke”/t1k:docsinit|update|summarizeTheOneKit Docs — Documentation Management
Section titled “TheOneKit Docs — Documentation Management”Manage project documentation in docs/ directory.
Operations
Section titled “Operations”| Operation | Description |
|---|---|
init | Create project-appropriate doc structure |
update | Update docs after code changes |
summarize | Quick codebase summary |
Composable with any operation:
--advice— before writing or updating any doc, spawnt1k-kongmingfor counsel on what to keep, cut, or restructure, and factor it into the change. It advises only; this skill stays responsible for every edit and still confirms writes with the user. Spawn it again when stuck, or before an irreversible docs change (deleting a doc, restructuring the tree). Full contract:skills/t1k-cook/references/advisory-supervision.md.
Docs-specific note: the highest-value checkpoint here is before the first
write, not after — counsel on what to cut is worth more than counsel on prose
already written. This skill’s own scope rules still govern whether a doc should
be touched at all; --advice does not override them.
Doc Structure
Section titled “Doc Structure”docs/├── code-standards.md├── system-architecture.md├── project-changelog.md├── development-roadmap.md└── codebase-summary.mdAgent Routing
Section titled “Agent Routing”Follow protocol: skills/t1k-cook/references/routing-protocol.md
This command uses role: t1k-docs-manager
References
Section titled “References”references/init-workflow.mdreferences/update-workflow.mdreferences/summarize-workflow.md