ogt-docs
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.
Why use this skill?
Master the OGT-Docs workflow. Learn to use the Documentation-as-Source-of-Truth pattern to align your code, tasks, and project architecture using OpenClaw.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/eduardou24/ogt-docsWhat This Skill Does
The ogt-docs skill implements a 'Documentation-as-Source-of-Truth' (OGT) workflow for OpenClaw AI agents. It shifts the development paradigm so that the docs/ folder functions as the primary database of project intent. By formalizing the relationship between documentation and implementation, this skill ensures that code is always a secondary byproduct of validated specifications. It manages a strict hierarchical structure, utilizing the 'Folder-as-Entity' pattern where every feature, task, or rule is self-contained within its own directory.
Installation
To integrate this skill into your workflow, run the following command in your terminal:
clawhub install openclaw/skills/skills/eduardou24/ogt-docs
Ensure your project repository is initialized with a docs/ directory to fully leverage the indexing capabilities of this skill.
Use Cases
Use ogt-docs when working in complex, fast-paced environments where code drift often leads to technical debt. It is ideal for:
- Managing product feature requirements that must stay in sync with codebase delivery.
- Maintaining strict adherence to architectural standards stored in
docs/rules/. - Executing complex task management through the lifecycle-based
docs/todo/directory system. - Onboarding developers by providing a single point of truth that explains the 'why' behind the 'what'.
Example Prompts
- "Initialize a new feature entity in the docs/definitions/features/ folder for the authentication module update."
- "Scan the docs/todo/pending/ folder and prioritize the highest impact tasks based on our current business rules."
- "Check the code in src/api against the requirements defined in docs/definitions/technical/api-spec.md and report any discrepancies."
Tips & Limitations
- Tip: Treat the
docs/folder as immutable code. If you change a requirement, update the documentation file first, then the implementation. - Tip: Use the dot-file signals within each entity folder to track the state of your project clearly.
- Limitation: The skill requires disciplined folder management; if the hierarchy is not maintained strictly, the AI may struggle to index specific entities. Always ensure that
docs/remains the root directory for all project definitions to prevent indexing errors.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-eduardou24-ogt-docs": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write
Related Skills
ogt-docs-define
General guide for creating definition documents. Use when you need to define WHAT something IS - concepts, entities, systems, or domains. Routes to specialized sub-skills for specific definition types (business, features, code, marketing, branding, tools).
ogt-docs-create
Create new documentation entities in the docs-first system. Routes to specialized creation sub-skills for tasks, definitions, rules, features, and social content. Use when adding any new documentation.
ogt-docs-create-task
Create and manage task documents in the docs/todo/ workflow. Use when creating new tasks, updating task status, or moving tasks between workflow stages. Provides complete task lifecycle management with verification.