Claude Code Skill. AI-powered software documentation automation. Professional software documentation specialist. Featuring Progressive Disclosure Architecture. Supports: Design, Requirements, SRS, PRD, API, and architecture docs. Few shot examples for Spring Boot, Pulumi, etc., Supports (Markdown, DOCX, PDF).
git clone https://github.com/SpillwaveSolutions/document-specialist-skill.gitDocumentation Specialist Skill transforms Claude Code into an expert documentation specialist using Progressive Disclosure Architecture to minimize token consumption. It supports two primary workflows: Greenfield Documentation creates professional specifications (SRS, PRD, API docs, design documents) from industry-standard templates, while Brownfield Documentation reverse-engineers documentation from existing codebases—fully mapped for Spring Boot and Pulumi frameworks. The skill includes automated documentation audits with quality checklists, gap analysis, and best practices validation across IEEE, OpenAPI, and accessibility standards. Output formats include Markdown, DOCX, PDF, and visual diagrams via Mermaid and PlantUML. It's designed for software engineers, technical leads, and documentation teams who need to generate or maintain comprehensive technical documentation efficiently.
Install via Skilz Marketplace with `skilz install SpillwaveSolutions_document-specialist-skill/documentation-specialist` or clone the GitHub repository into your Claude Code skills directory. Ask Claude Code to create documentation from templates, document existing code, audit specifications, or convert formats—the skill routes requests to appropriate workflows based on your needs.
Generate IEEE-compliant Software Requirements Specifications from templates for formal projects
Reverse-engineer API documentation and architecture diagrams from existing Spring Boot applications
Audit and improve documentation quality with automated gap analysis and compliance checking
Create multi-format deliverables (Markdown, Word, PDF) for stakeholder communication
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/SpillwaveSolutions/document-specialist-skillCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Act as a software documentation specialist. Create a [DOCUMENT_TYPE] for [COMPANY] in the [INDUSTRY] sector. Use the following [DATA] as reference: [DATA]. Ensure the document follows Progressive Disclosure Architecture. Format the output in [OUTPUT_FORMAT].
# Software Requirements Specification (SRS) for GreenTech Solutions ## 1. Introduction ### 1.1 Purpose This document describes the software requirements for the GreenTech Solutions' Energy Management System (EMS). The EMS aims to optimize energy consumption and reduce carbon footprint for commercial buildings. ### 1.2 Scope The EMS will monitor and control energy-consuming devices, provide real-time analytics, and offer recommendations for energy savings. The system will integrate with existing Building Management Systems (BMS) and IoT devices. ## 2. Overall Description ### 2.1 Product Perspective The EMS will be a web-based application with a responsive design, accessible via desktop and mobile devices. It will consist of the following components: - **Energy Monitoring Dashboard**: Real-time visualization of energy consumption data. - **Device Management Module**: Control and configure connected devices. - **Analytics Engine**: Process historical data to identify trends and patterns. - **Recommendation System**: Provide actionable insights for energy savings. ### 2.2 User Classes and Characteristics - **Facility Managers**: Primary users responsible for monitoring and controlling the EMS. - **Building Occupants**: Secondary users who can view energy consumption data and receive recommendations. - **IT Administrators**: Users responsible for system maintenance and troubleshooting. ## 3. System Features ### 3.1 Energy Monitoring - **Data Collection**: Gather energy consumption data from connected devices at regular intervals. - **Data Visualization**: Display real-time and historical data in charts, graphs, and tables. - **Alerts and Notifications**: Notify users of unusual energy consumption patterns or device malfunctions. ### 3.2 Device Management - **Device Discovery**: Automatically detect and register new devices on the network. - **Device Control**: Allow users to turn devices on/off, adjust settings, and schedule operations. - **Device Groups**: Organize devices into groups for collective control and monitoring. ### 3.3 Analytics and Recommendations - **Data Processing**: Clean, validate, and aggregate raw data for analysis. - **Trend Analysis**: Identify trends and patterns in energy consumption data. - **Recommendation Generation**: Provide actionable insights for energy savings based on historical data and best practices. ## 4. Other Nonfunctional Requirements ### 4.1 Performance - The EMS shall process and display real-time data with a maximum delay of 5 seconds. - The system shall support up to 1,000 concurrent users without significant performance degradation. ### 4.2 Security - The EMS shall implement role-based access control (RBAC) to restrict user access to specific features and data. - The system shall encrypt sensitive data both at rest and in transit using industry-standard encryption algorithms. ### 4.3 Software Quality Attributes - **Usability**: The EMS shall have an intuitive and user-friendly interface, requiring minimal training for new users. - **Reliability**: The system shall have an uptime of at least 99.9% during normal operating hours. - **Maintainability**: The EMS shall be designed with modular components to facilitate future updates and enhancements. ## 5. Appendices ### 5.1 Glossary - **BMS**: Building Management System - **IoT**: Internet of Things - **EMS**: Energy Management System ### 5.2 References - ISO/IEC/IEEE 29148:2011 - Systems and software engineering - Life cycle processes - Requirements engineering - IEEE 830-1998 - Recommended Practice for Software Requirements Specifications
Define and manage infrastructure using code with familiar programming languages.
Your one-stop shop for church and ministry supplies.
Hierarchical project management made simple
Automate your browser workflows effortlessly
AI assistant built for thoughtful, nuanced conversation
Automate your spreadsheet tasks with AI power
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan