workflow_coach

Analyze codebases page-by-page to surface gaps and recommend 1-2 concrete actions.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/mgsystemsdev/POD --skill workflow-coach
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow_coach
Source: https://github.com/mgsystemsdev/POD/tree/main/agent-system-base/.claude/skills/workflow_coach
Command: npx skills add https://github.com/mgsystemsdev/POD --skill workflow-coach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Late-stage QA and polish partner that reads the full codebase, analyzes each page for gaps, missing UX, and productivity improvements, and brainstorms ideas you might be missing. Use it when reviewing pages one by one, in QA or polish mode, or when you want a thinking partner to surface what could make a page better while staying minimal.

Core Features & Use Cases

  • Read the codebase to identify gaps in UX, missing validations, dead ends, and opportunities to streamline pages.
  • Brainstorm minimal improvements and surface 1-2 concrete recommendations per page for designers, engineers, and PMs.
  • Trigger phrases: "workflow coach", "let's review this page", "what am I missing", "help me polish", "go page by page".

Quick Start

Ask me to start a page-by-page review to begin a prioritized polish plan.

Frequently Asked Questions about workflow_coach

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

FAQPage Schema
How do I find missing UX validations and gaps during a page-by-page QA review?

To find missing UX validations during a page-by-page QA review, analyze your full codebase to surface thin spots, dead ends, and missing UX gaps for each route. This process identifies minimal concrete actions to streamline pages effectively.

What is the best way to brainstorm minimal improvements for high-traffic routes?

The best way to brainstorm minimal improvements for high-traffic routes is to read the codebase and analyze each page for productivity optimizations. You then surface one to two actionable recommendations for stakeholders.

How do I start a prioritized polish plan for my product's pages?

Start a prioritized polish plan by triggering a page-by-page review of your codebase. This analyzes pages, routes, and components to deliver concrete actions for missing validations and potential UX optimizations.

Can I use codebase analysis to surface productivity improvements for designers and PMs?

Yes, you can use codebase analysis to surface productivity improvements for designers, engineers, and PMs. By reviewing pages one by one, it identifies gaps and brainstorms one to two concrete recommendations per page.

When do I need a late-stage QA thinking partner for my codebase?

You need a late-stage QA thinking partner when you want to review pages in polish mode and surface what could make them better while staying minimal. It analyzes the full codebase to find gaps and missing UX features.

Does this approach work for identifying dead ends and missing validations on specific pages?

Yes, this approach works for identifying dead ends and missing validations by reading the codebase for pages and components. It then delivers actionable recommendations to fix these specific UX gaps.