tdmcp-docs-roadmap-update

Coordinate multi-phase sub-agent workflows to update tdmcp documentation and roadmaps.

30|6|Updated May 25, 2026
One-click install
npx skills add https://github.com/Pantani/tdmcp --skill tdmcp-docs-roadmap-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdmcp-docs-roadmap-update
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/tdmcp-docs-roadmap-update
Command: npx skills add https://github.com/Pantani/tdmcp --skill tdmcp-docs-roadmap-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the maintenance and synchronization of tdmcp documentation surfaces after feature waves or releases, including ROADMAP.md, high-level docs, EN/PT prompts cookbooks, and generated references.

Core Features & Use Cases

  • Release audit orchestration: runs and coordinates local release audits, changelog checks, and documentation surfaces.
  • Docs & Roadmap edits: updates docs/ROADMAP.md and related guides to reflect shipped features.
  • Cookbook sync & QA: aligns EN/PT cookbooks with new features and validates generated docs via QA workflow.
  • Agent orchestration: spawns and coordinates role agents defined in .Codex/agents to execute sub-tasks in order.

Quick Start

Run this skill to refresh the docs ROADMAP and related guides after a feature release.

Frequently Asked Questions about tdmcp-docs-roadmap-update

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

FAQPage Schema
How do I automate documentation roadmap updates after a release?

Automate documentation roadmap updates by coordinating a multi-phase sub-agent workflow that applies release audits, edits ROADMAP.md, synchronizes cookbooks, and runs QA verification.

What is the best way to sync EN/PT cookbooks with new released features?

Sync EN/PT cookbooks with new features by running a coordinated QA workflow that aligns cookbook content with shipped features and validates generated documentation references.

How does sub-agent orchestration work for documentation release audits?

Sub-agent orchestration works by spawning role agents defined in the .Codex/agents directory to execute release audits, roadmap edits, and QA verification sub-tasks in sequential order.

Do I need to manually edit docs/ROADMAP.md after shipping a feature wave?

You do not need to manually edit docs/ROADMAP.md after shipping a feature wave; the workflow automatically updates the roadmap and related guides to reflect shipped features.

Can I run a QA verification workflow on generated documentation references?

You can run a QA verification workflow on generated documentation references during release cycles to validate the updated docs and ensure cookbook synchronization accuracy.

When should I run an automated docs roadmap refresh?

Run an automated docs roadmap refresh immediately after a feature release or feature wave to ensure all documentation surfaces, ROADMAP.md, and cookbooks remain synchronized.