A structured methodology for creating definition documents that establish what concepts, entities, and systems are within a project.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install ogt-docs-define
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
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).
Get the raw skill files in a ZIP archive.
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.
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
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. |
Loading
A centralized skill for routing and generating structured documentation entities like tasks, features, and rules using a standardized folder-based architecture.

A comprehensive documentation-first system for managing the complete lifecycle of coding tasks from proposal to production.

A compact symbolic language designed to facilitate high-efficiency, low-token communication between AI agents.

A comprehensive, framework-first playbook for building, testing, and deploying Solana dApps and on-chain programs.

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

A comprehensive automation skill for interacting with the Nostr protocol and managing decentralized social identities via the nak command-line tool.








































