Intelligent PRD Versioning Assistant

The Pain Point of Version Management in Collaborative Document Authoring

When product managers use Markdown to write PRDs or feature design documents, they often encounter a specific friction: the disconnect between the evolution of document content and versioned delivery. Teams rely on general-purpose version control tools like Git to manage the history of source files, but the process becomes manual and error-prone when a 'finalized' snapshot with a clear version number (e.g., v0.2) needs to be delivered to developers, testers, or reviewers. This may involve manually copying files, renaming them with a version tag, and ensuring all parties reference the correct file. This workflow is cumbersome and risks version confusion or file loss.

Core Capabilities and Workflow

This Skill provides a structured solution, centered around two scripts: gen_template.js and gen_from_md.js. They orchestrate a workflow between 'source Markdown documents' and 'versioned snapshots'.

1. Template-Driven Initialization: Using gen_template.js, you can quickly bootstrap a new document's source Markdown file based on a built-in universal template (e.g., references/通用需求文档模板.md). This enforces structural consistency (like the standard twelve chapters). You can leverage profile files to reuse project-wide common fields.
2. Single/Batch Snapshot Generation: The core function lies in the gen_from_md.js script. You point it to one or more unversioned source Markdown files. The script reads the version number from the document metadata, generates a snapshot file like {filename}_v0.1.md, and automatically archives any existing old snapshot with the same name into a backup/ directory, enabling clean version iteration.
3. Configuration and Reuse: Through profile files (sets of common parameters) and manifest files (batch task lists), you can abstract settings like output directories, archive paths, and project-wide information. For scenarios requiring batch document generation for multiple modules (--manifest mode), this significantly reduces repetitive configuration.
4. Integrated Security and Standards: During document generation, for sensitive features involving identity authentication, access control, etc., you can uniformly reference the compliance baseline in references/通用等保三级安全要求.md and supplement module-specific requirements in the document's 7.1 section. This avoids hardcoding security rules into each individual document.

Applicability Boundaries and Important Considerations

This Skill is a general-purpose document engineering tool designed to solve the problem of versioned delivery for standardized structured documents. Its application has clear boundaries:

• Clear Target: It is specifically designed for structured Markdown documents such as requirement documents, PRDs, and feature design documents. Force-fitting its template and workflow onto unstructured content like meeting notes or marketing copy is inappropriate.
• Project-Agnostic: The Skill itself contains no specific business logic. All project-specific chapter content, role names, and business rules (e.g., whether a particular delete feature offers bulk operations) need to be written into your own source documents or project-level profiles.
• Recommended Process: It advocates and facilitates a collaborative model of 'content first, then versioning'. The source file is the single source of truth for content, while the snapshot is a finalized version for delivery. Avoid modifying content directly on a snapshot file.
• Key Considerations: Before generation, please ensure the version number in the source document matches its revision history. For file naming in data export features, it is recommended to follow the convention {business_prefix}_{YYYYMMDD}_{HHMMSS}.xlsx to maintain consistency within the project.