A centralized skill for routing and generating structured documentation entities like tasks, features, and rules using a standardized folder-based architecture.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install ogt-docs-create
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-create 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 Create is the foundational entry point for any documentation-first workflow. It provides a standardized framework for adding new documentation entities to your project, ensuring that every piece of information—from business definitions to technical rules—is stored in a predictable, machine-readable format. By leveraging this tool within the Openclaw Skills framework, developers can maintain a high-quality knowledge base that scales with their codebase.
This skill acts as a router, delegating specific creation tasks to specialized sub-skills such as ogt-docs-define or ogt-docs-rules. Every entity is organized into its own folder containing the primary markdown documentation and supplementary signal files, ensuring that your project metadata remains clean and searchable.
To begin using this skill within your Openclaw Skills environment, ensure your repository has a docs/_templates directory populated with your required markdown templates. You can initialize the structure manually or via the following bash commands:
# Create the directory structure
mkdir -p docs/{todo,define,rules,content,marketing}
# Example: Create a new feature folder
mkdir -p docs/define/features/new-feature-slug
# Copy a template into place
cp docs/_templates/feature.md docs/define/features/new-feature-slug/feature.md
# Add mandatory signal files
echo '{"schema": "1.0", "created": "'$(date -Iseconds)'"}' > docs/define/features/new-feature-slug/.version
The skill organizes data using a strict folder-per-entity hierarchy. Each folder contains the primary document and various signal files that represent state and metadata.
| File/Folder | Purpose | Format |
|---|---|---|
docs/{path}/{slug}/ |
Main entity container | Directory |
task.md, feature.md |
Primary documentation content | Markdown |
.version |
Schema versioning metadata | JSON |
.priority |
Task urgency level | Plaintext (low/medium/high) |
.enforced_by |
Rule enforcement tool identifiers | Plaintext |
.status |
Current workflow state | Plaintext (draft/review/approved) |
Loading
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 specialized AI agent for fundamental and technical investment analysis across stocks, FIIs, and ETFs.

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

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








































