do-docs

Create, restructure, and update technical documentation against tech-docs standards.

10|2|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/thermiteau/maverick --skill do-docs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-docs
Source: https://github.com/thermiteau/maverick/tree/main/skills/do-docs
Command: npx skills add https://github.com/thermiteau/maverick --skill do-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation is often neglected or inconsistent across projects, making onboarding and maintenance slow and error-prone. This Skill provides a structured workflow to create, restructure, and update technical docs while enforcing standards.

Core Features & Use Cases

  • Greenfield documentation: create a compliant docs baseline for a new project.
  • Refactor: audit and rewrite non-compliant docs to meet tech-docs standards.
  • Update: incrementally apply changes after code updates and maintain index consistency.
  • Validation: ensure documentation adheres to mav-scope-boundaries and tech-docs checks.

Quick Start

Tell the skill the mode (greenfield, refactor, or update), or let it auto-detect, and run the documentation workflow.

Frequently Asked Questions about do-docs

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

FAQPage Schema
How do I automate technical documentation creation for a new software project?▼

To automate technical documentation creation for a new software project, run a greenfield workflow that establishes a compliant docs baseline aligned with tech-docs standards. The system structures initial documentation and generates a standard index for consistent maintenance.

What is the best way to update existing technical docs after a code refactor?▼

Updating existing technical docs after a code refactor is best handled by an incremental update workflow that applies changes and maintains index consistency. This process validates documents against the tech-docs checklist to ensure post-change code is accurately reflected.

How do I validate technical documentation against scope boundaries?▼

You can validate technical documentation against scope boundaries by applying validation checks that confirm adherence to mav-scope-boundaries and tech-docs checklists. This process audits existing documents, identifies compliance gaps, and verifies scope alignment.

Does this documentation workflow support automatic mode detection for updates?▼

Yes, this documentation workflow supports automatic mode detection for updates. You can explicitly specify greenfield, refactor, or update modes, or let the system auto-detect the appropriate workflow based on the current project state and documentation structure.

When do I need to restructure technical documentation using a refactor workflow?▼

Restructure technical documentation using a refactor workflow when existing docs are non-compliant or inconsistent across software projects. This workflow audits and rewrites documents to meet tech-docs standards and align with mav-scope-boundaries for improved maintainability.