CtrlK
BlogDocsLog inGet started
Tessl Logo

spec-requirements

Generate comprehensive requirements definition documents with technology selection and improvement suggestions

Install with Tessl CLI

npx tessl i github:sc30gsw/claude-code-customes --skill spec-requirements
What are skills?

62

Does it follow best practices?

Validation for skill structure

SKILL.md
Review
Evals

Spec Requirements

Generate comprehensive requirements definition documents with technology selection, improvement suggestions, and EARS format acceptance criteria.

Usage

/spec:requirements <system_name> [options]

Options

OptionShortDescriptionExample
--mode-mMode (new-creation/reverse-engineering)-m reverse-engineering
--backlog-bEnable product backlog format--backlog
--epic-eEpic name for backlog structure-e "User Management Epic"
--story-pointsInclude story point estimation--story-points
--app-aApplication name-a "Web Store"
--function-fFunction/feature name-f "Authentication"
--output-oOutput file path-o specs.md
--tech-tTechnology stack-t "react,nodejs,postgresql"
--priority-pPriority level (low/medium/high/critical)-p high
--scope-sScope type (mvp/full/enterprise)-s mvp
--suggestInclude improvement suggestions--suggest
--examplesInclude implementation examples--examples
--templateTemplate type--template agile
--hearingInteractive clarification mode--hearing

Templates

TemplateDescription
standardGeneral purpose with EARS format
agileUser story format with acceptance criteria
waterfallDetailed specification document
product-backlogFull backlog with epics, features, stories

Tool Priorities

ALWAYS prioritize mcp__serena__ tools:

File Operations (Serena MCP First)

  • mcp__serena__find_fileRead (fallback)
  • mcp__serena__search_for_patternGrep (fallback)
  • mcp__serena__list_dirLS (fallback)

Code Analysis (Serena MCP)

  • mcp__serena__get_symbols_overview
  • mcp__serena__find_referencing_symbols

Context7 Integration

For technology documentation:

  • Frontend: React, Vue, Angular
  • Backend: Node.js, Express, FastAPI
  • Database: PostgreSQL, MongoDB, Redis

Modes

New Creation Mode (Default)

Generate requirements from specifications and user input.

Reverse Engineering Mode

Analyze existing codebase to extract requirements:

  1. Component Discovery (controllers, services, models)
  2. Feature Extraction (user-facing functionality)
  3. User Story Generation (features to stories)

EARS Format

Acceptance criteria use EARS (Easy Approach to Requirements Syntax):

  • WHEN [event] THEN [system] SHALL [response]
  • IF [precondition] THEN [system] SHALL [response]
  • WHILE [condition] THE SYSTEM SHALL [behavior]
  • WHERE [context] THE SYSTEM SHALL [behavior]

Examples

# Basic requirements
/spec:requirements "E-commerce Platform" -a "Web Store" -t "react,nodejs"

# MVP with suggestions
/spec:requirements "Social Media App" -s mvp --suggest

# Interactive hearing mode
/spec:requirements "Mobile App" --hearing

# Reverse engineering with backlog
/spec:requirements "User Management" -m reverse-engineering -b -e "Auth Epic"

# Full enterprise with examples
/spec:requirements "CRM System" -s enterprise -t "react,nodejs,postgresql" --examples

Output Structure

  1. Header Information: Timestamp, system name, priority, scope
  2. Functional Requirements: Core features, user scenarios (EARS format)
  3. Non-Functional Requirements: Performance, security, availability
  4. Technical Specifications: Architecture, tech stack, integrations
  5. Additional Sections: Examples, suggestions (if enabled)
Repository
sc30gsw/claude-code-customes
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.