OGT Docs Define for Openclaw

A structured methodology for creating definition documents that establish what concepts, entities, and systems are within a project.

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

Install & Download

1. ClawHub CLI

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

npx clawhub@latest install ogt-docs-define

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-define 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 Define?

OGT Docs Define serves as the foundational framework for establishing shared understanding across complex systems. It focuses strictly on the definition phase—answering what a thing is and why it exists—while intentionally excluding implementation details. By maintaining this separation, the skill ensures that all stakeholders, including developers and AI agents, operate from a unified source of truth.

This skill is part of the broader ecosystem of Openclaw Skills, providing a standardized routing system to specialized sub-skills for business, technical, marketing, and branding definitions. It utilizes a robust Folder-as-Entity pattern, where each concept is treated as a self-contained directory containing the primary documentation and metadata signal files to track its lifecycle.

OGT Docs Define Use Cases

  • Creating a shared vocabulary for complex business or domain-specific concepts.
  • Establishing clear boundaries and scope for new product features before development.
  • Documenting technical architecture, data models, and API contracts.
  • Managing the lifecycle of project documentation from initial draft to final approval or deprecation.
  • Providing a structured reference point for AI coding agents to understand system entities.

How OGT Docs Define Works

  1. Identify the entity type and select the relevant specialized sub-skill or use the general define process.
  2. Gather essential information through clarifying questions focused on the concept's name, purpose, and boundaries.
  3. Create a standardized folder structure within the docs/definitions/ directory using a unique slug.
  4. Draft the definition using a template that covers overview, core concepts, characteristics, and relationships.
  5. Initialize metadata using .version and .draft signal files to mark the current state.
  6. Execute the lifecycle workflow by moving the definition through review, approval, or rejection states using filesystem signals.

OGT Docs Define Setup

To implement this skill in your environment, ensure your repository follows the Openclaw Skills documentation structure. You can manually initialize a new definition using the following CLI commands:

# Create the directory for the new definition
mkdir -p docs/definitions/technical/example-concept

# Initialize the version metadata
echo '{"schema": "1.0", "created": "'$(date -Iseconds)'"}' > docs/definitions/technical/example-concept/.version

# Mark the initial state as draft
touch docs/definitions/technical/example-concept/.draft

OGT Docs Define Data Schema & Taxonomy

The skill organizes data using a Folder-as-Entity pattern where the folder name is the slug and its contents define the entity's state and essence.

Component Type Description
primary_file.md Markdown The core definition (e.g., definition.md or feature.md).
.version JSON Contains the schema version and ISO creation timestamp.
.draft Signal Empty file indicating the document is currently being written.
.approved Signal Empty file indicating the definition is finalized and valid.
.ready_for_review Signal Indicates the definition is awaiting stakeholder feedback.
.rejected_reason Text Explains why a definition was not approved.

OGT Docs Define Advanced Features

  • Multi-stage lifecycle management using filesystem-based signal files (Draft, Review, Approved, Rejected, Deprecated).
  • Standardized primary file naming conventions tailored to specific definition types (e.g., business vs technical).
  • Built-in routing logic to redirect specific queries to specialized Openclaw Skills sub-modules.
  • Explicit boundary definition requirements to prevent project scope creep.
  • Integrated attribution tracking to identify creators and reviewers of specific system concepts.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*