OGT Docs for Openclaw

A documentation-first workflow that treats the docs folder as the canonical source of truth for all definitions, rules, and tasks.

eduardou24
v1.0.0
Feb 8, 2026
0
1.5k
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install ogt-docs

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install ogt-docs using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is OGT Docs?

OGT Docs is a specialized skill designed for the Openclaw Skills ecosystem that implements a Documentation-as-Source-of-Truth (Doc-SoT) philosophy. It operates on the principle that documentation defines what a system is, while code is merely the implementation of those definitions. If a conflict arises between the two, the documentation is always considered correct.

This skill provides a structured framework for managing technical projects by routing requests to specific sub-skills for business definitions, coding rules, and task management. It ensures that every decision is recorded in the documentation before implementation begins, creating a robust, verifiable development lifecycle.

OGT Docs Use Cases

  • Initializing a new project with a structured docs-first architecture.
  • Defining business models, product features, and technical specifications as a primary source of truth.
  • Establishing and enforcing coding standards across frontend, backend, and infrastructure.
  • Managing complex task lifecycles using a folder-as-entity pattern.
  • Auditing task completion to ensure code accurately reflects documented requirements.

How OGT Docs Works

  1. Initialize the documentation structure using Openclaw Skills to create the foundational directory hierarchy.
  2. Define the project entities by creating folders in the definitions directory, including business and technical specs.
  3. Establish regulation by creating rules for coding standards and version control.
  4. Implement specific tasks by creating folder-based todo items that track progress from pending to done.
  5. Verify implementations by running audit checks that compare the resulting code against the source documentation.

OGT Docs Setup

To get started with this workflow in your environment, use the initialization sub-skill to generate the required directory structure:

# Initialize the documentation-as-source-of-truth structure
ogt-docs-init

# Configure your documentation workflow settings
ogt-docs-config

OGT Docs Data Schema & Taxonomy

The skill organizes data using a Folder-as-Entity pattern where each item is a directory containing specific files:

Component Location Description
Definitions docs/definitions/ Folders for business, features, technical, and domain specs.
Rules docs/rules/ Standards for code, git, and domain-specific implementation.
Tasks docs/todo/ Workflow stages: pending, in_progress, review, done, etc.
Guides docs/guides/ How-to documents and instructional content.
Signals .{signal_file} Dot-files (e.g., .approved, .verified) indicating status metadata.

OGT Docs Advanced Features

  • Intelligent routing to specialized sub-skills like ogt-docs-define-feature or ogt-docs-rules-code-infra.
  • Atomic status signaling using metadata dot-files to track approvals, blocks, and verification timestamps.
  • Support for the folder-as-entity pattern, allowing entire task contexts (including assets) to move through stages.
  • Specialized auditing tools to confirm implementation matches documentation before marking tasks as complete.
  • Seamless integration with the broader Openclaw Skills library for automated documentation-first agent workflows.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*