القائمة
Generate comprehensive requirements definition documents with technology selection and improvement suggestions
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/diegosouzapw/awesome-omni-skill --skill spec-requirementsيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Token-efficient tracking for AI orchestration. CLI-first for status updates (~50 tokens), agent fallback for complex ops (~1KB). Use when: updating task status, querying blockers, creating progress files, validating phases.
AshAi extension guidelines for integrating AI capabilities with Ash Framework. Use when implementing vectorization/embeddings, exposing Ash actions as LLM tools, creating prompt-backed actions, or setting up MCP servers. Covers semantic search, LangChain integration, and structured outputs.
This skill should be used when solving hard questions, complex architectural problems, or debugging issues that benefit from GPT-5 Pro or GPT-5.1 thinking models with large file context. Use when standard Claude analysis needs deeper reasoning or extended context windows.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | spec-requirements |
| description | Generate comprehensive requirements definition documents with technology selection and improvement suggestions |
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" --examples