Synchronize product specifications with session decisions while preserving EARS formatting and versioning.
npx skills add https://github.com/etr/groundwork --skill sync-specs
Please help me install this Agent Skill. Skill: sync-specs Source: https://github.com/etr/groundwork/tree/main/skills/sync-specs Command: npx skills add https://github.com/etr/groundwork --skill sync-specs
Product teams often diverge between session discussions and formal specs. This skill ensures that decisions made during a session are reflected in the master spec documents.
After a session ends, run this skill to synchronize product specs with the latest decisions.
High-intent search queries and answers about installing and using this skill.
To synchronize product specs with session decisions, run this skill after a session to read current specs, detect scope changes, and propose targeted updates to the PRD while preserving versioning.
Spec management with this skill preserves EARS formatting when proposing updates to requirements, ensuring that changes to PRD and feature sections remain structured and compliant with the existing format.
Yes, you can track versioning and maintain a clear audit trail for PRD updates, supporting safe and reviewable changes for collaboration across product teams.
The best way to align open questions and feature sections after scope changes is to map session discussions to corresponding product specs, proposing targeted updates for review.
You need to update the central specs document whenever requirements, scope, or features change during a session and need alignment across PRD and design artifacts.
vladm3105Validate PRD documents against Layer 2 schema standards.
polikeijiWrite and maintain Markdown product specification documents with frontmatter versioning.
AhmedKaram50Plan collaborative UX design workflows with structured steps and frontmatter-driven progress tracking.
michael-harrisRemove Git worktrees and optionally delete associated branches.
