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).
Why use this skill?
Use the ogt-docs-define skill to create clear, consistent definition documents for your business concepts, product features, and technical architecture in OpenClaw.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/eduardou24/ogt-docs-defineWhat This Skill Does
ogt-docs-define acts as the foundational documentation architect for the OpenClaw ecosystem. It is designed to establish clarity and consistency by standardizing how concepts, entities, systems, and domains are defined. The core philosophy of this skill is that effective implementation, marketing, and development cannot proceed without an agreed-upon definition of what a thing IS. The skill provides a structured framework that answers critical questions: What is the entity? Why does it exist? What are its boundaries? And how does it relate to the broader system? It intentionally avoids implementation details or task lists, focusing strictly on conceptual purity and scope.
Installation
You can install this skill directly via the OpenClaw hub using the following command:
clawhub install openclaw/skills/skills/eduardou24/ogt-docs-define
Use Cases
- Building a shared project lexicon for team alignment.
- Scoping new features before technical development begins.
- Defining business entities like user personas, revenue models, or market segments.
- Documenting technical architecture, API models, or system services.
- Establishing brand guidelines, including tone of voice and core messaging pillars.
- Documenting developer-facing tools, workflows, and CLI interfaces.
Example Prompts
- "ogt-docs-define: Create a definition document for our new 'User Loyalty' feature, explaining its core purpose, boundary conditions, and how it maps to our existing membership database."
- "ogt-docs-define: I need a business definition for our 'Freemium' pricing model. Focus on the value exchange and why this model exists in our current market strategy."
- "ogt-docs-define: Define the 'Data Ingestion Service' architecture, detailing the expected input formats and the primary system responsibilities without writing the implementation code."
Tips & Limitations
- Tip: When in doubt, consult the sub-skill routing table. If your definition involves code-level structures, always route to
ogt-docs-define-coderather than the general tool. - Tip: Maintain the 'Boundary' section strictly. Knowing what a feature is NOT is just as important as knowing what it IS for preventing scope creep.
- Limitation: This skill does not generate code or execution scripts. It is strictly a documentation aid designed for human-readability and conceptual modeling. Avoid using it for actionable task management or automated deployment configurations.
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-define": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Related Skills
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.
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.