用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/peel/fiddle --skill discover命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Use after implementation to analyze drift, update documentation, evolve evaluation, and close a completed epic.
Use when starting or resuming a full development lifecycle for a feature or explicit epic.
Use when you have a spec or requirements for a multi-step task, before touching code.
基于 SOC 职业分类
正在显示 SKILL.md
| name | discover |
| description | Use before defining a feature or epic to gather context, research options, and challenge scope assumptions. |
Invoke as fiddle:discover <topic> [--skip-docs] [--skip-challenge].
Gather project context, research the ecosystem, and challenge scope assumptions before defining a solution.
ARGUMENTS: {ARGS}
Parse from {ARGS}:
| Flag | Default | Description |
|---|---|---|
--skip-docs | false | Skip discover-docs — go straight to research and challenge |
--skip-challenge | false | Skip the challenge step after scope confirmation |
Config: see skills/orchestrate/SKILL.md for the schema. This skill reads providers.phases.discover (the provider list for this phase), the providers.<name>.command and .flags declarations for each provider named there, and providers.timeout.
Skip if --skip-docs was set.
Invoke discover-docs to gather project context and identify gaps:
Use the fiddle:discover-docs skill with <topic>.
This reads existing docs, CLAUDE.md, beans, and relevant source files. It produces a structured summary of what exists, what's relevant, and what gaps remain.
After discover-docs, check for user research artifacts:
docs/product/personas/ — if they exist, load them. Note which personas are relevant to the topic being discovered.docs/product/insights/ — if it exists, load it. Surface any themes or open questions relevant to the topic.If these artifacts exist, include relevant findings when presenting the discovery summary. If they don't exist, skip silently.
If providers are configured (default: codex):
Read hooks/dispatch-provider.sh for collection rules. For each provider, dispatch via:
hooks/dispatch-provider.sh <provider> \
--role "Research analyst" \
--topic "<topic>" \
--instructions "Research: ecosystem patterns, prior art, implementation approaches, potential pitfalls. Be specific and cite concrete examples."
Run provider dispatches in parallel when the harness supports it; otherwise run them sequentially. Collect results in attended mode.
If no provider CLI is available, skip and proceed with the current harness's internal knowledge only.
Skip if --skip-challenge was set.
Invoke the challenge skill to confirm scope and stress-test assumptions:
Use the fiddle:challenge skill with --phase discover.
This opens by synthesizing findings and confirming scope with the user, then walks the decision tree on assumptions and constraints — resolving every branch before moving forward. It self-serves answers from the codebase and only asks the user about genuine ambiguity.