docxa

Generates engineering documents from stakeholder interviews and codebase analysis.

Updated Mar 9, 2026

Search Tags:#code analysis #documentation #technical writing #ai #requirements gathering #stakeholder interviews

Ready to run

npx skills add https://github.com/achatt89/docxa --skill docxa

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and management of comprehensive software documentation, bridging the gap between stakeholder intent and technical reality.

Core Features & Use Cases

Automated Document Generation: Creates structured documents like BRDs, PRDs, HLDs, and ADRs using AI agents.
Evidence-Based Planning: Synthesizes information from stakeholder interviews and codebase analysis.
Use Case: A product manager can use Docxa to initiate a new project, conduct interviews with stakeholders, and automatically generate a Product Requirements Document (PRD) based on the gathered evidence.

Quick Start

Use the docxa skill to initialize a new workspace for a greenfield project.

Frequently Asked Questions about docxa

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

FAQPage Schema

How do I generate a PRD from stakeholder interviews and code analysis?▼

To generate a PRD from stakeholder interviews and code analysis, you can use AI agents to synthesize gathered evidence and repository insights into structured product requirements documents automatically.

What types of technical documentation can I automate for a software project?▼

You can automate various technical documentation types including BRD, PRD, FRD, TRD, HLD, LLD, NFR, and ADR files, bridging stakeholder intent with technical reality through evidence-based planning.

Can I use AI agents to create HLD and LLD documents from an existing codebase?▼

Yes, AI agents can analyze your existing repository and use CLI interaction for evidence gathering to create both High Level Design (HLD) and Low Level Design (LLD) documents.

Do I need CLI interaction to gather evidence for architecture decision records?▼

Yes, CLI interaction is required to gather evidence for architecture decision records, as the process relies on synthesizing stakeholder interviews and codebase analysis through LLM agents.

What's the best way to align stakeholder intent with technical reality in project docs?▼

The best way to align stakeholder intent with technical reality is through evidence-based planning that synthesizes stakeholder interviews and repository analysis into structured software documentation.