メニュー
Ideation domain specialist: Lean Canvas assembly, SPEC decomposition list extraction, and Diverge-Converge pipeline for product proposal generation. Use during /moai brain Phase 2 (Diverge), Phase 4 (Converge), and Phase 6 (Proposal).
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/TuYv/ccpm --skill moai-domain-ideationコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
| name | moai-domain-ideation |
| description | Ideation domain specialist: Lean Canvas assembly, SPEC decomposition list extraction, and Diverge-Converge pipeline for product proposal generation. Use during /moai brain Phase 2 (Diverge), Phase 4 (Converge), and Phase 6 (Proposal). |
| when_to_use | Use during /moai brain ideation: Lean Canvas assembly, SPEC decomposition-list extraction, diverge/converge brainstorming, proposal generation, and structured idea exploration. |
| license | Apache-2.0 |
| compatibility | Designed for Claude Code |
| allowed-tools | Read, Write, Edit, Grep, Glob |
| user-invocable | false |
| metadata | {"version":"1.0.0","category":"domain","status":"active","updated":"2026-05-04","modularized":"false","tags":"ideation, lean-canvas, diverge-converge, spec-decomposition, proposal, brain","related-skills":"moai-foundation-thinking, moai-domain-design-handoff, moai-domain-research"} |
| progressive_disclosure | {"enabled":true,"level1_tokens":100,"level2_tokens":5000} |
Thin orchestrator for the Diverge-Converge ideation pipeline. Delegates creative framework execution to moai-foundation-thinking and adds artifact-shaping logic specific to the brain workflow: Lean Canvas section assembly and SPEC Decomposition List extraction.
Core responsibilities:
ideation.md with all 9 blocksproposal.md with SPEC Decomposition Candidates sectionKey invariants:
- SPEC-{DOMAIN}-{NUM}: {scope} (see anchor below)Foundation reuse:
moai-foundation-thinking modules/diverge-converge.md (Diverge phase)moai-foundation-thinking modules/diverge-converge.md (Converge phase)moai-foundation-thinking modules/critical-evaluation.mdInvoke moai-foundation-thinking Diverge-Converge framework (Diverge phase):
Generate 5-15 divergent angles for the idea. Each angle explores a different lens:
For each angle, produce a one-sentence concept label.
Cluster related angles by affinity (max 5 clusters).
In-memory concept map. NOT persisted to disk at this phase — convergence in Phase 4 determines what is written.
[HARD] During divergence, do NOT anchor any angle to a specific programming language or framework. Describe capabilities, not implementations:
.moai/project/brand/brand-voice.mdInvoke moai-foundation-thinking Diverge-Converge framework (Converge phase) to reduce 5-15 angles to the single most defensible product concept.
Then assemble the Lean Canvas.
Populate each block for the converged concept. Every block MUST be present, even if sparse. Empty blocks get placeholder: [TBD — to be refined with user research].
## Lean Canvas
### Problem
[Top 3 problems this product solves for the target customer]
### Customer Segments
[Specific user personas — who has the problem most acutely?]
### Unique Value Proposition
[Single, clear, compelling message — why this over alternatives]
### Solution
[Top 3 features / capabilities that address the problems]
### Channels
[How the product reaches customers: direct, marketplace, viral, partnerships]
### Revenue Streams
[How value is monetized: subscription, freemium, per-use, enterprise license, API]
### Cost Structure
[Main cost drivers: infrastructure, people, acquisition, support]
### Key Metrics
[The numbers that tell you the product is succeeding — leading and lagging indicators]
### Unfair Advantage
[What is genuinely hard for competitors to copy? Network effect, data, brand, IP, team]
[HARD] The Solution block describes WHAT the product does, not HOW it is built:
Write ideation.md to .moai/brain/IDEA-NNN/:
# Idea: {user's original idea, verbatim}
*Session: {date}*
## Lean Canvas
[9 blocks as specified above]
After Phase 5 executes (managed by moai-foundation-thinking critical-evaluation.md), append the evaluation report to the existing ideation.md:
## Evaluation Report
### Strengths
[Evidence-backed strengths from critical evaluation]
### Weaknesses
[Identified gaps, assumptions, and risks]
### First Principles Validation
[First principles breakdown per moai-foundation-thinking/modules/first-principles.md]
### Verdict
[Proceed / Proceed with caveats / Revisit / Abandon — with rationale]
ideation.md with Lean Canvas + Evaluation ReportTranslate the converged product concept into actionable SPEC candidates. Each candidate represents a discrete, independently-implementable unit of work.
[HARD] SPEC domain labels MUST be generic capability terms, never technology/language names:
| Correct (capability-based) | Wrong (technology-based) |
|---|---|
SPEC-AUTH-001 | SPEC-OAUTH2-001 |
SPEC-API-001 | SPEC-FASTAPI-001 |
SPEC-PIPELINE-001 | SPEC-AIRFLOW-001 |
SPEC-UI-001 | SPEC-REACT-001 |
SPEC-DB-001 | SPEC-POSTGRES-001 |
SPEC-NOTIFY-001 | SPEC-FIREBASE-001 |
SPEC-SEARCH-001 | SPEC-ELASTICSEARCH-001 |
Suggest 2-10 SPEC candidates. Each candidate should:
If the idea is very small (single capability), 2-3 candidates is appropriate. If the idea is large, suggest 7-10 candidates and note that ordering matters.
If the idea seems too atomic for SPEC decomposition:
### SPEC Decomposition Candidates with note "Idea scope is atomic — consider direct /moai plan instead of /moai brain decomposition"Write proposal.md to .moai/brain/IDEA-NNN/:
# Proposal: {product name or concept label}
*Generated: {date} | Idea: IDEA-NNN*
## Product Summary
{2-3 sentence summary derived from Lean Canvas UVP + Solution blocks}
## Target User
{From Lean Canvas Customer Segments block}
## Core Problems Solved
{From Lean Canvas Problem block, formatted as numbered list}
## Proposed Solution
{From Lean Canvas Solution block — capabilities only, no tech stack}
## SPEC Decomposition Candidates
{2-10 bullets, each matching the canonical grammar below}
- SPEC-{DOMAIN}-001: {one-line scope description}
- SPEC-{DOMAIN}-002: {one-line scope description}
...
## Recommended Execution Order
{Numbered list of SPEC IDs in dependency order, with brief rationale}
## Out of Scope (v0.1)
{Explicit exclusions deferred to later SPECs or a v0.2 phase}
## Notes
{Any caveats, open questions, or assumptions from the evaluation}
The ### SPEC Decomposition Candidates section MUST follow this exact grammar:
- SPEC-{DOMAIN}-{NUM}: {scope}
Where:
{DOMAIN} is uppercase alphanumeric (e.g., AUTH, API, UI, DB, NOTIFY){NUM} is zero-padded 3 digits (e.g., 001, 002, 010){scope} is a plain English one-line description (no backticks, no nested lists)The /moai plan --from-brain parser uses this regex: ^- SPEC-[A-Z][A-Z0-9]+-[0-9]{3}: .+$
Any bullet NOT matching this pattern is excluded from the suggestion list (surfaced as a warning, not an error).
moai-foundation-thinking: Diverge-Converge, Critical Evaluation, First Principles modulesmoai-domain-research: Feeds research.md content into Converge phase contextmoai-domain-design-handoff: Consumes proposal.md product summary for prompt.md context sectionmoai-workflow-brain: Orchestrates this skill across phases 2, 4, 5 (append), and 6| Rationalization | Reality |
|---|---|
| "The user mentioned Python, so SPEC-PYTHON-001 is clearer" | Technology names in SPEC IDs create language lock-in. Use SPEC-API-001 — the technology choice happens at /moai plan time. |
| "The Solution block needs a tech stack to be concrete" | Solution describes WHAT the system does. HOW is deferred to architecture phase. "Processes 10K events/sec" is concrete without naming a framework. |
| "5 SPEC candidates is too few for a complex idea" | Start with 5-7 high-level candidates. /moai plan will decompose each one further if needed. |
| "I should skip the Lean Canvas for a simple idea" | Every brain invocation produces a Lean Canvas. The Customer Segments block alone is worth the exercise — it forces explicit user definition. |
### SPEC Decomposition Candidates heading- SPEC-{DOMAIN}-{NUM}: {scope}