skills.rest
cuioss
cuiossCOMMUNITY
Explore all skills by this author →
GitHub

cui-requirements

Generate structured requirements documents and technical specifications.

1|Updated Feb 3, 2025
Search Tags:#quality assurance#documentation#software development#project planning#agile#technical specification#requirements engineering
One-click install
npx skills add https://github.com/cuioss/cui-llm-rules --skill cui-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cui-requirements
Source: https://github.com/cuioss/cui-llm-rules/tree/main/claude/marketplace/skills/cui-requirements
Command: npx skills add https://github.com/cuioss/cui-llm-rules --skill cui-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent, incomplete, or ambiguous project requirements lead to rework, delays, and misaligned development. This Skill standardizes the entire requirements engineering process, ensuring clarity, completeness, and traceability from the outset, saving time and reducing complexity.

Core Features & Use Cases

  • Standardized Requirements: Enforces SMART criteria, clear structure (MUST/SHOULD/MAY), and quality attributes for all requirements documentation.
  • Technical Specification Guidance: Provides templates and rules for architecture, component design, interfaces, and data models.
  • Quality Verification: Includes checklists for completeness, clarity, consistency, and traceability, ensuring high-quality documentation.
  • Use Case: When starting a new feature, use this skill to generate a structured requirements document and a detailed technical specification, ensuring all stakeholders are aligned and development proceeds smoothly, allowing you to focus on implementation.

Quick Start

Create Feature Requirements Document

  1. Document overview and background
  2. Identify functional requirements (MUST/SHOULD/MAY)
  3. Define non-functional requirements (performance, security)
  4. List constraints and dependencies
  5. Define success criteria
  6. Write acceptance criteria (Given/When/Then)
  7. Review with stakeholders

Write Technical Specification

  1. Design architecture and components
  2. Define interfaces and contracts
  3. Document data models
  4. Specify configuration
  5. Describe data flow
  6. Plan error handling
  7. Define testing strategy