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.
Why use this skill?
Learn how to use the ogt-docs-create skill to efficiently manage your project documentation, from technical tasks and definitions to coding rules.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/eduardou24/ogt-docs-createWhat This Skill Does
ogt-docs-create is the central orchestrator for managing documentation within the OpenClaw docs-first framework. Rather than manually creating files, this skill provides a standardized pathway for generating structured documentation entities. It acts as a router, directing user intent to specific sub-skills that handle the creation of tasks, definitions (covering features, business logic, code, marketing, and branding), rules, and social media content. By enforcing a consistent folder-based structure, it ensures that your project documentation remains searchable, organized, and scalable.
Installation
To install this skill, use the following command in your OpenClaw environment:
clawhub install openclaw/skills/skills/eduardou24/ogt-docs-create
Ensure your workspace is configured to handle folder creation, as this skill performs direct filesystem operations to scaffold new directories and boilerplate files.
Use Cases
- Project Management: Rapidly create tasks in the
docs/todo/pending/directory to track development progress. - Architecture Documentation: Define system components or code structures within the
docs/define/code/directory to maintain team knowledge. - Standardization: Establish and formalize coding standards or git workflows by creating entries in the
docs/rules/directory. - Content Marketing: Draft social media posts and marketing collateral using the dedicated social sub-skill, ensuring consistent storage in
docs/content/social/. - History Tracking: Maintain project transparency by appending updates to the
CHANGELOG.mdfile through the automated changelog sub-skill.
Example Prompts
- "I need to track a new feature for the user authentication flow. Please create a task for this."
- "Establish a new coding rule for our repository that mandates consistent error handling blocks in all asynchronous functions."
- "Create a new feature definition for the upcoming dark-mode UI toggle, ensuring it is stored in the correct features folder."
Tips & Limitations
- Follow the Slug Format: Always use lowercase, hyphenated slugs (e.g.,
user-login-flow) for your folder names to avoid path issues. - Identify the Type: Before triggering the skill, be clear about whether you are creating a rule, a definition, or a task to ensure the correct routing.
- Consistency: This skill is strictly for creating entities. It does not replace the need for thoughtful content writing; remember to fill in the generated templates with specific project details after creation.
- Dependencies: Ensure your system has write permissions for the
docs/root directory to allow the sub-skills to scaffold effectively.
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-create": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-write, file-read
Related Skills
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).
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.