smithery.ai

implement-doc-update

Perform changes to implement a feature

First seen Mar 21, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,752 B
  • docs SUMMARY.md 66 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Update Documentation

Purpose of this skill

The purpose of this skill is to generate a meaningful and useful set of documentation that explains how an implementation works.

It is not to replicate API documentation (which drives the developer experience through XML comments), but rather to complement it with context and explanatory information, such that a developer with limited domain knowledge would be able to work on this project.

Compared to the [feature-doc-elaborate skill](../feature-doc-elaborate/SKILL.md), which is focused on the plan for an implementation, this skill is focused on documenting an implementation that either already exists or is currently in development.

When to use this skill

Use this skill when the user wants the agent to update documentation based on an implementation, or to update documentation while performing an implementation.

Process inputs

  • A workspace containing an implementation or partial implementation
  • Optionally, a focus or area to update in particular
  • Optionally, a partially created or outdated set of documentation
  • Optionally, a completed and up to date set of documentation

Process outputs

  • A completed and up to date set of documentation

How to update documentation

  • Read and analyse the code in the repository
  • Create a model of the implementation organised by functional area and component
  • Create or update a Markdown Document under [docs](../../docs/)
  • For ea
  • Link from [docs/README.md](../docs/README.md)
  • Validate links

Principles of documentation

  • Use common 'plain English'
  • Words that are not 'plain English', such as domain terms