ideation（ideation 搜索） Skills下载安装命令和教程

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：ideation（ideation 搜索）
来源仓库：https://github.com/nicknisi/claude-plugins
仓库路径：skills/ideation
安装命令：
npx skills add nicknisi/claude-plugins --skill "ideation"
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

AgentSkills.tonpx skills

npx skills add nicknisi/claude-plugins --skill "ideation"

简介

用于查找、检索和筛选相关信息，支持基于关键词和任务场景的搜索。

适合在多种宿主环境中快速定位候选结果。
可结合来源仓库和原始文档核验具体功能。
安装前建议确认权限范围和维护状态。ideation 属于研究检索类 Skill，可作为该场景下的辅助能力补充。
注意是否涉及联网、命令执行或文件访问。

SKILL.md

name: ideation
description: Transform raw brain dumps (dictated freestyle) into structured implementation artifacts. Use when user has messy ideas, scattered thoughts, or dictated stream-of-consciousness about something they want to build. Produces contracts, phased PRDs, and implementation specs written to ./docs/ideation/{project-name}/.

Ideation

Transform unstructured brain dumps into structured, actionable implementation artifacts through a confidence-gated workflow.

Critical: Use AskUserQuestion Tool

ALWAYS use the AskUserQuestion tool when asking clarifying questions. Do not ask questions in plain text. The tool provides structured options and ensures the user can respond clearly.

Use AskUserQuestion for:

Clarifying questions during confidence scoring (Phase 2)
Project name confirmation before writing artifacts
Contract approval before PRD generation
PRD review feedback before spec generation
Any decision point requiring user input

Workflow Pipeline

INTAKE → CONTRACT FORMATION → PRD GENERATION → SPEC GENERATION → EXECUTION HANDOFF
              ↓                                                        ↓
         confidence < 95%?                                     [Fresh Session]
              ↓                                                        ↓
         ASK QUESTIONS                                         /execute-spec
              ↓                                                        ↓
         (loop until ≥95%)                                    Review → Test → Commit

Phase 1: Intake

Accept whatever the user provides:

Scattered thoughts and half-formed ideas
Voice dictation transcripts (messy, stream-of-consciousness)
Bullet points mixed with rambling
Topic jumping and tangents
Contradictions and unclear statements
Technical jargon mixed with vague descriptions

Don't require organization. The mess is the input.

Acknowledge receipt and begin analysis. Do not ask for clarification yet.

Phase 2: Contract Formation

2.1 Analyze the Brain Dump

Extract from the raw input:

Problem signals: What pain point or need is being described?
Goal signals: What does the user want to achieve?
Success signals: How will they know it worked?
Scope signals: What's included? What's explicitly excluded?
Contradictions: Note any conflicting statements

2.2 Calculate Confidence Score

Load references/confidence-rubric.md for detailed scoring criteria.

Score each dimension (0-20 points):

Dimension	Question
Problem Clarity	Do I understand what problem we're solving and why it matters?
Goal Definition	Are the goals specific and measurable?
Success Criteria	Can I write tests or validation steps for "done"?
Scope Boundaries	Do I know what's in and out of scope?
Consistency	Are there contradictions I need resolved?

Total: /100 points

2.3 Confidence Thresholds

Score	Action
< 70	Major gaps. Ask 5+ questions targeting lowest dimensions.
70-84	Moderate gaps. Ask 3-5 targeted questions.
85-94	Minor gaps. Ask 1-2 specific questions.
≥ 95	Ready to generate contract.

2.4 Ask Clarifying Questions

When confidence < 95%, MUST use AskUserQuestion tool to ask clarifying questions. Structure questions with clear options when possible.

Using AskUserQuestion effectively:

Provide 2-4 options per question when choices are clear
Use multiSelect: true when multiple answers apply
Keep question headers short (max 12 chars)
Include descriptions that explain implications of each choice

Question strategy:

Target the lowest-scoring dimension first
Be specific, not open-ended
Offer options when possible ("Is it A, B, or C?")
Reference what was stated ("You mentioned X, did you mean...?")
Limit to 3-5 questions per round
After each round, recalculate confidence

Question templates by dimension:

Problem Clarity:

"What specific problem are you trying to solve?"
"Who experiences this problem and how often?"
"What's the cost of NOT solving this?"

Goal Definition:

"What does success look like for this project?"
"How will you measure whether this worked?"
"What specific metrics should improve?"

Success Criteria:

"How will you know when you're done?"
"What tests would prove this feature works?"
"What would a QA person check?"

Scope Boundaries:

"What is explicitly NOT part of this project?"
"Are there related features we should defer?"
"What's the MVP vs. nice-to-have?"

Consistency:

"You mentioned [X] but also [Y]. Which takes priority?"
"These requirements seem to conflict. Can you clarify?"
"How should we handle [edge case]?"

2.5 Generate Contract

When confidence ≥ 95%, generate the contract document.

Use AskUserQuestion to confirm project name if not obvious from context
Convert to kebab-case for directory name
Create output directory: ./docs/ideation/{project-name}/
Write contract.md using references/contract-template.md
Use AskUserQuestion to get approval: "Does this contract accurately capture your intent?"

Do not proceed to PRD generation until contract is explicitly approved.

Phase 3: PRD Generation

After contract is approved:

3.1 Determine Phases

Analyze the contract and break scope into logical implementation phases.

Phasing criteria:

Dependencies (what must be built first?)
Risk (tackle high-risk items early)
Value delivery (can users benefit after each phase?)
Complexity (balance phases for consistent effort)

Typical phasing:

Phase 1: Core functionality / MVP
Phase 2: Enhanced features
Phase 3: Polish and optimization
Phase N: Future considerations

3.2 Generate PRDs

For each phase, generate prd-phase-{n}.md using references/prd-template.md.

Include:

Phase overview and rationale
User stories for this phase
Functional requirements (grouped)
Non-functional requirements
Dependencies (prerequisites and outputs)
Acceptance criteria

3.3 Present for Review

Show all PRDs to user. Use AskUserQuestion to gather feedback:

Question: "Do these PRD phases look correct?"
Options:
- "Approved" - Phases and requirements look good, proceed to specs
- "Adjust phases" - Need to move features between phases
- "Missing requirements" - Some requirements are missing or unclear
- "Start over" - Need to revisit the contract

Iterate until user explicitly approves.

Phase 4: Spec Generation

After PRDs are approved:

4.1 Generate Implementation Specs

For each approved phase, generate spec-phase-{n}.md using references/spec-template.md.

Include:

Technical approach
File changes (new and modified)
Implementation details with code patterns
Testing requirements
Error handling
Validation commands

4.2 Final Review

Present specs to user. Proceed to execution handoff.

Phase 5: Execution Handoff

After specs are generated, create task list and hand off for implementation.

5.1 Create Task List

Generate a unique task list ID and create initial phase tasks:

// Generate unique ID
const taskListId = `{project-name}-${Date.now()}`;

// Create phase tasks with dependencies
TaskCreate({
  subject: "Phase 1: {phase title from PRD}",
  description: "Execute spec-phase-1.md",
  activeForm: "Implementing Phase 1",
  metadata: { phase: 1, specFile: "spec-phase-1.md" }
});

// Phase 2 blocked by Phase 1
TaskCreate({
  subject: "Phase 2: {phase title}",
  description: "Execute spec-phase-2.md",
  activeForm: "Implementing Phase 2",
  metadata: { phase: 2, specFile: "spec-phase-2.md" }
});

TaskUpdate({
  taskId: "{phase2-id}",
  addBlockedBy: ["{phase1-id}"]
});