Ai Assisted Docs banner
dknauss dknauss

Ai Assisted Docs

AI community

Description

Methodology and process documentation for AI-assisted technical writing and review — a practical exploration.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

AI-Assisted Documentation Processes Applied to WordPress Security

[![Validate Reusable Docs Workflow](https://github.com/dknauss/ai-assisted-docs/actions/workflows/validate-reusable-generate-docs.yml/badge.svg)](https://github.com/dknauss/ai-assisted-docs/actions/workflows/validate-reusable-generate-docs.yml) [![License](https://img.shields.io/github/license/dknauss/ai-assisted-docs)](LICENSE) [![Security Policy](https://img.shields.io/badge/security-policy-4c1)](SECURITY.md) [![AI Authorship](https://img.shields.io/badge/AI%20authorship-disclosed-8a63d2.svg)](docs/ai-authorship.md)

This repository contains a methodology, process documentation, and working scripts for AI-assisted technical writing and editorial review. It includes agent roles, skills, and Behavior-Driven Development (BDD) scenarios for researching, updating, verifying, aligning, and cross-referencing complex technical documents for different audiences and use cases.

For CI status on the shared Pandoc generation pipeline, treat **Validate Reusable Docs Workflow** as the health signal for the reusable docs workflow. The reusable `workflow_call` entrypoint is designed to be called from other repositories, so its standalone badge/run history can reflect older downstream failures even when this repository's validation workflow is green.

As a working system, `ai-assisted-docs` curates and maintains a series of technical documents about WordPress security contained in four separate repositories, ensuring they remain living documents aligned with current code and industry standards. It can also track adjacent associated documentation repos when they share tooling or editorial process, without collapsing them into the four-document security series.

**End-to-end transparency is a key feature.** Readers of the resulting documents should be able to understand how AI was involved, what guardrails were in place, what authority hierarchies were followed, and where human editorial judgment was applied.