dokumentera

Automate intent-first documentation and governance for software projects.

3|Updated Mar 15, 2026

Search Tags:#templates #documentation #audit #artifact #contract #intent-first

Ready to run

npx skills add https://github.com/jgabor/agentera --skill dokumentera

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dokumentera
Source: https://github.com/jgabor/agentera/tree/main/skills/dokumentera
Command: npx skills add https://github.com/jgabor/agentera --skill dokumentera

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation drift and misalignment across projects cause rework and delays. Dokumentation centralizes governance to ensure upfront intent, consistent updates, and traceability from design to delivery.

Core Features & Use Cases

Intent-first documentation: capture feature intent before coding to guide design and acceptance.
Documentation governance: maintain consistent mappings (VISION, TODO, PLAN) and artifact contracts to align docs with code.
Audit-ready workflows: generate, verify, and trace documentation against implementation using contract templates.

Quick Start

Create or update the project's documentation to enforce intent-first planning and verify alignment with implementation.

Frequently Asked Questions about dokumentera

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent documentation drift between code and project artifacts?▼

Prevent documentation drift by applying intent-first governance to maintain consistent mappings between code and project artifacts like VISION, PLAN, and TODO files, ensuring traceability from design to delivery and reducing rework.

What is intent-first documentation and how does it guide software development?▼

Intent-first documentation captures feature intent before coding to guide design and acceptance criteria. It enforces upfront planning to align project documents with implementation through contract-based checklists and artifact mapping.

How do I audit project documents against implementation using contract templates?▼

Audit project documents against implementation by generating and verifying documentation using contract templates. This workflow traces artifacts to ensure alignment and satisfies frontmatter-driven discovery for scalable governance.

Does this documentation governance workflow require any specific dependencies or frameworks?▼

No specific dependencies or frameworks are required. The workflow operates independently using frontmatter-driven discovery and contract-based checklists to manage document creation, updates, and audits across software projects.

When should I use contract-based checklists for documentation governance?▼

Use contract-based checklists when you need audit-ready workflows to verify alignment between code and docs. This approach scales document governance by tracing implementation against captured intent and artifact mappings.