tech-spec-wrangler

Refresh doc-sources.yaml metadata using Ref MCP and generate reports.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill tech-spec-wrangler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tech-spec-wrangler
Source: https://github.com/jlenrique/course-DEV-IDE-with-AGENTS/tree/main/skills/tech-spec-wrangler
Command: npx skills add https://github.com/jlenrique/course-DEV-IDE-with-AGENTS --skill tech-spec-wrangler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill orchestrates a consistent docs-refresh workflow by prioritizing authoritative sources (Ref MCP) and synchronizing local metadata and refresh reports, reducing manual drift.

Core Features & Use Cases

  • Primary use: refresh documentation visibility by pulling changelogs and docs via Ref MCP, then updating local doc-sources.yaml metadata and generating a structured refresh report.
  • Optional sidecar augmentation: appends discoveries to an agent sidecar patterns.md to share insights with requesting tools.

Quick Start

Provide the path to the doc-sources.yaml and an optional output location for the refresh report.

Frequently Asked Questions about tech-spec-wrangler

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

FAQPage Schema
How do I refresh documentation from authoritative sources and update local metadata?

To refresh documentation, this skill prioritizes Ref MCP as the authoritative source to pull changelogs and docs, then updates local doc-sources.yaml metadata fields like last_refreshed and refresh_notes to prevent manual drift.

What is the best way to automate changelog retrieval and generate a structured refresh report?

Automating changelog retrieval involves routing requests through Ref MCP to fetch authoritative updates, summarizing the findings, and generating a structured refresh report to maintain documentation visibility workflows.

Does this documentation refresh workflow require a specific metadata format to function?

Yes, the documentation refresh workflow requires a doc-sources.yaml file as input to load existing metadata, alongside an optional output path for the generated refresh report.

Can I append discovered documentation patterns to a sidecar file during the refresh process?

Yes, you can append discoveries to an agent sidecar patterns.md file during the refresh process, optionally augmenting the workflow to share insights with requesting tools and specialist agents.

Why does my doc-sources.yaml metadata drift when manually tracking documentation updates?

Manual metadata drift occurs because tracking updates across multiple tools lacks consistency, whereas prioritizing an authoritative source like Ref MCP synchronizes local metadata and refresh reports automatically.

What are the limitations of using PyYAML for documentation metadata refresh workflows?

Using PyYAML limits the workflow to processing YAML structures like doc-sources.yaml, meaning it handles metadata parsing but does not directly retrieve documents without the Ref MCP integration.