Slash Command

/update-docs

Updates implementation documentation: reviews specs/status/testing results, marks completed tasks, updates percentages, adds best practices/lessons to phase docs, CLAUDE.md, README.md.

Markdown

documentation

Install

npx claudepluginhub davepoon/buildwithclaude --plugin all-commands

Allowed Tools

ReadEditWrite

Prompt Preview

# Documentation Update Command: Update Implementation Documentation

## Documentation Analysis

1. Review current documentation status:
   - Check `specs/implementation_status.md` for overall project status
   - Review implemented phase document (`specs/phase{N}_implementation_plan.md`)
   - Review `specs/flutter_structurizr_implementation_spec.md` and `specs/flutter_structurizr_implementation_spec_updated.md`
   - Review `specs/testing_plan.md` to ensure it is current given recent test passes, failures, and changes
   - Examine `CLAUDE.md` and `README.md` for project-wide documentation
   ...

Command Content

Other plugins with /update-docs

/update-docs

Generates script references, env var docs from source files like package.json and .env.example, updates CONTRIBUTING.md and RUNBOOK.md, checks doc staleness, and shows update summary.

everything-claude-code

162.2k

/update-docs

Updates implementation documentation: reviews specs/status/testing results, marks completed tasks, updates percentages, adds best practices/lessons to phase docs, CLAUDE.md, README.md.

ReadEditWrite

commands-documentation-changelogs

2.7k

/update-docs

Syncs documentation from package.json scripts and .env.example, generating docs/CONTRIB.md (dev workflow, scripts, env, testing) and docs/RUNBOOK.md (deployment, monitoring, issues, rollback). Identifies obsolete docs and shows diff.

claude-forge

605

/update-docs

Updates project documentation based on changes: consolidates redundancies, debloats, detects AI slop, syncs capabilities, verifies accuracy via LSP. Supports skip flags and strict mode.

sanctum

242

/update-docs

Generates script references, env var docs from source files like package.json and .env.example, updates CONTRIBUTING.md and RUNBOOK.md, checks doc staleness, and shows update summary.

awesome-claude-notes

123

/update-docs

Updates project documentation from source-of-truth files like package.json, .env.example, openapi.yaml, and Dockerfiles; generates script refs, env docs, contributing guide, runbook; checks staleness.

everything-claude-code

Stats

Parent Repo Stars2696

Parent Repo Forks300

Last CommitJan 4, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Tags

documentation-update

implementation-status

specs-update

best-practices

lessons-learned

# Documentation Update Command: Update Implementation Documentation ## Documentation Analysis 1. Review current documentation status: - Check `specs/implementation_status.md` for overall project status - Review implemented phase document (`specs/phase{N}_implementation_plan.md`) - Review `specs/flutter_structurizr_implementation_spec.md` and `specs/flutter_structurizr_implementation_spec_updated.md` - Review `specs/testing_plan.md` to ensure it is current given recent test passes, failures, and changes - Examine `CLAUDE.md` and `README.md` for project-wide documentation ...

Documentation Update Command: Update Implementation Documentation

Documentation Analysis

Review current documentation status:

Check specs/implementation_status.md for overall project status
Review implemented phase document (specs/phase{N}_implementation_plan.md)
Review specs/flutter_structurizr_implementation_spec.md and specs/flutter_structurizr_implementation_spec_updated.md
Review specs/testing_plan.md to ensure it is current given recent test passes, failures, and changes
Examine CLAUDE.md and README.md for project-wide documentation
Check for and document any new lessons learned or best practices in CLAUDE.md

Analyze implementation and testing results:

Review what was implemented in the last phase
Review testing results and coverage
Identify new best practices discovered during implementation
Note any implementation challenges and solutions
Cross-reference updated documentation with recent implementation and test results to ensure accuracy

Documentation Updates

Update phase implementation document:

Mark completed tasks with ✅ status
Update implementation percentages
Add detailed notes on implementation approach
Document any deviations from original plan with justification
Add new sections if needed (lessons learned, best practices)
Document specific implementation details for complex components
Include a summary of any new troubleshooting tips or workflow improvements discovered during the phase

Update implementation status document:

Update phase completion percentages
Add or update implementation status for components
Add notes on implementation approach and decisions
Document best practices discovered during implementation
Note any challenges overcome and solutions implemented

Update implementation specification documents:

Mark completed items with ✅ or strikethrough but preserve original requirements
Add notes on implementation details where appropriate
Add references to implemented files and classes
Update any implementation guidance based on experience

Update CLAUDE.md and README.md if necessary:

Add new best practices
Update project status
Add new implementation guidance
Document known issues or limitations
Update usage examples to include new

Documentation Update Command: Update Implementation Documentation

Documentation Analysis

Review current documentation status:

Check specs/implementation_status.md for overall project status
Review implemented phase document (specs/phase{N}_implementation_plan.md)
Review specs/flutter_structurizr_implementation_spec.md and specs/flutter_structurizr_implementation_spec_updated.md
Review specs/testing_plan.md to ensure it is current given recent test passes, failures, and changes
Examine CLAUDE.md and README.md for project-wide documentation
Check for and document any new lessons learned or best practices in CLAUDE.md

Analyze implementation and testing results:

Review what was implemented in the last phase
Review testing results and coverage
Identify new best practices discovered during implementation
Note any implementation challenges and solutions
Cross-reference updated documentation with recent implementation and test results to ensure accuracy

Documentation Updates

Update phase implementation document:

Mark completed tasks with ✅ status
Update implementation percentages
Add detailed notes on implementation approach
Document any deviations from original plan with justification
Add new sections if needed (lessons learned, best practices)
Document specific implementation details for complex components
Include a summary of any new troubleshooting tips or workflow improvements discovered during the phase

Update implementation status document:

Update phase completion percentages
Add or update implementation status for components
Add notes on implementation approach and decisions
Document best practices discovered during implementation
Note any challenges overcome and solutions implemented

Update implementation specification documents:

Mark completed items with ✅ or strikethrough but preserve original requirements
Add notes on implementation details where appropriate
Add references to implemented files and classes
Update any implementation guidance based on experience

Update CLAUDE.md and README.md if necessary:

Add new best practices
Update project status
Add new implementation guidance
Document known issues or limitations
Update usage examples to include new