refreshing-metrics

Refresh governance metrics in markdown documents from MCP issue data.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/bacchus-labs/wrangler --skill refreshing-metrics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refreshing-metrics
Source: https://github.com/bacchus-labs/wrangler/tree/main/skills/refreshing-metrics
Command: npx skills add https://github.com/bacchus-labs/wrangler --skill refreshing-metrics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating stale metrics across your project's governance documents, ensuring accurate project status reporting.

Core Features & Use Cases

  • Automated Metric Updates: Scans MCP issue data to refresh counts, percentages, and progress indicators.
  • Cross-Document Synchronization: Updates metrics in .wrangler/issues/README.md, .wrangler/specifications/README.md, and .wrangler/ROADMAP_NEXT_STEPS.md.
  • Use Case: After closing several issues and completing a specification, run this skill to automatically update the project dashboard and roadmap progress without manual recalculation.

Quick Start

Run the refreshing-metrics skill to update all governance document metrics.

Frequently Asked Questions about refreshing-metrics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically update project management metrics in markdown governance documents?

To update governance metrics in markdown documents automatically, you can run a skill that queries issue tracking data and refreshes issue counts, specification statuses, and progress indicators across your project's README and roadmap files without manual recalculation.

What is the best way to keep issue counts and specification statuses current across multiple project files?

Keeping issue counts and specification statuses current across multiple project files requires cross-document synchronization, which scans issue tracking data to update dashboards and roadmap progress indicators automatically whenever issues are closed or specifications are completed.

Do I need MCP issue data to refresh governance metrics and constitutional compliance percentages?

Yes, refreshing governance metrics and constitutional compliance percentages requires access to MCP issue data and specific file paths for updating READMEs and the ROADMAP_NEXT_STEPS file to ensure accurate project status reporting.

Can I update feature implementation progress in my roadmap without manually editing each markdown file?

You can update feature implementation progress in your roadmap without manual editing by running an automated metric refresh that queries issue tracking data and synchronizes progress indicators across your governance documentation files.

Why are my project dashboard metrics out of date after closing several issues and completing a specification?

Project dashboard metrics become stale after closing issues because markdown governance documents are not automatically linked to issue tracking data, requiring a manual or automated metric refresh to synchronize counts and statuses across files.