user-spec-planning

Generates a user-spec.md document via adaptive interview, codebase scanning, and dual validation.

244|75|Updated Dec 22, 2025
One-click install
npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill user-spec-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user-spec-planning
Source: https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/user-spec-planning
Command: npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill user-spec-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of defining user requirements for new features by conducting thorough, AI-guided interviews that incorporate codebase analysis and project knowledge.

Core Features & Use Cases

  • Adaptive Interviewing: Engages users in a structured, multi-cycle interview process to gather detailed requirements.
  • Codebase Integration: Scans the project's codebase to inform interview questions and ensure technical feasibility.
  • Project Knowledge Utilization: Leverages existing project documentation (architecture.md, patterns.md, etc.) to provide context and propose solutions.
  • Dual Validation: Ensures the generated user specification meets quality and adequacy standards through automated checks.
  • Use Case: When a product manager wants to add a new user authentication flow, this Skill will guide them through defining the requirements, considering existing security patterns and code, and producing a clear user-spec.md document.

Quick Start

Use the user-spec-planning skill to create a user specification for a new feature.

Frequently Asked Questions about user-spec-planning

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

FAQPage Schema
How do I gather feature requirements using an AI-driven interview?

Gathering feature requirements via an AI interview involves an adaptive, multi-cycle questioning process that scans your codebase and project documentation to produce a detailed user specification document.

What is the best way to define user stories for new features in an existing codebase?

Defining user stories for existing codebases works best by leveraging project knowledge like architecture patterns to inform technical feasibility, ensuring generated feature definitions integrate with current structures.

Can I use existing project documentation to inform requirement validation?

Yes, existing project documentation like architecture and patterns files can inform requirement validation, providing context for automated checks that ensure specification adequacy and completeness.

Does requirement generation work for bug specifications and refactoring plans?

Requirement generation works for bug specifications and refactoring plans by using iterative questioning and dual validation to capture details and ensure completeness before final user approval.

How are generated user specifications validated for completeness?

Generated user specifications are validated for completeness through a dual validation mechanism performing automated checks against project knowledge and codebase constraints before allowing user approval.

When should I not use an automated interview for requirements gathering?

Avoid using automated interviews for requirements gathering when your project lacks existing documentation or a scannable codebase, as the tool relies on these elements to provide context and validate technical feasibility.