software-docs-system

Generate cross-phase documentation packs with BRD, SRS, and ADRs.

Updated Mar 20, 2026
One-click install
npx skills add https://github.com/2zcory/skills --skill software-docs-system
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-docs-system
Source: https://github.com/2zcory/skills/tree/main/software-docs-system
Command: npx skills add https://github.com/2zcory/skills --skill software-docs-system

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating durable, cross-phase documentation for software projects is hard without a unified system. This skill provides a structured approach to capture requirements, design decisions, and delivery handoffs across the Source, -ctx, and Knowledge surfaces, reducing drift and rework.

Core Features & Use Cases

  • Three-surface strategy (Source, -ctx, Knowledge) to map documents and decisions for long-term accessibility.
  • Artifact generation and traceability (BRD, SRS, ADRs, HLD/LLD) with linked user stories and outcomes.
  • Visual architecture and workflow diagrams using Mermaid.js, plus story-capture workflows to populate the -ctx repo.
  • bilingual documentation approach with English primary content and concise Vietnamese summaries.

Quick Start

Generate a minimal, coherent document pack for a software project and map it across Source, -ctx, and Knowledge repos.

Frequently Asked Questions about software-docs-system

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

FAQPage Schema
How do I automate cross-phase software documentation for BRD, SRS, and ADRs?

Automating cross-phase software documentation involves generating BRD, SRS, and ADRs within a unified system. This skill creates traceable document packs linking requirements to design decisions, reducing drift across project phases.

What is the best way to map architecture decisions across Source, -ctx, and Knowledge repos?

Mapping architecture decisions across Source, -ctx, and Knowledge repos uses a three-surface strategy for long-term accessibility. This approach places code-adjacent context, story capture, and durable knowledge in distinct locations.

Can I generate Mermaid.js workflow diagrams from my software requirements?

Generating Mermaid.js workflow diagrams from software requirements is supported to visualize architecture and workflows. The skill produces diagram visuals alongside structured BRD and SRS documentation.

Does traceable documentation support bilingual English and Vietnamese summaries?

Traceable documentation supports bilingual English and Vietnamese summaries for cross-phase artifacts. Primary content remains in English while concise Vietnamese summaries accompany the generated SRS and BRD files.

How do I create lightweight governance documentation packs for software delivery?

Creating lightweight governance documentation packs for software delivery requires linking user stories to outcomes via HLD and LLD artifacts. This skill automates traceable handoffs satisfying governance needs without excessive overhead.