sync-project-docs

sync-project-docs is a skill for Claude Code from 686f6c61/alfred-dev. It costs 37 tokens per session (412 once invoked), scanned A, original, MIT.

A procedure for updating a project's living documentation after a development phase. It covers project status, architecture, compliance, threat modelling, and the documentation index.

In plain words
What is it for?
Use it after a phase to update only the relevant documents and check that the documentation gate passes before closing the phase.
Why use it?
It keeps documentation aligned with actual code changes without adding claims about work that was not done.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 .claude/alfred-continuity.py sync-project-docs "$PWD".

Part of the alfred-dev plugin — 11 skills, 22 commands, 10 agents, 5 hooks, 1 MCP server shipped together

Good fit Use it after a phase to update only the relevant documents and check that the documentation gate passes before closing the phase.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/686f6c61/alfred-dev
agentmods
npx agentmods add skills/686f6c61/alfred-dev/sync-project-docs

Made for: Claude Code.

Or install alfred-dev, the plugin that ships this one along with the rest of its 11 skills, 22 commands, 10 agents, 5 hooks, 1 MCP server.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sync-project-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/686f6c61/alfred-dev/sync-project-docs/github.svg)](https://agentmods.dev/skills/686f6c61/alfred-dev/sync-project-docs)
Your own site
<a href="https://agentmods.dev/skills/686f6c61/alfred-dev/sync-project-docs"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/sync-project-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sync-project-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/686f6c61/alfred-dev/sync-project-docs"><img src="https://agentmods.dev/badge/skills/686f6c61/alfred-dev/sync-project-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 412 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00037 $0.00412
Opus 5.5 $0.00015 $0.00165
Sonnet 5.5 $0.00007 $0.00082
Haiku 4.5 $0.00004 $0.00041

Measured 2mo ago against content hash bd44ae0b8668, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync-project-docs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/sync-project-docs/SKILL.md · 53 lines

What it actually says

Sincronizar documentación viva

Resumen

Tras una fase, actualiza solo lo que ha cambiado. El helper crea esqueletos y comprueba la gate. Tú escribes el contenido.

Proceso

  1. Esqueleto e índice:

    python3 .claude/alfred-continuity.py sync-project-docs "$PWD"
    
  2. Lee docs/project/README.md y el protocolo commands/_docs_vivas.md.

  3. Actualiza únicamente los ficheros de la fase. Si no hubo API nueva, no toques una guía de API. Si no hubo decisión, no inventes un ADR.

  4. Cuando un esqueleto tenga contenido real, deja <!-- alfred-doc:filled --> y quita <!-- alfred-doc:scaffold -->.

  5. Comprueba la gate:

    python3 .claude/alfred-continuity.py check-project-docs "$PWD" --command <comando> --phase <fase>
    
  6. Si el helper falla, no declares la fase cerrada.

En quick y fix

Sync mínimo: índice + docs/project/current.md. ADR solo si el cambio mueve un límite (auth, persistencia, integración).

Criterios de éxito

  • El índice refleja el estado real (scaffold o filled).
  • No hay prosa inventada sobre código que no se ha tocado.
  • check-project-docs sale 0 antes de cerrar la gate.

Qué NO hacer

  • No reescribas todo docs/ en cada fase.
  • No copies el chat al Markdown.
  • No marques filled si siguen los _(pendiente)_.
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 53 lines · 37 tokens per session scan A bd44ae0b8668

Subscribe to this mod's changes

sync-project-docs is a skill published in the GitHub repository 686f6c61/alfred-dev (115 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 412 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

promote-idea

Converts an album idea from IDEAS.md into an actual album project in one step. Use when the user says "promote [idea title]", "turn idea into album", or "start working on [idea]".

bitwize-music-studio/claude-ai-music-skills · 50 tokens

customer-onboarding-and-implementation

Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…

cbrock84/headcount · 94 tokens

vendor-management

Selects, contracts, and manages suppliers and vendors — requirements, evaluation, negotiation support, onboarding, performance management, and exit. Use this to choose a vendor, run a selection process, structure a service agreement's operational terms, manage an underperforming supplier, plan an exit or migration, or…

cbrock84/headcount · 69 tokens

traction-eos

Implement the Entrepreneurial Operating System (EOS) to align vision and execution across a company. Use when the user mentions "EOS", "Entrepreneurial Operating System", "V/TO", "quarterly rocks", "Level 10 meetings", "accountability chart", "IDS process", "my company feels chaotic", "we keep having the same…

wondelai/skills · 147 tokens

ledger

OPS on-demand: This skill should be used when the user asks to "ops ledger", "what did we handle", or…

Lifecycle-Innovations-Limited/claude-ops · 28 tokens

bmad-retrospective

Review a finished epic folder in the ticket tree against the evidence it left behind — the epic file, each ticket's story file and plan, diffs, commits — and produce a retrospective with sourced findings, action items, and an acceptance decision. Use when the user says "run a retrospective" or "lets retro the epic…

bmad-code-org/BMAD-METHOD · 0 tokens