Update docs/roadmap.md diffs from git history and pubspec.yaml.
npx skills add https://github.com/YoursshLabs/yourssh --skill yourssh-roadmap
Please help me install this Agent Skill. Skill: yourssh-roadmap Source: https://github.com/YoursshLabs/yourssh/tree/main/.claude/skills/yourssh-roadmap Command: npx skills add https://github.com/YoursshLabs/yourssh --skill yourssh-roadmap
Update docs/roadmap.md efficiently by diffing against the current repo state and history, avoiding a full rewrite and ensuring alignment with shipped changes and strategic plans.
Run the roadmap refresh to update docs/roadmap.md with the latest changes
High-intent search queries and answers about installing and using this skill.
Updating a roadmap based on git history without rewriting it uses a diff-based approach to align docs/roadmap.md with the latest codebase state. It reads git log and current version data to generate precise diffs, outputting an updated section with a timestamp.
Refreshing your project roadmap using a diff-based workflow is applicable during feature ships, version bumps, sprint planning, or roadmap review requests. This ensures roadmap accuracy by reflecting shipped changes and strategic plans without starting from scratch.
Yes, the roadmap refresh process reads version information directly from app/pubspec.yaml. It aligns docs/roadmap.md with the current codebase state, repository surface areas, and git history to synchronize metadata like version lines and date stamps.
The best way to synchronize roadmap documentation with shipped features and version bumps is automated metadata synchronization. It determines when to refresh, applies changes by generating precise diffs, and presents outputs for review to reflect reality accurately.
Yes, you can use this diff-based roadmap update for sprint planning and feature ships. It evaluates repository surface areas and git history to propose changes that reflect sprint outcomes, ensuring documentation alignment without a full content rewrite.
A limitation of updating roadmap diffs against the current codebase state is that it proposes changes strictly based on git log and repository surface areas. It does not generate new strategic content from scratch, focusing only on aligning existing roadmap text with shipped code reality.
VamdawnAnalyze commit history to infer semantic versions and update version files and changelogs.
MicrockValidate and align project documentation with the current codebase.
Emz1998Generate sprint reports with goals, completed work, blockers, and velocity.
muhammadhamad1104Generate structured documentation using the Diataxis framework.
