Flutter-Structurizr: Command for Claude Code

.claude/commands/update-docs.md

update-docs is a command for Claude Code from Consiliency/Flutter-Structurizr. It costs 0 tokens per session (702 once invoked), scanned A, original, MIT.

A command for reviewing and updating implementation documentation after work is completed.

In plain words
What is it for?
Use it to update phase documents, testing notes, implementation percentages, README or CLAUDE.md guidance, and lessons learned.
Why use it?
It keeps project status, implementation plans, testing plans, and project guidance aligned with the code and test results.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is Consiliency/Flutter-Structurizr's own configuration. It tells Claude Code how to work on Flutter-Structurizr itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Flutter-Structurizr configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Consiliency/Flutter-Structurizr. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Consiliency/Flutter-Structurizr/main/.claude/commands/update-docs.md
Clone the repo
git clone --depth 1 https://github.com/Consiliency/Flutter-Structurizr

Made for: Claude Code.

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 update-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/consiliency/flutter-structurizr/update-docs/github.svg)](https://agentmods.dev/commands/consiliency/flutter-structurizr/update-docs)
Your own site
<a href="https://agentmods.dev/commands/consiliency/flutter-structurizr/update-docs"><img src="https://agentmods.dev/badge/commands/consiliency/flutter-structurizr/update-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 update-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/consiliency/flutter-structurizr/update-docs"><img src="https://agentmods.dev/badge/commands/consiliency/flutter-structurizr/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 702 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.
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.00000 $0.00702
Opus 5.5 $0.00000 $0.00281
Sonnet 5.5 $0.00000 $0.00140
Haiku 4.5 $0.00000 $0.00070

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

Security

Grade A, and why

update-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.

.claude/commands/update-docs.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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
    • Check for and document any new lessons learned or best practices in CLAUDE.md
  2. 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

  1. 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
  2. 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
  3. 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

Read the full file on GitHub · 88 lines

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 · 88 lines · 0 tokens per session scan A dd20fde37494

Subscribe to this mod's changes

update-docs is a command published in the GitHub repository Consiliency/Flutter-Structurizr (7 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 702 tokens. 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-31.

Related

update-docs compared with commands from other repositories

update-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-docsConsiliency/Flutter-StructurizrCommand711d agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code