一键在 Manus 中运行任何 Skill

开始使用

spec-interview

星标1

分支0

更新时间2026年1月31日 01:36

Interview the user to flesh out feature ideas from the backlog into concrete SPEC.md files

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

kenfdev

kenfdev/figma-event-modeling-plugin

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Spec Interview

You are interviewing the user to turn rough feature ideas from the Feature Backlog into detailed, concrete specifications.

Setup

Read docs/spec.md to understand the project, existing features, and the Feature Backlog section.
Read any existing src/features/*/SPEC.md files that are relevant to the backlog items.
Present the current backlog items to the user and confirm which ones to work on in this session.

Interview

Work through the backlog items. For each idea, interview the user in depth using the AskUserQuestion tool. Cover all of these areas, but skip questions where the answer is obvious from context:

Problem & motivation: What user pain does this solve? When does this come up?
Scope boundaries: What is explicitly in vs. out of scope?
UI & UX: Where does it appear? What does the user see and interact with? What are the states (empty, loading, error, success)?
Data model: What data is stored, where, and in what format? How does it relate to existing plugin data?
Edge cases: What happens with empty input, invalid input, conflicts with existing features?
Technical tradeoffs: Are there multiple implementation approaches? What are the pros/cons?
Dependencies: Which existing features does this depend on or affect?
Acceptance criteria: What concrete checks determine "done"?

Ask follow-up questions when answers are vague. Challenge assumptions. Suggest alternatives when appropriate. Do not ask questions whose answers are already clear from the codebase or existing specs.

Multiple backlog items may consolidate into a single feature or split into multiple features — let the interview determine the right boundaries.

Continue interviewing until all areas are sufficiently covered for each feature.

Output

Once the interview is complete:

Create src/features/<feature-name>/SPEC.md for each finalized feature, following the format used by existing SPEC.md files in the project.
Add rows to the Feature Index table in docs/spec.md for each new feature (Status column left empty).
Remove the corresponding bullet points from the Feature Backlog section in docs/spec.md.

同仓库更多 Skills

同仓库

prepare-task

kenfdev/figma-event-modeling-plugin

TDD test preparation workflow. Use when user says "prepare-task", "/prepare-task", or wants to prepare the next available task. Claims a pending code task, writes tests, and gets user approval before implementation.

2026-02-021

run-task

kenfdev/figma-event-modeling-plugin

Non-interactive workflow for implementing and reviewing claimed tasks. Use when user says "run-task", "/run-task", or wants to run the next implementation/review cycle. Designed to be executed in a shell loop until complete. Handles non-code tasks automatically. Requires tests to be prepared first via /prepare-task for code tasks.

2026-02-021

slice-to-task

kenfdev/figma-event-modeling-plugin

Convert feature slice documents into Claude Code tasks. Reads slice markdown files (containing Type, Description, User Story, Acceptance Criteria, Dependencies, Technical Notes) and creates appropriately-sized tasks using TaskCreate. Use when user says "slice-to-task", "/slice-to-task", wants to convert a slice to tasks, or wants to implement a feature slice. Checks slice dependencies and warns if prerequisites are incomplete.

2026-01-311

Spec Interview

You are interviewing the user to turn rough feature ideas from the Feature Backlog into detailed, concrete specifications.

Setup

Read docs/spec.md to understand the project, existing features, and the Feature Backlog section.

Read any existing src/features/*/SPEC.md files that are relevant to the backlog items.

Present the current backlog items to the user and confirm which ones to work on in this session.

Interview

Work through the backlog items. For each idea, interview the user in depth using the AskUserQuestion tool. Cover all of these areas, but skip questions where the answer is obvious from context:

Problem & motivation: What user pain does this solve? When does this come up?

Scope boundaries: What is explicitly in vs. out of scope?

UI & UX: Where does it appear? What does the user see and interact with? What are the states (empty, loading, error, success)?

Data model: What data is stored, where, and in what format? How does it relate to existing plugin data?

Edge cases: What happens with empty input, invalid input, conflicts with existing features?

Technical tradeoffs: Are there multiple implementation approaches? What are the pros/cons?

Dependencies: Which existing features does this depend on or affect?

Acceptance criteria: What concrete checks determine "done"?

Ask follow-up questions when answers are vague. Challenge assumptions. Suggest alternatives when appropriate. Do not ask questions whose answers are already clear from the codebase or existing specs.

Multiple backlog items may consolidate into a single feature or split into multiple features — let the interview determine the right boundaries.

Continue interviewing until all areas are sufficiently covered for each feature.

Output

Once the interview is complete:

Create src/features/<feature-name>/SPEC.md for each finalized feature, following the format used by existing SPEC.md files in the project.

Add rows to the Feature Index table in docs/spec.md for each new feature (Status column left empty).

Remove the corresponding bullet points from the Feature Backlog section in docs/spec.md.

name	spec-interview
description	Interview the user to flesh out feature ideas from the backlog into concrete SPEC.md files
disable-model-invocation	true