Uc Interviewer logo

Uc Interviewer

Organization
TestAny-io
uc-interviewer

User journey interview, use case interview, 用户旅程访谈。Use when: 基于 BRD 访谈、整理或补全 User Journey，"对齐 use case"、"确认用户操作流程"。

Overview

PublisherTestAny-io
Repositorytestany-agent-skills
Skill nameuc-interviewer
Stars
82
Forks
23
Bundled files
7
LicenseMIT
Links
Skill sourceRepositoryHomepage
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by TestAny-io on GitHub. Read the source before you install it.

Installation

Install the Uc Interviewer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/TestAny-io/testany-agent-skills.git /tmp/testany-agent-skills
mkdir -p .claude/skills
cp -r /tmp/testany-agent-skills/plugins/testany-eng/skills/uc-interviewer .claude/skills/uc-interviewer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Uc Interviewer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Uc Interviewer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Uc Interviewer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

UC Interviewer - 用户旅程梳理

先读取 工作流执行约定 和 访谈模式与事实标准：先取证、按真实能力工作，从当前安装位置定位资源。

默认跟随用户输入语言；显式指定优先。metadata 字段、枚举、ID 和 comment markers 保持英文，模板与子任务继承同一 output_language，见 语言规则。

触发与边界

用于基于 BRD 澄清或整理用户操作流程、跨 Journey 跳转和异常/边界行为。不替代技术设计、PRD 批准或实施。仅编辑已有 Journey 片段时只检查受影响范围，不重新启动完整访谈。

模式选择

模式行为
interview模糊目标或明确要求访谈：开放发现，必要时提供可信选项，每轮 2-3 个关键缺口；尊重逐条确认要求
synthesis材料足够且要求整理：批量复用已知旅程、步骤、优先级及跳转，直接交付草稿，不强制逐条再确认
gap_followup材料基本齐全：只问未决分支、来源冲突或缺失决定，不重问有效基线和已有事实

已确认事实与本次工件的正式批准分开；用户只要求草稿就保持 draft。没有批准 BRD 仍可产出带来源状态的探索性草稿，不自行升级为正式基线。

工作流

1. 读取 BRD 与旅程材料

读取用户指定 BRD、相关批准依据和已有流程。提取目标用户、业务目标、in/out-scope、成功定义、版本及来源。 多份来源冲突时引用具体差异，集中询问真实缺口；文件名、“approved”标签或修改时间不单独证明批准。

2. 建立范围与稳定 ID

复用已明确的 Journey 范围和优先级，为缺失而确有必要的项目询问，不重新确认所有已给内容。 维护稳定 JOURNEY 工件 ID、FLOW-* Journey ID 和每条 Journey 的 S1/S2/... Step ID；更新已有材料不随意重编号。 建立 BRD → Journey 映射及 Journey Graph。新发现超出当前范围的旅程先作为待决项，不擅自扩大范围。

3. 细化步骤、跳转与边界

对每条在范围内的 Journey 整理：

  • 谁、目标、前置/入口、终点与用户得到的结果。
  • Happy Path 步骤；每条流向记录 from/to、触发条件、跨 Journey 目标入口和数据交接；结束用 END。
  • 异常、回退、重试、中断、权限、状态变化、部分成功等相关分支。已给决定直接复用，未给的关键行为保持待定。
  • 按 步骤级边界框架 检查适用类别，不能只列空泛名词。

每个选入范围的 edge case 记录 EC ID、类别、适用 Sx、触发条件、用户可见结果、处理流向、数据保留/恢复、MVP/后续及已确认/待定。 P0 Journey 不得把所有边界一概跳过；确无额外适用项时说明理由。MVP 边界缺失阻止锁定基线，但不阻止透明草稿。 这些是内容覆盖要求，不是每个字段都必须再次向用户提问。

4. 跨 Journey 一致性与 Checkpoint

检查共享步骤/异常策略、优先级依赖、悬挂跳转、未定义入口及跨 Journey 循环的退出路径。已有一致决定直接保留，仅对实质冲突补问。 按 checkpoint-gates.md 分别记录内容覆盖、证据和批准条件；不得因资料充分或 lint 成功自称 approved。

5. 交付与验证

按语言读取 中文模板 或 英文模板，包含：

  • journey-profile-v1 示例 中的 TRACEABILITY-METADATA、稳定 ID、source_documents、relations；使用该实际路径，不猜同名 schema 文件。
  • Journey Graph、步骤/跳转表、步骤级 Edge Case Matrix。
  • BRD → Journey 与 Journey → PRD 映射、Checkpoint Decision、待定项及真实 review record。

使用用户指定路径；未指定时选项目内合理默认并说明，不为路径重复提问。生成后先从当前 SKILL.md 的位置解析 TESTANY_ENG_ROOT（plugin 根目录），不要假定该环境变量预先存在。执行实际可用的检查：

bash
python3 "$TESTANY_ENG_ROOT/scripts/trace_lint.py" --format json --profile journey-profile-v1 "[Journey路径]"

lint 未运行/失败需如实记录，必要依赖缺失不自动安装，也不阻止草稿交付；不得声称 lint 已通过。只有满足 checkpoint 条件且有当前版本/范围的真实批准，才可锁定基线。 用户指定 draft 不因检查通过自动提升；改 metadata 状态后需重新校验最终版本。

返回实际文档、当前状态、检查结果及剩余决定。推荐下游需说明是否可作锁定基线，不因完成草稿自动启动 PRD 或让用户重复上游已知信息。

输出规范

流程图使用 Mermaid；如用户要求的交付格式不能承载 Mermaid，保留可审查的节点/边表并说明限制，不用装饰性图代替流向证据。 具体结构以模板和 journey-profile-v1 为准；模板中的示例状态不是批准事实，应按本次证据填写。

使用示例

  • “先访谈报销主流程，每条确认后再继续”：按该检查点访谈并等待。
  • “把完整流程笔记整理为 User Journey 草稿”：直接生成，不逐步重复确认。
  • “只有失败后是否重试、取消后是否保留草稿两点未定”：只补问两点，其余复用，未答前保留待定。
  • “只修改 S2 的按钮文案”：局部修改并检查相关步骤/跳转一致性，不重开完整准出。

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Uc Interviewer AI skill do?

User journey interview, use case interview, 用户旅程访谈。Use when: 基于 BRD 访谈、整理或补全 User Journey，"对齐 use case"、"确认用户操作流程"。

Why use Uc Interviewer on TypingMind?

Because you install it once and use it with any model. Uc Interviewer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Uc Interviewer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/TestAny-io/testany-agent-skills/tree/main/plugins/testany-eng/skills/uc-interviewer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Uc Interviewer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Uc Interviewer?

As many as you like. As long as a model supports skills, you can use Uc Interviewer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Uc Interviewer AI skill free?

Yes. It is published on GitHub by TestAny-io under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

Related AI Skills

View all
mattpocock logo

To Spec

mattpocock
CommunityPopular

Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.

22.3K
264.4K
1 files
View
mattpocock logo

To Tickets

mattpocock
CommunityPopular

Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket…

22.3K
264.4K
1 files
View
mattpocock logo

Triage

mattpocock
CommunityPopular

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

22.3K
264.4K
3 files
View
mattpocock logo

Claude Handoff

mattpocock
CommunityPopular

Hand the current conversation off to a fresh background agent that picks up the work immediately.

22.3K
264.4K
1 files
View

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇