How do I install the Spec Interview skill?

Run npx skillmds add majiayu000/spec-interview-3 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Spec Interview skill do?

Collects missing spec inputs and synchronizes answers into `spec.yaml`. Use when review-spec leaves unresolved specification fields. It is listed under Coding & Dev Tools on SkillMD.

Is Spec Interview safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Interview?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Interview free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Interview?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Interview by majiayu000 — Agent Skill

Name: Spec Interview
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Follow feature-dev-aidd:aidd-core.

Steps

Set active stage spec-interview and active feature.
Run python3 ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/runtime/spec_interview.py --ticket <ticket>.
Run subagent feature-dev-aidd:spec-interview-writer.
Use AskUserQuestionTool to gather missing spec details; update aidd/docs/spec/<ticket>.spec.yaml.
If answers arrive, sync them into the spec and AIDD:OPEN_QUESTIONS/AIDD:DECISIONS as needed.
Return the output contract and next step /feature-dev-aidd:tasks-new <ticket>.

Command contracts

`python3 ${CLAUDE_PLUGIN_ROOT}/skills/spec-interview/runtime/spec_interview.py`

When to run: as canonical spec interview entrypoint after review-spec and before tasklist derivation.
Inputs: --ticket <ticket> with current PRD/plan context and optional notes.
Outputs: updated spec.yaml, synchronized open questions/decisions, and stage status.
Failure mode: non-zero exit when required source artifacts are missing or spec contract is violated.
Next action: gather missing inputs/answers, then rerun the same command.

Notes

Use the aidd-core question format.
Planning stage: AIDD:ACTIONS_LOG: n/a.
Canonical stage name: spec-interview (legacy alias spec normalizes to spec-interview).

Additional resources

Spec template source: templates/spec.template.yaml (when: creating or reconciling spec structure; why: keep generated spec.yaml aligned with canonical schema).

Frequently asked questions