What is the primary purpose of the Spec skill?

The Spec skill is designed to handle requirements discovery when the project scope is unclear. It uses a structured interview to generate a detailed specification document rather than executable code.

Where does the skill store the generated specifications?

It generates timestamped markdown files in the /tmp directory (e.g., /tmp/spec-YYYYMMDD-name.md), ensuring that every session creates a unique, non-overwriting record.

Does this skill require other plugins?

For full functionality involving codebase research, it recommends the vibe-workflow codebase-explorer and web-researcher agents, though it can proceed with manual research if they are unavailable.

How does the interview process handle complex technical dependencies?

The skill uses an 'unbounded loop' of research and questioning. As new dependencies are discovered via codebase exploration or user input, it dynamically adds new todos to ensure every edge case is addressed before finalizing the spec.

Structured Requirements Discovery

Name: Structured Requirements Discovery
Author: doodledood

bydoodledood

•

Productivity & Workflow

Guides users through a structured discovery interview to transform vague ideas into detailed requirement specifications.

About

The Spec skill acts as a Senior Product Manager within your Claude Code environment, facilitating a rigorous discovery process to define the 'What' and 'Why' of any project. By leveraging agentic codebase exploration and web research, it uncovers hidden dependencies, edge cases, and technical constraints that users might overlook. It iteratively builds a comprehensive markdown specification and interview log, providing a solid foundation for the technical planning and implementation phases of development.

Key Features

Interactive discovery interviews using structured multi-choice and open-ended questions
Automated codebase analysis via codebase-explorer to identify existing patterns and constraints
Contextual web research integration for industry standards and external domain knowledge
Dynamic todo list tracking that evolves as new requirements and complexities are revealed
Iterative specification generation with persistent interview logging and versioning
8 GitHub stars

Use Cases

Conducting external market research or vendor analysis for architectural decision-making
Defining the scope and functional requirements for a new feature before writing code
Gathering context and defining success criteria for complex bug fixes or refactors

About

Key Features

Interactive discovery interviews using structured multi-choice and open-ended questions
Automated codebase analysis via codebase-explorer to identify existing patterns and constraints
Contextual web research integration for industry standards and external domain knowledge
Dynamic todo list tracking that evolves as new requirements and complexities are revealed
Iterative specification generation with persistent interview logging and versioning
8 GitHub stars

Use Cases

Conducting external market research or vendor analysis for architectural decision-making
Defining the scope and functional requirements for a new feature before writing code
Gathering context and defining success criteria for complex bug fixes or refactors