Mdspec: Automatically sync your Markdown files from GitHub repositories with wikis.

Mdspec addresses a common and tedious pain point in modern software development: the manual synchronization of technical documentation. Teams frequently write crucial specifications in Markdown, but these specs must live in multiple operational tools—a dev wiki (Confluence), a project tracker (ClickUp), and archival storage (S3). Mdspec solves this by treating documentation publishing as a Git-native, version-controlled workflow. The core mechanism is elegant in its simplicity and robustness. By utilizing a `.mdspecmap` file, developers define mappings that govern which Markdown content goes to which destination, and how. This configuration is then invoked via a single GitHub Actions step. The system is designed to be highly efficient, leveraging `git diff` to ensure that only genuinely modified specs are published, minimizing unnecessary API calls and maintaining a clean CI pipeline. What elevates Mdspec beyond a simple synchronization script is the 'Agent layer.' The ability to pass raw Markdown content through an LLM, like Claude Haiku, for post-publication transformation is a significant feature. Instead of merely copying a spec into a task management system, a team can specify that the published content should be transformed—for instance, turning a detailed feature spec into a concise, action-oriented task summary, or gathering multiple specs into structured release notes. This shifts the tool from being a mere publishing mechanism to an active documentation orchestration layer. For technical teams and documentation groups managing multiple projects, the combination of robust feature sets—such as multi-destination support, exclusion glob patterns, and segregated team-level mapping files—makes this highly valuable. The commitment to security, running on SOC 2 Type II and ISO 27001 compliant infrastructure with no content storage, is also a major positive differentiator. Mdspec positions itself not just as a publishing pipeline, but as a scalable, auditable system for ensuring documentation consistency across the entire software development lifecycle.