user-spec-planning

Generate an approved user-spec.md via adaptive interviews and codebase analysis.

12|2|Updated Feb 2, 2020
One-click install
npx skills add https://github.com/servitola/dotfiles --skill user-spec-planning-servitola
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-spec-planning
Source: https://github.com/servitola/dotfiles/tree/main/claude-code/skills/user-spec-planning
Command: npx skills add https://github.com/servitola/dotfiles --skill user-spec-planning-servitola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates a structured user-spec.md by conducting adaptive interviews, scanning the codebase, and applying dual validation to ensure a clear, approvable spec.

Core Features & Use Cases

  • Adaptive interview workflow to elicit comprehensive user requirements in a structured manner.
  • Codebase-informed planning by extracting relevant context from the repository to shape the spec.
  • Dual validation & approval to verify feasibility and stakeholder alignment, resulting in an approved user-spec.md.
  • Output discipline writes to work/{feature}/user-spec.md with status approved after successful validation.

Quick Start

Run the User Spec Planning skill to generate work/{feature}/user-spec.md and start the adaptive interview workflow.

Frequently Asked Questions about user-spec-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a user spec for a new feature through an interview?▼

To generate a user spec, conduct an adaptive interview workflow that elicits requirements, scans your codebase for context, and applies dual validation to produce a structured user-spec.md file ready for stakeholder approval.

What is the best way to gather feature requirements from stakeholders using adaptive interviews?▼

Adaptive interviews gather feature requirements by dynamically adjusting questions based on prior answers and codebase context, ensuring comprehensive discovery while structuring outputs into a validated user-spec.md document with approved status.

Does user spec planning support writing documentation in Russian?▼

Yes, user spec planning supports a Russian interview style, allowing you to conduct requirements discovery and generate structured feature documentation in Russian for stakeholder review and approval.

How do you validate feature documentation against a codebase before approval?▼

Feature documentation undergoes dual validation, which checks stakeholder alignment and technical feasibility by extracting relevant context from the repository, ensuring the final user-spec.md is fully validated before receiving an approved status.

Where does the feature planning workflow save the final requirements document?▼

The feature planning workflow saves the final requirements document directly into a work folder, specifically writing to the path work/{feature}/user-spec.md, including frontmatter-driven metadata and an approved status upon successful validation.

Do I need any external dependencies to run the feature requirements interview?▼

No external dependencies are required to run the feature requirements interview, as the workflow operates independently to analyze your codebase, conduct adaptive interviews, and output the validated user-spec.md document.