docs-expert

Generate technical documentation from a project's Discovery Brief.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/echarabati/adi-capital-admin --skill docs-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-expert
Source: https://github.com/echarabati/adi-capital-admin/tree/main/.agent/skills/roles/docs
Command: npx skills add https://github.com/echarabati/adi-capital-admin --skill docs-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the generation of essential technical documentation from a project's Discovery Brief, ensuring consistency and saving significant time for product and engineering teams.

Core Features & Use Cases

  • Automated Document Generation: Creates Feature Maps, User Personas, User Stories, Business Rules, Data Models, and Architecture documents.
  • ID Consistency: Manages and enforces stable IDs for features, stories, and entities across all generated documents.
  • Use Case: After completing a Discovery Brief, use this Skill to instantly produce a comprehensive set of planning documents, ready for review and further design work.

Quick Start

Run the docs skill to generate all central technical documentation from the current discovery brief.

Frequently Asked Questions about docs-expert

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

FAQPage Schema
How do I generate technical documentation from a discovery brief?

To generate technical documentation from a discovery brief, run this Skill to automatically create feature maps, user personas, user stories, data models, and architecture diagrams directly from your project requirements.

What is included in automated project documentation generation?

Automated project documentation generation includes feature maps, user personas, user stories, business rules, data models, and architecture diagrams, ensuring a single source of truth for project specifications.

Can I refine generated requirements and technical writing iteratively?

Yes, you can refine generated requirements and technical writing iteratively using built-in refresh modes, which update existing documents and flag open questions or assumptions requiring further clarification.

How does automated documentation handle ID consistency across user stories and data models?

Automated documentation handles ID consistency by enforcing stable IDs and cross-referencing for features, user stories, and entities across all generated documents to maintain a single source of truth.

What is the best way to maintain a single source of truth for project specifications?

The best way to maintain a single source of truth for project specifications is to generate documents from a central discovery brief, enforcing consistent ID generation and cross-referencing across all technical writing outputs.