Borrowing it
Nothing to install: this file belongs to Kandil7/prprompts-flutter-generator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kandil7/prprompts-flutter-generator/master/.claude/commands/automation/update-plan.mdgit clone --depth 1 https://github.com/Kandil7/prprompts-flutter-generatorWrote 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.
[](https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/update-plan)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/update-plan"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/update-plan.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.03409 |
| Opus 5 | $0.00000 | $0.01705 |
| Sonnet 5 | $0.00000 | $0.00682 |
| Haiku 4.5 | $0.00000 | $0.00341 |
Grade A, and why
update-plan 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EXECUTE: Update Implementation Plan
IMPORTANT: This is an EXECUTION command. Immediately perform all steps below without waiting for confirmation.
Re-plan based on actual progress, calculate velocity, identify blockers, and adjust sprint allocations.
STEP 1: Prerequisites Check
First, check if IMPLEMENTATION_PLAN.md exists:
ls docs/IMPLEMENTATION_PLAN.md
If missing:
❌ Error: docs/IMPLEMENTATION_PLAN.md not found
Please run:
claude generate-implementation-plan
Then try update-plan again.
STEP 2: Read Current Plan
Read docs/IMPLEMENTATION_PLAN.md and extract:
Metadata:
- Team Size: How many developers
- Sprint Duration: 2 weeks (standard)
- Initial Velocity: Planned SP/sprint
- Actual Velocity: Average from completed sprints
- Total Tasks: Total count
- Total Story Points: Sum of all tasks
Current Progress:
For each task, extract:
- Task ID: e.g., "Task 1.2"
- Status: TODO | IN_PROGRESS | BLOCKED | DONE | SKIPPED
- Estimated: Hours planned
- Actual: Hours spent (if DONE or IN_PROGRESS)
- Owner: Team member assigned
- Sprint: Which sprint it's in
Completed Sprints:
For each sprint marked [COMPLETED] or [IN_PROGRESS]:
- Sprint Number: 1, 2, 3...
- Planned SP: Story points allocated
- Completed SP: Story points actually done
- Velocity %: (Completed / Planned) × 100%
STEP 3: Calculate Actual Velocity
Velocity Formula:
Actual Velocity = Average(Completed SP per sprint)
Example:
Sprint 1: 32 planned, 32 completed → 100%
Sprint 2: 32 planned, 26 completed → 81%
Sprint 3: 32 planned, 10 completed → 31% (Week 1 only, not counted)
Average velocity = (32 + 26) / 2 = 29 SP/sprint
Velocity Trend:
- Increasing: Team getting faster (learning curve)
- Stable: Consistent delivery
- Decreasing: Technical debt, blockers, team issues
Compare to Planned Velocity:
Planned Velocity: 44 SP/sprint (team capacity)
Actual Velocity: 29 SP/sprint
Velocity Ratio: 29 / 44 = 66% (delivering 66% of capacity)
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.
- 7d ago First seen · 466 lines · 0 tokens per session scan A b303788846ed
update-plan is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,409 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-30.
Other commands, from other repositories
speckit.gh-triage.triage
Fetch open GitHub issues, classify each as bug, feature, or chore, then DELEGATE to the correct extension: bugs → bug.fetch (saved under .specify/bugs/), chores → chore.fetch (saved under .specify/chores/), features → speckit.specify (saved under specs/). Never save bugs or chores as specs.
speckit.chore.fetch
Load an existing GitHub issue into the chore workflow and seed a triage draft.
speckit.bug.issue
File a GitHub issue from a bug assessment (the 'report' phase) and record the issue link.
speckit.chore.implement
Implement the scoped chore (the actual maintenance work) and record what changed.
speckit.chore.issue
File a GitHub issue from a chore assessment (the 'report' phase) and record the issue link.
speckit.gh-triage.feature
Create a GitHub issue describing a new feature, label it with the configured feature label, and optionally auto-run speckit.specify to turn it into a spec.