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-requirements62
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Generate comprehensive requirements definition documents with technology selection, improvement suggestions, and EARS format acceptance criteria.
/spec:requirements <system_name> [options]| Option | Short | Description | Example |
|---|---|---|---|
--mode | -m | Mode (new-creation/reverse-engineering) | -m reverse-engineering |
--backlog | -b | Enable product backlog format | --backlog |
--epic | -e | Epic name for backlog structure | -e "User Management Epic" |
--story-points | Include story point estimation | --story-points | |
--app | -a | Application name | -a "Web Store" |
--function | -f | Function/feature name | -f "Authentication" |
--output | -o | Output file path | -o specs.md |
--tech | -t | Technology stack | -t "react,nodejs,postgresql" |
--priority | -p | Priority level (low/medium/high/critical) | -p high |
--scope | -s | Scope type (mvp/full/enterprise) | -s mvp |
--suggest | Include improvement suggestions | --suggest | |
--examples | Include implementation examples | --examples | |
--template | Template type | --template agile | |
--hearing | Interactive clarification mode | --hearing |
| Template | Description |
|---|---|
standard | General purpose with EARS format |
agile | User story format with acceptance criteria |
waterfall | Detailed specification document |
product-backlog | Full backlog with epics, features, stories |
ALWAYS prioritize mcp__serena__ tools:
mcp__serena__find_file → Read (fallback)mcp__serena__search_for_pattern → Grep (fallback)mcp__serena__list_dir → LS (fallback)mcp__serena__get_symbols_overviewmcp__serena__find_referencing_symbolsFor technology documentation:
Generate requirements from specifications and user input.
Analyze existing codebase to extract requirements:
Acceptance criteria use EARS (Easy Approach to Requirements Syntax):
# 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" --examples45a1bdf
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.