Taya Skills

English · 中文

A collection of reusable Agent Skills for Claude (Claude Code / Claude.ai / Claude API) and other AI tools that can load Markdown instructions, such as Codex. Each skill is a self-contained folder with a SKILL.md instruction file, plus the templates and references it loads on demand.

This repository ships three skills: technical-pm (write a PRD), prd-review (audit a PRD someone already wrote), and technical-pm-guided (learn PM skills step by step).

technical-pm - Technical Product Manager

technical-pm makes the assistant operate like an experienced technical product manager: someone who owns what to build and why, not just how. Give it a fuzzy idea, raw feature request, meeting notes, or an existing requirements document, and it turns that material into clear, sharply scoped, buildable product artifacts.

The skill is intentionally product-first. It should clarify the problem, scope, success criteria, and risks before implementation begins.

AI/ML product lens built in. When the feature is AI-driven, such as extraction, classification, generation, OCR, or matching, technical-pm applies a dedicated lens: eval sets, thresholds, precision/recall tradeoffs, error-cost asymmetry, human-in-the-loop review, needs_review handling, and data dependencies.

What It Produces

When To Use It

Use technical-pm whenever you are deciding what to build or why:

• writing a PRD or product spec;
• scoping an MVP;
• breaking a feature into epics, stories, and tasks;
• prioritizing a backlog;
• estimating a sprint or release;
• defining success metrics;
• assessing product, delivery, or technical risk;
• preparing a stakeholder update or decision doc.

It should also activate when someone asks the assistant to "act as a PM", "wear the product hat", or starts building without a clear problem statement and scope.

Output Language

The skill follows the user's language. For Chinese users, product artifacts default to Chinese while keeping established framework terms such as MVP, PRD, RICE, and MoSCoW in English.

prd-review - PRD Completeness Review

prd-review is the inverse of technical-pm: instead of writing a PRD, it audits one that someone has already written. Point it at an existing PRD or spec and it answers a single question: can an engineer build the right thing from this without guessing, and if not, what exactly is missing? It diagnoses the document rather than rewriting it.

It reuses the technical-pm body of knowledge, but inverts it: those references define how a good PRD is written, so here they become the standard the review judges against.

What It Produces

When To Use It

Use prd-review when you want to review, grade, or sanity-check an existing PRD rather than write one, for example "审一下这份 PRD", "这份需求能交开发吗", "PRD 还缺什么", or "is this spec ready for dev". Trigger it on evaluating a PRD someone already wrote, not on drafting a new one.

technical-pm-guided - Guided Learning for technical-pm

technical-pm-guided is a Socratic-coaching companion for the technical-pm skill. Instead of producing PM artifacts for the user, it teaches users how to produce them themselves — one workflow step at a time, with hands-on practice, feedback, and progressive hints.

It uses the same body of knowledge as technical-pm (references/ and assets/) but inverts it: those files define how a good PM artifact is made, and the guided mode walks the user through creating each one themselves.

How It Differs from technical-pm

What It Teaches

The skill walks users through the 8 technical-pm workflows (Discovery → PRD → Slicing → Prioritization → Estimation → Metrics → Risk → Communication), matching its opening strategy to the user's intent:

• Convergent ("Teach me how to do X") — step-by-step, hands-on practice with the user's real case
• Divergent ("What is product management?") — brief overview + 2–3 entry points to pick from
• Simple recall ("What does RICE mean?") — short definition + invitation to practice with it

Design Principles

Informed by ChatGPT Study Mode and Gemini Guided Learning:

1. One step at a time — never dump the entire methodology at once
2. Guide, don't produce — the user writes first, the coach gives feedback
3. Progress over purity — after 2–3 failed attempts, demonstrate directly
4. Practice over theory — teach through the user's real case, not abstract explanations

When To Use It

Use technical-pm-guided when someone wants to learn PM skills rather than get a finished artifact. Triggers include "教我怎么写 PRD", "带我走一遍需求拆分", "我是新手", "不会排优先级", "teach me how to...", "walk me through...", or "I'm new to this".

Installing Into Claude Code

Copy a skill folder into Claude Code's skills directory:

mkdir -p "$HOME/.claude/skills"
cp -R technical-pm "$HOME/.claude/skills/technical-pm"
cp -R prd-review "$HOME/.claude/skills/prd-review"
cp -R technical-pm-guided "$HOME/.claude/skills/technical-pm-guided"

Then start a new conversation and either let a skill trigger automatically on product/PM-shaped requests, or invoke it explicitly:

$technical-pm
$prd-review
$technical-pm-guided

Example prompts:

Act as a technical PM and turn this feature idea into a scoped PRD.
Review this PRD and tell me whether it is ready for development.

Other AI Tools

Load a skill's SKILL.md (technical-pm/SKILL.md, prd-review/SKILL.md, or technical-pm-guided/SKILL.md) as the system instruction. The skill will pull relevant files from references/ and assets/ on demand.

Repository Structure

skills/
├── .gitignore
├── LICENSE
├── README.md
├── README.zh-CN.md
├── technical-pm/
│   ├── SKILL.md                       # instructions and workflow router
│   ├── agents/
│   │   └── openai.yaml                # display name and default prompt for Codex-style UIs
│   ├── assets/                        # fill-in templates
│   │   ├── prd-template.md
│   │   ├── risk-register-template.md
│   │   └── user-story-template.md
│   └── references/                    # deep-dive references loaded on demand
│       ├── ai-ml-products.md
│       ├── delivery-and-process.md
│       ├── discovery-and-requirements.md
│       ├── edge-cases-and-exceptions.md
│       ├── metrics.md
│       ├── prioritization-and-estimation.md
│       ├── technical-artifacts.md
│       └── worked-example.md
├── prd-review/
│   ├── SKILL.md                       # instructions and rubric router
│   ├── agents/
│   │   └── openai.yaml
│   ├── assets/                        # templates and the HTML report shell
│   │   ├── prd-template.md
│   │   ├── report-template.html
│   │   ├── risk-register-template.md
│   │   └── user-story-template.md
│   └── references/                    # the rubric and standards the review judges against
│       ├── ai-ml-products.md
│       ├── delivery-and-process.md
│       ├── discovery-and-requirements.md
│       ├── edge-cases-and-exceptions.md
│       ├── metrics.md
│       ├── prioritization-and-estimation.md
│       ├── review-rubric.md
│       ├── technical-artifacts.md
│       ├── worked-example.md
│       └── worked-review-example.md
└── technical-pm-guided/
    ├── SKILL.md                       # Socratic coaching instructions
    ├── agents/
    │   └── openai.yaml
    ├── assets/                        # shared templates (same as technical-pm)
    │   ├── prd-template.md
    │   ├── risk-register-template.md
    │   └── user-story-template.md
    └── references/                    # shared references (same as technical-pm)
        ├── ai-ml-products.md
        ├── delivery-and-process.md
        ├── discovery-and-requirements.md
        ├── edge-cases-and-exceptions.md
        ├── metrics.md
        ├── prioritization-and-estimation.md
        ├── technical-artifacts.md
        └── worked-example.md

Conventions

• SKILL.md is the sole entry point for each skill.
• agents/openai.yaml holds UI metadata; execution logic lives in SKILL.md.
• references/ holds deep-dive material loaded progressively on demand.
• assets/ holds output templates and reusable files.
• Avoid extra READMEs or changelogs inside skill folders so the assistant has less loading noise.

Adding More Skills

To add another skill, create a new top-level folder with at least a SKILL.md. Keep the skill self-contained: templates in assets/, detailed guidance in references/, and UI metadata in agents/ only when a target assistant surface needs it.