Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Documentation-as-Source-of-Truth workflow. Use when working with projects that use docs/ as the canonical source for definitions, rules, and tasks. Routes to specialized sub-skills for specific documentation types.
Documentation-as-Source-of-Truth workflow. Use when working with projects that use docs/ as the canonical source for definitions, rules, and tasks. Routes to specialized sub-skills for specific documentation types.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Documentation is the database of decisions. Code is merely its implementation. โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ THE DOC-FIRST PRINCIPLE โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ 1. Documentation DEFINES what something IS โ โ 2. Code IMPLEMENTS what documentation specifies โ โ 3. Conflicts RESOLVE in favor of documentation โ โ โ โ If docs say X and code does Y โ CODE IS WRONG โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
Use ogt-docs when you need to: Understand the docs/ folder structure Find the right sub-skill for a specific task Initialize a new docs-first project Navigate between definition types For specific tasks, use the specialized sub-skills listed below.
docs/ โโโ definitions/ # WHAT things ARE โ โโโ business/ # Business model, pricing, users โ โโโ features/ # Product features and specs โ โโโ technical/ # Architecture, services, data โ โโโ domain/ # Domain-specific concepts โ โโโ rules/ # HOW to IMPLEMENT โ โโโ code/ # Coding standards โ โ โโโ frontend/ โ โ โโโ backend/ โ โ โโโ infra/ โ โโโ git/ # Version control rules โ โโโ domain/ # Domain-specific rules โ โโโ todo/ # TASK management โ โโโ pending/ # Not started โ โโโ in_progress/ # Being worked on โ โโโ review/ # Awaiting review โ โโโ blocked/ # Cannot proceed โ โโโ done/ # Completed & verified โ โโโ rejected/ # Declined tasks โ โโโ guides/ # HOW-TO documents โ โโโ {topic}/ โ โโโ social/ # Marketing & communications โโโ campaigns/ โโโ content/ โโโ branding/
Every documentable item is a folder containing: {item_slug}/ โโโ {type}.md # Primary document (task.md, feature.md, etc.) โโโ {supporting_files}.md # Additional documentation โโโ .{signal_files} # Status markers and metadata Benefits: Move entire folder between workflow stages Attach unlimited supporting files Signal status via dot-files Version and track changes atomically
Sub-SkillPurposeUse Whenogt-docs-defineGeneral definition guidanceNeed overview of definition typesogt-docs-define-businessBusiness model, pricing, usersDefining business conceptsogt-docs-define-featureProduct features and specsSpecifying a new featureogt-docs-define-codeTechnical architectureDefining services, data modelsogt-docs-define-marketingBrand, messaging, audienceMarketing definitionsogt-docs-define-brandingVisual identity, toneBrand guidelinesogt-docs-define-toolsTooling and CLI specsDefining developer tools
Sub-SkillPurposeUse Whenogt-docs-rulesGeneral rules guidanceNeed overview of rule typesogt-docs-rules-codeCoding standards overviewGeneral code rulesogt-docs-rules-code-frontFrontend-specific rulesReact, CSS, componentsogt-docs-rules-code-backBackend-specific rulesAPI, database, servicesogt-docs-rules-code-infraInfrastructure rulesDocker, CI/CD, deploymentogt-docs-rules-gitVersion control rulesCommits, branches, PRs
Sub-SkillPurposeUse Whenogt-docs-create-taskCreate and manage tasksNeed to create/update a taskogt-docs-audit-taskVerify task completionChecking if task is truly done
Sub-SkillPurposeUse Whenogt-docs-createGeneral creation guidanceNeed to create any doc typeogt-docs-create-socialMarketing contentCreating social/marketing contentogt-docs-auditGeneral audit guidanceAuditing documentationogt-docs-initInitialize docs structureSetting up new projectogt-docs-configConfiguration optionsCustomizing docs workflow
flowchart TB subgraph define ["1. DEFINE"] D1[Create Definition] D2[Get Approval] end subgraph regulate ["2. REGULATE"] R1[Create Rules] R2[Add Examples] end subgraph implement ["3. IMPLEMENT"] I1[Create Task] I2[Write Code] I3[Review] end subgraph verify ["4. VERIFY"] V1[Run Checks] V2[Confirm Match] end define --> regulate --> implement --> verify verify -->|Mismatch| implement verify -->|Docs Wrong| define
โ Use ogt-docs-define to understand types, then the specific sub-skill
โ Use ogt-docs-create-task
โ Use ogt-docs-audit-task
โ Use ogt-docs-rules-code or the specific frontend/backend/infra variant
โ Use ogt-docs-init
ElementFormatExampleFolder slugssnake_caseglobal_search, user_authPrimary fileslowercase typetask.md, feature.md, rule.mdSupporting fileslowercase descriptivephase_0.md, notes.md, progress.mdSignal filesdot + snake_case.blocked_reason, .approved_by_human
Signal files are dot-files that indicate status or metadata. SignalTypeMeaning.versionContentSchema/doc version (JSON).blockedEmptyItem is blocked.blocked_reasonContentWhy it's blocked.approvedEmptyApproved for implementation.approved_by_{name}EmptyWho approved.rejectedEmptyRejected.rejected_reasonContentWhy rejected.verifiedEmptyImplementation verified.completed_atContentCompletion timestamp.assigned_to_{agent}EmptyWho's working on it.pr_linkContentAssociated PR URL.depends_onContentDependencies list
If it's not documented, it doesn't exist If code contradicts docs, code is wrong Never trust "done" status without verification Move folders, don't copy files Signal with dot-files, don't edit status fields
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.