sync-docs

Audit and update Markdown documentation to match current specs, ADRs, and project state.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/ConductionNL/buildiq --skill sync-docs-conductionnl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sync-docs
Source: https://github.com/ConductionNL/buildiq/tree/main/.claude/skills/sync-docs
Command: npx skills add https://github.com/ConductionNL/buildiq --skill sync-docs-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation drifts out of sync with implemented features, specs, and configuration as projects evolve. This Skill systematically audits app feature docs or developer workflow guides against authoritative sources of truth, flags gaps and stale content, and applies confirmed updates without touching code or config files. ## Core Features & Use Cases - Dual sync modes: Sync user-facing app docs in a Nextcloud app's docs/ folder, or developer/Claude guides in the .github repo's docs/claude/ directory. - Spec-driven gap analysis: Cross-references OpenSpec specs, ADRs, and writing-docs.md principles to find outdated content, stale [Future] markers, broken links, duplicated content, and ADR compliance gaps. - Safe editing guardrails: Only modifies .md files, always asks for confirmation before writing, verifies git branch and remote divergence before editing the .github repo, and routes learnings through a candidates-to-learnings buffer. - Use Case: After shipping a new export feature in the OpenRegister app, run the sync to detect that docs/features/export.md is missing and the README still marks export as [Future], then apply confirmed fixes. ## Quick Start Ask the assistant to sync the docs for a specific app, for example by saying "sync the docs for openregister" or "check if the developer docs are up to date".

Frequently Asked Questions about sync-docs

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

FAQPage Schema
How do I sync app documentation with implemented features?▼

Invoke the sync with the app name, such as "/sync-docs openregister". The skill loads the app's OpenSpec specs and ADRs, compares them against README.md and docs/ files, presents a gap summary table, and applies updates only after your confirmation.

What is the difference between app mode and dev mode for doc syncing?▼

App mode syncs user-facing feature docs in a specific Nextcloud app's docs/ directory. Dev mode syncs developer and Claude workflow guides in the .github repo's docs/claude/ folder, and additionally verifies the repo's branch and remote sync state before editing.

Can the skill edit configuration files like schema.yaml or settings.json?▼

No. A strict guardrail limits edits to Markdown files only. When drift is detected in YAML or JSON files, the skill reports it as a manual follow-up item in the final summary instead of editing it.

Does the skill make changes without asking for confirmation?▼

No. Every sync presents a summary of proposed changes and asks how to proceed: update all, review file by file, show a full diff first, or cancel. Nothing is written until you explicitly confirm.

What happens if my local .github repo is behind the remote branch?▼

In dev mode the skill fetches the remote and compares local HEAD with origin before editing. If the local repo is behind, ahead, or diverged, it warns you and offers to pull or cancel so edits are never made on stale files.

Why does the skill refuse to add ADR links to app documentation?▼

ADRs are internal development constraints, not user-facing material. The skill uses ADRs only as audit context to check correctness, and names them in prose (e.g., "Conduction ADR-002") rather than linking to ADR file paths.