draft-guide

Name: draft-guide
Availability: InStock
Author: Covcloud-LLC

Generate Diátaxis-structured documentation drafts verified against repository code and git history.

Updated Jul 9, 2026

Search Tags:#automation #workflow #documentation #technical writing #verification #diátaxis

Ready to run

npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill draft-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: draft-guide
Source: https://github.com/Covcloud-LLC/adhd-workflow/tree/main/skills/draft-guide
Command: npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill draft-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent, unverified, or poorly structured technical documentation by automating the creation of first drafts that adhere to the Diátaxis framework and the repository's specific house voice.

Core Features & Use Cases

Diátaxis Mode Selection: Automatically structures content as a tutorial, how-to, quickstart, brief, or explanation based on the user's intent.
Technical Verification: Ensures every command, output, and value is verified against the current codebase or live service before writing.
Use Case: When you need to promote a complex reasoning note into a formal explanation doc, this skill transforms the note while maintaining technical accuracy and matching the existing documentation style.

Quick Start

Ask the assistant to draft a how-to guide for the authentication module using the latest plan from the backlog.

Frequently Asked Questions about draft-guide

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

FAQPage Schema

How do I automate technical documentation drafts using the Diátaxis framework?▼

Automating technical documentation drafts with the Diátaxis framework requires structuring content as tutorials, how-to guides, quickstarts, briefs, or explanations while verifying all technical claims against source code and git history.

What is the best way to generate verified how-to guides from repository plans and reasoning notes?▼

Generating verified how-to guides from repository plans and reasoning notes involves transforming notes into prose-shaped drafts while validating every command, output, and value against the current codebase or live service to ensure factual accuracy.

Does this approach to technical writing ensure consistency with my existing documentation style?▼

Consistency with existing documentation style is maintained by operating on repository-specific plans and reasoning notes, matching the repository's specific house voice while promoting complex notes into formal explanation docs.

Can I use this automation workflow to create different types of documentation like tutorials and quickstarts?▼

Creating different types of documentation like tutorials and quickstarts is supported through automatic Diátaxis mode selection, structuring content based on user intent into tutorials, how-to guides, quickstarts, briefs, or explanations.

What prerequisites are needed to generate technically-verified documentation drafts?▼

Generating technically-verified documentation drafts requires integration with the repository's backlog root and git history to validate all technical claims and front-matter metadata before writing the final prose.

Why does documentation generation require verification against the current codebase?▼

Documentation generation requires verification against the current codebase to ensure factual accuracy, preventing inconsistent or unverified technical claims by validating every command, output, and value before writing the draft.