How do I install the Interview Openspec skill?

Run npx skillmds add tools-only/interview-openspec 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 Interview Openspec skill do?

Create OpenSpec artifacts (proposal, specs, design, tasks) through Socratic interview. Use when starting a new OpenSpec change that needs structured requirements elicitation. It is listed under Coding & Dev Tools on SkillMD.

Is Interview Openspec 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 Interview Openspec?

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 Interview Openspec free to use?

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

Who published Interview Openspec?

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

Interview Openspec by tools-only — Agent Skill

Name: Interview Openspec
Rating: 4.5 (4 reviews)
Author: tools-only

File contents

OpenSpec Interview

Phased Socratic interview that produces OpenSpec artifacts incrementally. Each phase maps to one artifact; user may exit after any phase.

Steps

If $ARGUMENTS is empty, use AskUserQuestion to ask what to build. Derive kebab-case name.
Run openspec new change "<name>" and openspec status --change "<name>" --json.
Read resources/INTERVIEW_PRINCIPLES.md and resources/OPENSPEC_INTERVIEW_DIMENSIONS.md.
Execute 4 interview phases. Each phase: ask via AskUserQuestion (2-4 convergent options), then write artifact. If user says "skip", advance with gathered info.
- Phase 1 → proposal.md: Business goals, MVP scope, risk preview, capability identification.
- Phase 2 → specs/<cap>/spec.md: Requirements per capability in WHEN/THEN scenarios (ADDED/MODIFIED/REMOVED).
- Phase 3 → design.md: Technical decisions, architecture tradeoffs (Context/Goals/Non-Goals/Decisions).
- Phase 4 → tasks.md: Implementation breakdown as hierarchical checkbox list.
Use openspec instructions <artifact> --change "<name>" --json before writing each artifact. Fallback: resources/ARTIFACT_TEMPLATES.md.
If high-risk operations detected, read resources/RISK_PROTECTION.md and get explicit authorization.
On completion, run openspec status --change "<name>". Guide user to /opsx:apply or /opsx:verify. See resources/EXAMPLES.md for a full walkthrough.

Constraints

Double-quote paths, use / separator. Prefer rg over grep.
Never auto-execute Git write operations (commit, push).
All questions via AskUserQuestion with clickable options — no plain-text A/B/C.

Frequently asked questions