# Update Docs

> Update project documentation after implementing a feature. Use when: updating docs, documentation, update docs after implementation. Do not use: for doc-first design, specification writing.

- **Type:** Skill
- **Install:** `agentstack add skill-woliveiras-geremmyas-update-docs`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [woliveiras](https://agentstack.voostack.com/s/woliveiras)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [woliveiras](https://github.com/woliveiras)
- **Source:** https://github.com/woliveiras/geremmyas/tree/main/project/.github/skills/update-docs

## Install

```sh
agentstack add skill-woliveiras-geremmyas-update-docs
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Update Docs

Update documentation in `docs/` after a feature is implemented.

## When to Use

- After finishing a feature implementation
- When specs, code, or architecture changed and docs are stale
- When onboarding docs need to reflect new patterns

## Procedure

1. Read the spec for the implemented feature (from `specs/` or the conversation)
2. Read the implemented code to understand what actually shipped
3. Search `docs/` for existing documentation that may need updates
4. For each affected doc:
   - If it exists: update the relevant sections, preserving the existing format
   - If it doesn't exist: create it following the format of neighboring docs
5. Check for broken references (links to moved/renamed files)

## What to Document

- **API changes**: new endpoints, changed parameters, updated responses
- **Architecture changes**: new modules, changed boundaries, new patterns
- **Setup changes**: new dependencies, changed build steps, new env vars
- **Configuration changes**: new settings, changed defaults

## Rules

- Match the existing documentation style and format
- Do NOT rewrite docs that don't need changes
- Keep docs concise — one paragraph per concept, not walls of text
- Update the table of contents if the doc has one
- If no `docs/` directory exists, create it with a README

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [woliveiras](https://github.com/woliveiras)
- **Source:** [woliveiras/geremmyas](https://github.com/woliveiras/geremmyas)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-woliveiras-geremmyas-update-docs
- Seller: https://agentstack.voostack.com/s/woliveiras
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.