Requirement Analysis

Skill Profile

(Select at least one profile to enable specific modules)

[ ] DevOps
[x] Backend
[ ] Frontend
[ ] AI-RAG
[ ] Security Critical

Overview

Requirement analysis is process of defining, documenting, and maintaining requirements throughout a software project. This skill covers requirement types (functional, non-functional, business, technical), gathering techniques (interviews, workshops, surveys, prototyping), user stories vs use cases, acceptance criteria definition, MoSCoW prioritization, requirements documentation, traceability matrices, validation and verification, change management, and best practices for effective requirement management.

Why This Matters

Clear Direction: Well-defined requirements provide roadmap for development
Stakeholder Alignment: Documentation ensures all stakeholders share common understanding
Quality Assurance: Testable requirements enable verification and validation
Change Control: Traceability enables impact analysis for changes
Success Measurement: Defined acceptance criteria enable objective verification

Core Concepts & Rules

1. Core Principles

Follow established patterns and conventions
Maintain consistency across codebase
Document decisions and trade-offs

2. Implementation Guidelines

Start with the simplest viable solution
Iterate based on feedback and requirements
Test thoroughly before deployment

Inputs / Outputs / Contracts

Inputs:
- Business requirements and objectives
- Stakeholder information
- User feedback and research
- Technical constraints
- Regulatory requirements
Entry Conditions:
- Project is approved
- Key stakeholders identified
- Initial requirements gathered
- Requirements tool configured (Jira, Confluence)
Outputs:
- Software Requirements Specification (SRS)
- User stories and use cases
- Acceptance criteria
- Requirements traceability matrix
- Change request process
Artifacts Required (Deliverables):
- Requirements document
- User story backlog
- Use case specifications
- Acceptance criteria for each story
- Traceability matrix
- Change request template
Acceptance Evidence:
- Stakeholder approval of requirements
- All requirements have acceptance criteria
- Traceability matrix established
- Change control process defined
Success Criteria:
- Requirements approved by stakeholders
- All requirements are testable
- Traceability established from requirements to tests
- Change control process implemented
- Requirements document complete and accessible

Skill Composition

Depends on: agile-scrum, user-stories
Compatible with: project-planning, technical-specifications, risk-management
Conflicts with: Pure discovery-driven approaches with minimal documentation
Related Skills: integration-testing, e2e-playwright

Quick Start / Implementation Example

Review requirements and constraints
Set up development environment
Implement core functionality following patterns
Write tests for critical paths
Run tests and fix issues
Document any deviations or decisions

# Example implementation following best practices
def example_function():
    # Your implementation here
    pass

Assumptions / Constraints / Non-goals

Assumptions:
- Development environment is properly configured
- Required dependencies are available
- Team has basic understanding of domain
Constraints:
- Must follow existing codebase conventions
- Time and resource limitations
- Compatibility requirements
Non-goals:
- This skill does not cover edge cases outside scope
- Not a replacement for formal training

Compatibility & Prerequisites

Supported Versions:
- Python 3.8+
- Node.js 16+
- Modern browsers (Chrome, Firefox, Safari, Edge)
Required AI Tools:
- Code editor (VS Code recommended)
- Testing framework appropriate for language
- Version control (Git)
Dependencies:
- Language-specific package manager
- Build tools
- Testing libraries
Environment Setup:
- .env.example keys: API_KEY, DATABASE_URL (no values)

Test Scenario Matrix (QA Strategy)

Technical Guardrails & Security Threat Model

1. Security & Privacy (Threat Model)

Top Threats: Injection attacks, authentication bypass, data exposure

[ ] Data Handling: Sanitize all user inputs to prevent Injection attacks. Never log raw PII
[ ] Secrets Management: No hardcoded API keys. Use Env Vars/Secrets Manager
[ ] Authorization: Validate user permissions before state changes

2. Performance & Resources

[ ] Execution Efficiency: Consider time complexity for algorithms
[ ] Memory Management: Use streams/pagination for large data
[ ] Resource Cleanup: Close DB connections/file handlers in finally blocks

3. Architecture & Scalability

[ ] Design Pattern: Follow SOLID principles, use Dependency Injection
[ ] Modularity: Decouple logic from UI/Frameworks

4. Observability & Reliability

[ ] Logging Standards: Structured JSON, include trace IDs request_id
[ ] Metrics: Track error_rate, latency, queue_depth
[ ] Error Handling: Standardized error codes, no bare except
[ ] Observability Artifacts:
- Log Fields: timestamp, level, message, request_id
- Metrics: request_count, error_count, response_time
- Dashboards/Alerts: High Error Rate > 5%

Agent Directives & Error Recovery

(ข้อกำหนดสำหรับ AI Agent ในการคิดและแก้ปัญหาเมื่อเกิดข้อผิดพลาด)

Thinking Process: Analyze root cause before fixing. Do not brute-force.
Fallback Strategy: Stop after 3 failed test attempts. Output root cause and ask for human intervention/clarification.
Self-Review: Check against Guardrails & Anti-patterns before finalizing.
Output Constraints: Output ONLY the modified code block. Do not explain unless asked.

Definition of Done (DoD) Checklist

[ ] Tests passed + coverage met
[ ] Lint/Typecheck passed
[ ] Logging/Metrics/Trace implemented
[ ] Security checks passed
[ ] Documentation/Changelog updated
[ ] Accessibility/Performance requirements met (if frontend)

Anti-patterns / Pitfalls

⛔ Don't: Log PII, catch-all exception, N+1 queries
⚠️ Watch out for: Common symptoms and quick fixes
💡 Instead: Use proper error handling, pagination, and logging

Reference Links & Examples

Internal documentation and examples
Official documentation and best practices
Community resources and discussions

Versioning & Changelog

Version: 1.0.0
Changelog:
- 2026-02-22: Initial version with complete template structure