What is dot-ai-prd-update-progress?

A process for updating a product requirements document using conversation context, Git commits, and code changes. It connects completed work to planned requirements and proposes progress updates for confirmation.

Use it to review implementation progress, update PRD requirements and checkboxes, record a progress checkpoint, and identify unfinished or divergent work.

It reduces the manual effort of keeping a PRD's checkboxes and status aligned with actual development work. It also highlights differences between the plan and the code.

dot-ai-prd-update-progress — Skill for Claude Code by vfarcic

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add vfarcic/dot-ai --skill dot-ai-prd-update-progress

Clone the repo

git clone --depth 1 https://github.com/vfarcic/dot-ai

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-update-progress/github.svg)](https://agentmods.dev/skills/vfarcic/dot-ai/dot-ai-prd-update-progress)

Your own site

<a href="https://agentmods.dev/skills/vfarcic/dot-ai/dot-ai-prd-update-progress"><img src="https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-update-progress/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vfarcic/dot-ai/dot-ai-prd-update-progress"><img src="https://agentmods.dev/badge/skills/vfarcic/dot-ai/dot-ai-prd-update-progress.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,801 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00023	$0.02801
Opus 5	$0.00012	$0.01401
Sonnet 5	$0.00005	$0.00560
Haiku 4.5	$0.00002	$0.00280

Measured 9d ago against content hash 8d88a7b47cc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

dot-ai-prd-update-progress 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 9d 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/skills/dot-ai-prd-update-progress/SKILL.md · 321 lines

How it starts

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

PRD Update Progress Slash Command

Instructions

You are helping update an existing Product Requirements Document (PRD) based on implementation work completed. This command analyzes git commits and code changes, enhanced by conversation context, to track PRD completion progress and propose evidence-based updates.

Process Overview

Identify Target PRD - Determine which PRD to update
Context-First Progress Analysis - Use conversation context first, Git analysis as fallback
Map Changes to PRD Items - Intelligently connect work to requirements
Propose Updates - Suggest checkbox completions and requirement changes
User Confirmation - Verify proposals and handle edge cases
Update PRD - Apply changes to checkboxes and status
Flag Divergences - Alert when actual work differs from planned work
Commit Progress Updates - Preserve progress checkpoint
Continue to Next Task - Prompt user to run /prd-next

Step 1: Smart PRD Identification

Automatically detect target PRD using conversation context:

Current Work Context: Look for recent conversation about specific PRD work, features, or issues
Git Branch Analysis: Check current git branch for PRD indicators (feature/prd-*, issue numbers)
Recent File Activity: Identify recently modified PRD files in prds/ directory
Todo List Context: Check if TodoWrite tool shows PRD-specific tasks in progress

Detection Priority Order:

If conversation explicitly mentions "PRD #X" or specific PRD file → Use that PRD
If git branch contains PRD reference (e.g., "feature/prd-12-*") → Use PRD #12
If TodoWrite shows PRD-specific tasks → Use that PRD context
If only one PRD file recently modified → Use that PRD
If multiple PRDs possible → Ask user to clarify

Step 2: Context-First Progress Analysis

PRIORITY: Use conversation context first before Git analysis

Conversation Context Analysis (FAST - Use First)

If recent conversation shows clear work completion:

Recently discussed implementations: "Just completed X", "Implemented Y", "Built Z"
Todo list context: Check TodoWrite tool for completed/in-progress items
File creation mentions: "Created file X", "Added Y functionality"
Test completion references: "Tests passing", "All X tests complete"
User confirmations: "That works", "Implementation complete", "Ready for next step"

Read the full file on GitHub · 321 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.

9d ago First seen · 321 lines · 23 tokens per session scan A 8d88a7b47cc1

Subscribe to this mod's changes

dot-ai-prd-update-progress is a skill published in the GitHub repository vfarcic/dot-ai (336 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 2,801 once invoked, about $0.0001 per session on Opus 5. 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.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

dot-ai-prd-update-progress