一键导入
intent-capture
Capture user intent through guided conversation. Exploratory phase with high degrees of freedom.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Capture user intent through guided conversation. Exploratory phase with high degrees of freedom.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Execute work items based on their assigned mode (autopilot, confirm, validate). Supports single-item and multi-item (batch/wide) runs.
Generate implementation walkthrough for human review after run completion. Documents decisions, changes, and verification steps.
Multi-perspective idea evaluation using Six Hats analysis, impact/feasibility scoring, and collaborative shortlisting.
Shape top ideas into actionable concept briefs using Disney Strategy — Dream, Reality, Critique.
Rapid idea generation with cross-domain diversity, anti-bias enforcement, and deep thinking.
Review code written during a run, auto-fix no-brainer issues, and suggest improvements requiring confirmation. Invoked after tests pass.
| name | intent-capture |
| description | Capture user intent through guided conversation. Exploratory phase with high degrees of freedom. |
| version | 1.0.0 |
<degrees_of_freedom> HIGH — This is a creative, exploratory phase. Ask open-ended questions. Don't constrain prematurely. </degrees_of_freedom>
NEVER assume requirements — ALWAYS ask clarifying questions Capture the "what" and "why" — leave the "how" for decomposition Let user describe freely — don't interrupt What do you want to build? Let user describe freely. Don't interrupt. Based on response, ask follow-up questions:<question if="unclear who benefits">
Who is this for? Who will use this feature?
</question>
<question if="unclear problem">
What problem does this solve? What's painful today?
</question>
<question if="unclear scope">
What's the minimum that would be valuable? What can wait?
</question>
<question if="unclear constraints">
Any technical constraints? Existing systems to integrate with?
</question>
<question if="unclear success">
How will you know this is working? What does success look like?
</question>
Let me make sure I understand:
**Goal**: {summarized goal}
**Users**: {who benefits}
**Problem**: {what pain this solves}
**Success Criteria**:
- {criterion 1}
- {criterion 2}
- {criterion 3}
**Constraints**:
- {constraint 1}
- {constraint 2}
Is this accurate? [Y/n/edit]
</output>
<check if="response == n or edit">
<action>Ask specific clarifying questions</action>
<goto step="3"/>
</check>
Create intent ID from title (kebab-case)
Generate intent brief using template: templates/brief.md.hbs
Create directory: .specs-fire/intents/{intent-id}/
Save: .specs-fire/intents/{intent-id}/brief.md
Add intent to state.yaml
Set intent status to "in_progress"
**Intent captured**: "{intent-title}"
Saved to: .specs-fire/intents/{intent-id}/brief.md
---
Ready to break this into work items? [Y/n]
</output>
<check if="response == y">
<invoke_skill>work-item-decompose</invoke_skill>
</check>
<output_artifacts>
| Artifact | Location | Template |
|---|---|---|
| Intent Brief | .specs-fire/intents/{id}/brief.md | ./templates/brief.md.hbs |
| </output_artifacts> |
<success_criteria> User intent fully understood through dialogue Goal, users, problem clearly captured Success criteria defined Constraints identified Intent brief saved to correct location State.yaml updated with new intent </success_criteria>