Compare a PRD against its last Git commit with section-by-section changes.
npx skills add https://github.com/sinositato/tato-claude-plugins --skill prd-diff
Please help me install this Agent Skill. Skill: prd-diff Source: https://github.com/sinositato/tato-claude-plugins/tree/main/plugins/prd-builder/skills/prd-diff Command: npx skills add https://github.com/sinositato/tato-claude-plugins --skill prd-diff
This Skill helps you quickly understand the differences between your current Product Requirements Document (PRD) and its last saved version, highlighting exactly what has changed.
Compare the current working copy of 'my-feature-prd.md' against its last committed version.
High-intent search queries and answers about installing and using this skill.
Comparing PRD versions involves checking your current document against its last committed version in Git to highlight section-by-section additions, removals, and modifications. It maps semantic changes to a 22-section template for detailed reporting.
Tracking document changes in Git is done by comparing the working copy against the last committed version to extract semantic additions and removals. It provides word count deltas to show exactly how much each section was altered before committing or sharing.
Yes, this PRD diff tool requires Git to function because it operates read-only by comparing your current working copy against the last committed version. It relies on Git version control to establish the baseline for the document comparison.
Yes, you can see word count differences when comparing requirement documents. The analysis provides word count deltas for each section, offering insights into the extent of additions, removals, and modifications mapped to a 22-section template.
Section-by-section document comparison works by analyzing semantic changes within PRD sections and mapping them to a 22-section template. It breaks down the differences between your current file and its last committed version, highlighting specific additions and removals.
sitharaj88Generate and execute conventional Git commit messages from staged changes.
shawnpangTranslate ambiguous product ideas into an 8-section PRD with success metrics.
mikersaysInitialize a structured issue tracking system in a Git repository.
cipherstashRun pre-commit checks and create atomic conventional commits.
