wr-jtbd:update-guide

Generate and migrate Jobs To Be Done documentation into docs/jtbd/ directories.

4|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/windyroad/agent-plugins --skill wr-jtbd-update-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wr-jtbd:update-guide
Source: https://github.com/windyroad/agent-plugins/tree/main/packages/jtbd/skills/update-guide
Command: npx skills add https://github.com/windyroad/agent-plugins --skill wr-jtbd-update-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create or update the project's Jobs To Be Done (JTBD) documentation by organizing per-persona directories and individual job files under docs/jtbd/, while migrating legacy content from docs/JOBS_TO_BE_DONE.md when present.

Core Features & Use Cases

  • Generate per-persona directories with persona.md and JTBD files.
  • Migrate legacy JTBD content from docs/JOBS_TO_BE_DONE.md into the new structure.
  • Maintain a central docs/jtbd/README.md index to summarize personas and jobs and track status.

Quick Start

Run wr-jtbd:update-guide to generate or migrate the JTBD documentation structure in docs/jtbd/.

Frequently Asked Questions about wr-jtbd:update-guide

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

FAQPage Schema
How do I migrate legacy Jobs To Be Done documentation into a structured directory?

Generate Jobs To Be Done documentation by creating per-persona directories with persona.md files and individual job definitions under docs/jtbd/, while maintaining a central README.md index to track status.

Does this JTBD structure migration require an existing docs file?

This JTBD structure migration does not strictly require an existing file; it can create new persona and job files in docs/jtbd/ or migrate content if a legacy docs/JOBS_TO_BE_DONE.md file is present.

How do I organize Jobs To Be Done files by persona for product governance?

Organize Jobs To Be Done files by generating dedicated per-persona directories under docs/jtbd/, each containing a persona.md and specific job files to support product discovery and governance workflows.

What is the best way to maintain a central index for JTBD personas and jobs?

Maintain a central index for JTBD personas and jobs by generating a docs/jtbd/README.md file that summarizes all personas, lists individual jobs, and tracks their current status.

When do I need a standardized JTBD documentation structure?

You need a standardized JTBD documentation structure when product discovery workflows require clear persona and job definitions, or when governance processes demand organized, per-persona job tracking.