sc30gsw/spec-requirements
skills/spec-requirements/SKILL.md
Generate comprehensive requirements definition documents with technology selection and improvement suggestions
$ install --global
skillsauthnpx skillsauth add sc30gsw/claude-code-customes spec-requirementsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 19, 2026, 6:36 AM152.0s1 file scanned
SKILL.md
- name:
- spec-requirements
- description:
- Generate comprehensive requirements definition documents with technology selection and improvement suggestions
Spec Requirements
Generate comprehensive requirements definition documents with technology selection, improvement suggestions, and EARS format acceptance criteria.
Usage
/spec:requirements <system_name> [options]
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 |
Templates
| 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 |
Tool Priorities
ALWAYS prioritize mcp__serena__ tools:
File Operations (Serena MCP First)
mcp__serena__find_file→Read(fallback)mcp__serena__search_for_pattern→Grep(fallback)mcp__serena__list_dir→LS(fallback)
Code Analysis (Serena MCP)
mcp__serena__get_symbols_overviewmcp__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:
- Component Discovery (controllers, services, models)
- Feature Extraction (user-facing functionality)
- 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
- Header Information: Timestamp, system name, priority, scope
- Functional Requirements: Core features, user scenarios (EARS format)
- Non-Functional Requirements: Performance, security, availability
- Technical Specifications: Architecture, tech stack, integrations
- Additional Sections: Examples, suggestions (if enabled)
Related Skills
sc30gsw/skill-creator
tools
VerifiedTrustedCommunity
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
10SKILL.mdUpdated May 30, 2026
sc30gsw/skills/sdd-workflow
testing
VerifiedTrustedCommunity
# sdd-workflow — Workflow Status Dashboard ## Slash Command ``` /sdd-workflow [slug] ``` ## Purpose Read-only meta skill. Displays the current state of the SDD workflow — which phases are complete, which is next, and any blockers. Does NOT modify any files. --- ## This Skill is Read-Only `sdd-workflow` never writes to or modifies any file. It only reads spec files and git history to report status. There is no approval gate for this skill. --- ## Usage: Specific Feature ``` /sdd-workflo
10SKILL.mdUpdated May 30, 2026
sc30gsw/skills/sdd-tasks
content-media
VerifiedTrustedCommunity
# sdd-tasks **Slash command**: `/sdd-tasks <slug>` **Purpose**: Generate `tasks.md` (TASK-001..N) and `progress.md` from `requirements.md` and `design.md`. --- ## Prerequisites - `.claude/specs/<slug>/requirements.md` must exist - `.claude/specs/<slug>/design.md` must exist (run `/sdd-design` first) --- ## Steps ### 1. Read spec inputs ``` .claude/specs/<slug>/requirements.md .claude/specs/<slug>/design.md ``` Extract: - Every REQ-XXX ID with its acceptance criteria - Every design sect
10SKILL.mdUpdated May 30, 2026
sc30gsw/skills/sdd-review
development
VerifiedTrustedCommunity
# sdd-review — Post-Implementation Code Review ## Slash Command ``` /sdd-review <slug> ``` ## Purpose Run code review and security review on all changes introduced by the feature branch. Append structured findings to `review.md`. Does NOT auto-apply fixes — only proposes them. --- ## Prerequisites - `sdd-impl` has completed: all tasks in `progress.md` are `done` (or at least one is `done`; partial reviews are allowed). - The feature branch must have at least one commit ahead of `main`. -
10SKILL.mdUpdated May 30, 2026