SDLC-Docs-Engine: Standards-Driven Documentation Across the Software Lifecycle

SDLC-Docs-Engine (formerly SRS-Skills) is a modular, AI-driven toolkit for generating comprehensive, standards-compliant documentation across all phases of software development. It supports Waterfall, Agile, and Hybrid methodologies, providing IEEE/ISO-aligned documentation from strategic vision to deployment operations.

Active Projects

The following client projects are maintained under projects/ (gitignored — not committed to this repository). Each project has a full SDLC documentation suite generated by these skills.

Project	Domain	Methodology	AI Module	Status
AcademiaPro	Education SaaS (Uganda-first, pan-Africa)	Hybrid (Water-Scrum-Fall)	AI Module — 5 features (UGX 50K–800K/mo)	Phase 1 gate open — development ready
Medic8	Healthcare SaaS (Africa-first, global)	Hybrid (Water-Scrum-Fall)	AI Clinical Intelligence — 5 features (UGX 200K–1.5M/mo)	Phase 1 gate blocked — 7 HIGH gaps
Kulima	Farm Management SaaS (Uganda-first)	Hybrid (Water-Scrum-Fall)	AI Farm Advisor — 5 features (UGX 30K–300K/mo)	Phase 2 partial — SRS complete
LonghornERP	ERP SaaS (Uganda-first, universal)	Hybrid (Water-Scrum-Fall)	AI Intelligence — 5 features (UGX 100K–800K/mo)	Phase 1 complete — Phase 2 in progress
Maduuka	POS + Bookkeeping SaaS (Africa SMBs)	Hybrid (Water-Scrum-Fall)	AI Business Intelligence — 4 features (UGX 30K–200K/mo)	Full SDLC complete — development ready
BIRDC-ERP	Bespoke Banana Factory ERP (BIRDC/PIBID)	Waterfall (consulting)	AI Intelligence Phase 7 — 5 capabilities (lump-sum extension)	Full SDLC complete — 38 docs delivered

Project files are gitignored per the submodule design. Only the skills, domains, templates, and documentation tooling are committed to this repository. Project DOCUMENTATION-STATUS.md files within each project directory are the authoritative status reference for each engagement.

What's New in v3.6

Requirements Engineering Fundamentals Expanded - Added Business Analysis Planning, Business Process Modeling, Business Rules Analysis, Prototyping and Solution Discovery, and Solution Evaluation and Transition
Phase 03: Design Documentation - Added IoT System Design for connected-device and edge-enabled products
Phase 06: Deployment & Operations - Added Go-Live Readiness for structured launch governance and release decision support
Book-driven gap closure - Reduced major coverage gaps in BA planning, workflow modeling, rule analysis, connected-product design, and launch readiness without restructuring the repository

What's New in v3.3

Phase 04: Development Artifacts - 4 new skills: Technical Specification, Coding Guidelines (IEEE 730), Dev Environment Setup, Contribution Guide (IEEE 1074)
Phase 05: Testing Documentation - 3 new skills: Test Strategy, Test Plan, Test Report (IEEE 829)
Phase 06: Deployment & Operations - 4 new skills: Deployment Guide (IEEE 1062), Runbook (SRE), Monitoring Setup (ISO 25010), Infrastructure Docs (IEEE 1016)
Phase 07: Agile Artifacts - 4 new skills: Sprint Planning, Definition of Done, Definition of Ready, Retrospective Template (Scrum Guide)
Phase 08: End-User Documentation - 4 new skills: User Manual, Installation Guide, FAQ (ISO 26514), Release Notes (IEEE 830)
Phase 09: Governance & Compliance - 4 new skills: Traceability Matrix, Audit Report (IEEE 1012), Compliance Docs (GDPR/HIPAA/SOC2), Risk Assessment (ISO 31000)
100% phase coverage - All 10 SDLC phases fully implemented with 63 documentation skills

What's New in v3.2

Phase 01: Strategic Vision - 3 new skills: Vision Statement (IEEE 29148), PRD (IEEE 29148/1233), Business Case (IEEE 1058)
Phase 02: Agile Track Complete - 3 new skills: Acceptance Criteria, Story Mapping, Backlog Prioritization (IEEE 29148)
Phase 03: Design Documentation - 4 new skills: HLD, LLD (IEEE 1016), API Specification (OpenAPI 3.0), Database Design (IEEE 1016)
Setup Scripts - PowerShell and Bash scripts for bootstrapping new SRS projects

What's New in v3.0

Multi-Methodology Support: Choose Waterfall (IEEE 830 SRS) or Agile (User Stories) pipelines
Expanded Scope: Beyond SRS—now supports PRDs, HLD/LLD, API docs, test plans, deployment guides, and more
Phase-Based Organization: 10 SDLC phases from strategic vision to governance/compliance
Methodology Detection: New Phase 00 helps select the right documentation approach
Backward Compatible: Existing Waterfall SRS pipeline preserved (moved to 02-requirements-engineering/waterfall/)

📚 Supported Documentation Types

Strategic & Vision Documents (Phase 01)

PRD (Product Requirements Document) - IEEE 29148
Vision Statements
Business Cases
Lean Canvas & Impact Mapping (NEW) - MVP/startup alternative to PRD (decision gate)

Requirements Engineering (Phase 02)

RE Fundamentals (NEW):

Stakeholder Analysis - IEEE 29148, Power/Interest grids, RACI
Elicitation Toolkit - Interviews, JAD, Prototyping, Observation, Surveys
BRD Generation (optional) - Business Requirements Document
Requirements Analysis - Conflict detection, feasibility, prioritization
Conceptual Data Modeling - Entity-relationship from business language
Requirements Patterns - Decision tables, state transitions, CRUD matrices
Requirements Validation - Reviews, inspections, prototype testing
Business Analysis Planning (NEW) - Governance, stakeholder engagement, BA approach
Business Process Modeling (NEW) - Events, workflows, handoffs, decision points
Business Rules Analysis (NEW) - Rule catalogs, ownership, contradictions, fit criteria
Prototyping and Solution Discovery (NEW) - Candidate comparison, prototype strategy, decision support
Requirements Management - Baselining, change control, versioning
Traceability Engineering - Forward/backward trace links
Requirements Metrics - Universal quality gate (GREEN/YELLOW/RED)
Requirements Reuse (optional) - Product line requirements library
Solution Evaluation and Transition (NEW) - Readiness, adoption, organizational transition, outcome evaluation

Waterfall Track:

SRS (Software Requirements Specification) - IEEE 830-1998, IEEE 1233-1998
Use Cases - UML 2.5 standards
Formal Requirements - Stimulus/response patterns

Agile Track:

User Stories - INVEST criteria, IEEE 29148-2018
User Story Maps - Jeff Patton methodology
Product Backlog - Sprint-ready with story points

Design Documentation (Phase 03)

HLD (High-Level Design) - IEEE 1016-2009, scalability patterns (ByteByteGo)
LLD (Low-Level Design) - IEEE 1016-2009
API Specifications - OpenAPI 3.0, advanced API patterns (Geewax)
Database Design - ERDs, schema documentation
UX Specification (NEW) - Information architecture, wireframes, design systems, usability testing
Infrastructure Design (NEW) - Scalability, caching, reliability, monitoring (decision gate)
IoT System Design (NEW) - Device, edge, connectivity, fleet lifecycle, secure operations

Testing Documentation (Phase 05)

Test Strategy - IEEE 829
Test Plans & Test Cases
Test Reports - Defect tracking, coverage metrics

Deployment & Operations (Phase 06)

Deployment Guides - Step-by-step procedures
Runbooks - SRE best practices
Monitoring Documentation
Infrastructure as Code Docs
Go-Live Readiness (NEW) - Launch gates, blocker register, rollback, hypercare

Agile Artifacts (Phase 07)

Sprint Planning Documents
Definition of Done (DoD)
Definition of Ready (DoR)
Retrospective Reports
Burndown/Burnup Charts

End-User Documentation (Phase 08)

User Manuals - ISO 26514
Installation Guides
Troubleshooting FAQs
Release Notes

Governance & Compliance (Phase 09)

Requirements Traceability Matrix - IEEE 1012-2016
Audit Reports - IEEE 1012 V&V
Compliance Documentation - GDPR, HIPAA, SOC2
Risk Assessments

🛠 Supported Standards

IEEE Std 830-1998: Software Requirements Specifications
IEEE Std 1233-1998: System Requirements Development
IEEE Std 610.12-1990: Software Engineering Terminology
IEEE Std 1012-2016: Verification and Validation
IEEE Std 1016-2009: Software Design Descriptions
IEEE Std 29148-2018: Requirements Engineering
IEEE Std 829: Software Test Documentation
ASTM E1340-96: Rapid Prototyping of Computerized Systems
ISO/IEC 15504: Process Assessment Framework
ISO/IEC 25010: Software Product Quality Model
ISO 26514: User Documentation
OpenAPI 3.0: API Documentation

🚀 Integration & Workflow

This repository is architected as a "Stateless Documentation Engine." It provides the logic and templates, while your parent project provides the context.

Starting a New Client Project

Tell Claude: "start a new project"

Claude will:

Invoke superpowers:brainstorming to explore requirements and design
Ask 4 quick questions (project name, description, methodology, client contact)
Deduce the domain automatically from your description
Scaffold projects/<ProjectName>/ with all 9 phase directories
Pre-populate _context/ with your answers
Inject domain-default requirements tagged [DOMAIN-DEFAULT]

Then fill in remaining _context/ files and say: "generate PRD for <ProjectName>" or "generate SRS for <ProjectName>"

To export a finished document to Word: "build the SRS" → outputs SRS_Draft.docx in the phase directory

Installation

Add this project as a submodule in your existing repository:

git submodule add https://github.com/peterbamuhigire/srs-skills.git skills
cd skills
git checkout main

Quick Start

Step 1: Select Your Methodology

Run the methodology detection skill:

Run skill: 00-meta-initialization

This will:

Detect your project type (Waterfall, Agile, Hybrid)
Create projects/<ProjectName>/_context/methodology.md
Generate a documentation roadmap
Activate appropriate pipelines

Step 2: Choose Your Documentation Path

For Waterfall Projects (Traditional SDLC):

flowchart LR
    V[01 Strategic<br/>Vision] --> SRS[02 Waterfall<br/>SRS Pipeline]
    SRS --> D[03 Design<br/>Documentation]
    D --> T[05 Testing<br/>Documentation]
    T --> G[09 Governance<br/>& Compliance]

    style SRS fill:#e1f5ff

Start with: 02-requirements-engineering/waterfall/01-initialize-srs

For Agile Projects (Scrum/Kanban):

flowchart LR
    V[01 Strategic<br/>Vision] --> US[02 Agile<br/>User Stories]
    US --> SP[07 Sprint<br/>Planning]
    SP --> I[Implementation]
    I --> R[Retrospective]

    style US fill:#fff4e1

Start with: 02-requirements-engineering/agile/01-user-story-generation

Step 3: Execute Your Documentation Pipeline

Each phase builds on the previous:

Initialize context (seed projects/<ProjectName>/_context/ with vision, features, tech stack)
Run sequential skills in your chosen pipeline
Generate outputs inside projects/<ProjectName>/... under the active phase/document workspace
Validate with auditing skills (Phase 09)

🗂 Repository Structure

sdlc-docs-engine/
├── 00-meta-initialization/          # Methodology selection & project setup
├── domains/                         # Domain knowledge bases (tracked)
│   ├── INDEX.md
│   ├── healthcare/                  # HIPAA, HL7/FHIR, NFR defaults
│   ├── finance/                     # PCI-DSS, SOX, AML
│   ├── education/                   # FERPA, COPPA
│   ├── retail/                      # PCI-DSS, GDPR
│   ├── logistics/                   # DOT, ISO 28000
│   └── government/                  # FISMA, FedRAMP
├── projects/                        # [UNTRACKED] Per-client project workspaces
│   └── <ProjectName>/
│       ├── _context/                # Project inputs (vision, features, tech stack)
│       └── 01-09 <phases>/          # Generated section files + .docx output
├── scripts/
│   └── build-doc.sh                 # Pandoc: stitch .md sections → .docx
├── templates/
│   └── reference.docx               # [LOCAL ONLY] Word style template
├── 01-strategic-vision/             # PRD, vision statements, business cases, lean canvas
├── 02-requirements-engineering/
│   ├── fundamentals/               # NEW: Methodology-agnostic RE lifecycle (11 skills)
│   │   ├── before/                  # Stakeholder analysis, elicitation, BRD
│   │   ├── during/                  # Analysis, data modeling, patterns, validation
│   │   └── after/                   # Management, traceability, metrics, reuse
│   ├── waterfall/                   # IEEE 830 SRS pipeline (8 phases)
│   │   ├── 01-initialize-srs/
│   │   ├── 02-context-engineering/
│   │   ├── 03-descriptive-modeling/
│   │   ├── 04-interface-specification/
│   │   ├── 05-feature-decomposition/
│   │   ├── 06-logic-modeling/
│   │   ├── 07-attribute-mapping/
│   │   ├── 08-semantic-auditing/
│   │   └── 09-use-case-modeling/    # NEW: UML use cases, activity diagrams
│   └── agile/                       # User stories, story mapping, backlog
│       ├── 01-user-story-generation/
│       ├── 02-acceptance-criteria/
│       ├── 03-story-mapping/
│       └── 04-backlog-prioritization/
├── 03-design-documentation/         # HLD, LLD, API specs, database, UX spec, infrastructure
├── 04-development-artifacts/        # Technical specs, code documentation
├── 05-testing-documentation/        # Test strategy, plans, cases, reports
├── 06-deployment-operations/        # Deployment guides, runbooks, IaC docs
├── 07-agile-artifacts/              # Sprint planning, DoD, DoR, retrospectives
├── 08-end-user-documentation/       # User manuals, installation guides, FAQs
├── 09-governance-compliance/        # Traceability, audits, compliance docs
└── skills/                          # Domain-specific patterns & utilities
    ├── multi-tenant-saas-architecture/
    ├── feature-planning/
    ├── doc-architect/
    ├── mysql-best-practices/
    ├── webapp-gui-design/
    └── [25+ additional skills]

Pathing Model

The canonical runtime model is the project workspace under projects/<ProjectName>/.

Context source of truth: projects/<ProjectName>/_context/
Generated markdown and phase artifacts: projects/<ProjectName>/<phase>/...
Final .docx outputs: projects/<ProjectName>/<phase>/

Many existing skill-local files still use ../project_context/ and ../output/. Those are compatibility aliases used inside skill execution contexts. They are not a second architecture. Root documentation follows the canonical workspace model described in docs/pathing-model.md.

📋 Documentation Pipelines

Waterfall SRS Pipeline (Phase 02)

Best for: Regulated industries, fixed-scope projects, safety-critical systems

Generates: Complete IEEE 830-compliant SRS with 8 sections

Phases:

Initialize context templates
Generate Section 1.0 (Introduction)
Generate Section 2.0 (Overall Description)
Generate Section 3.1 (External Interfaces)
Generate Section 3.2 (Functional Requirements)
Generate Section 3.2.x (Logic & Algorithms)
Generate Sections 3.3-3.6 (Non-Functional Requirements)
Validate & generate Traceability Matrix

Output: canonical project artifacts under projects/<ProjectName>/02-requirements-engineering/... and projects/<ProjectName>/09-governance-compliance/...

👉 Start Waterfall SRS Pipeline

Agile User Story Pipeline (Phase 02)

Best for: Startups, MVPs, iterative projects, Scrum/Kanban teams

Generates: INVEST-compliant user stories with acceptance criteria

Phases:

Generate user stories from features
Refine acceptance criteria (Given-When-Then)
Create story map visualization
Prioritize backlog (MoSCoW/WSJF)

Output: canonical project artifacts under projects/<ProjectName>/02-requirements-engineering/...

👉 Start Agile User Story Pipeline

🤖 AI-Assisted Development Skills (New in v3.1)

Purpose: Skills that make Claude Code better at helping you develop software by enforcing patterns, preventing errors, and optimizing workflows.

Core AI Development Skills

1. ai-assisted-development - Multi-Agent Orchestration

Use when: Coordinating multiple AI agents (Planning, Coding, Testing, Review)

Provides:

5 orchestration strategies (Sequential, Parallel, Conditional, Looping, Retry)
3 AI-specific patterns (Agent Handoff, Fan-Out/Fan-In, Human-in-the-Loop)
Real-world examples from MADUUKA and BRIGHTSOMA projects
30-75% faster development through parallelization

👉 Learn AI Agent Orchestration

2. ai-error-prevention - Trust But Verify Workflow

Use when: Working with Claude to generate code (always!)

Provides:

7 prevention strategies to catch Claude's mistakes early
Common failure modes: Hallucination, Incomplete Solutions, Misunderstanding, Lazy Solutions
App-specific checklists (MADUUKA, MEDIC8, BRIGHTSOMA, DDA, CROWNPOINT)
Saves 50-75% of wasted tokens through early error detection

👉 Learn Error Prevention

3. orchestration-best-practices - The 10 Commandments

Use when: Generating multi-step workflows or complex processes

Provides:

The 10 orchestration rules (steps, dependencies, validation, error handling)
Complete code examples (good vs bad patterns)
Verification checklist
Anti-patterns guide

👉 Learn Orchestration Rules

4. ai-error-handling - 5-Layer Validation Stack

Use when: Validating AI-generated code before production

Provides:

5 validation layers: Syntax, Requirements, Testing, Security, Documentation
Quality scoring system (0-100, threshold >= 80)
Validation loop with max 3 iterations
Automated recovery strategies

👉 Learn Validation Stack

Reference Guides

prompting-patterns-reference.md

10 essential patterns for better AI instructions

Reduces clarification questions by 50%
Improves first-time-right code by 60%
Patterns: Clear Task+Context+Constraints, Chain-of-Thought, Few-Shot Learning, etc.

orchestration-patterns-reference.md

Comprehensive guide for coordinating multiple agents/tasks

5 orchestration types with examples
4 core patterns (Map-Reduce, Pipeline, Fan-Out/Fan-In, Circuit Breaker)
Decision trees and performance analysis

encoding-patterns-into-skills.md

How to create skills that automatically enforce patterns

Formula: Rules + Examples + Checklists + Decision Trees
Pattern encoding templates
Skill iteration strategies

How AI Skills Work Together

REQUEST PREPARATION (ai-error-prevention)
├─ Use prompting patterns (prompting-patterns-reference)
├─ Break into small steps
└─ Clear task + context + constraints

CLAUDE GENERATES CODE

IMMEDIATE VERIFICATION (ai-error-prevention)
├─ Verification-First strategy
├─ Test-Driven Validation
└─ Specification Matching

STRUCTURE CHECK (orchestration-best-practices)
├─ Steps clearly defined?
├─ Dependencies identified?
└─ Error handling present?

VALIDATION (ai-error-handling)
├─ 5-layer validation stack
└─ Quality threshold check (>= 80/100)

ACCEPTANCE OR ITERATION
└─ All checks passed? → USE CODE ✓

Result: Production-ready code, 50-75% fewer wasted tokens, higher quality output

✅ Methodology Selection Guide

When to Use Waterfall SRS Pipeline

✅ YES for:

Regulated industries (FDA, FAA, DOD, medical devices)
Fixed-scope, fixed-price contracts
Safety-critical systems (aerospace, automotive)
Projects requiring IEEE 830/1233 compliance
Formal verification & validation (IEEE 1012)

❌ NO for:

Agile/Scrum projects with evolving requirements
MVPs with high uncertainty
Startups needing rapid iteration

When to Use Agile User Story Pipeline

✅ YES for:

Scrum, Kanban, XP projects
Startups with evolving requirements
MVPs and rapid prototypes
Continuous stakeholder collaboration
Projects with flexible scope

❌ NO for:

Regulated industries requiring comprehensive SRS
Fixed-scope contracts with formal signoffs
Safety-critical systems

Hybrid Approach

You can mix methodologies:

Example 1: Use Waterfall SRS for backend (regulated) + Agile User Stories for frontend (rapid iteration)

Example 2: Use Waterfall for core platform + Agile for new feature experiments

🔁 Iterative Development & Re-running Phases

Idempotency Rule: Most skills are designed to be re-runnable.

When Context Changes

Changed File	Re-run Phases	Reason
`vision.md`	02 (Context/Stories), 09 (Audit)	Vision affects all downstream docs
`features.md`	02 (Requirements), 03 (Design)	New features → new requirements
`tech_stack.md`	03 (Design), 04 (Interfaces)	Tech stack changes affect architecture
`business_rules.md`	06 (Logic Modeling)	Business rules map to algorithms
`quality_standards.md`	07 (NFRs), 05 (Testing)	Quality targets define test criteria

Maintenance Mode

When re-running skills on existing documentation:

Phase 01 has --maintenance flag to add missing templates without overwriting
Phases 02-08 will prompt before overwriting: [APPEND], [PATCH], or [OVERWRITE]
Always re-run Phase 09 (Audit) after any changes to validate consistency

🧠 Design Philosophy

Project-Workspace Targeting: Skills execute within the submodule but target the active project workspace under projects/<ProjectName>/
Standards-Driven Prompts: Every skill maps to specific IEEE/ISO clauses
Engineering over Authorship: Requirements use stimulus-response patterns and logic modeling for verifiability
Methodology-Agnostic Core: Choose Waterfall, Agile, or Hybrid based on project needs
Submodule Portability: The engine is stateless; project-specific data never commits to this submodule
Token Efficiency: 500-line hard limit on all .md files ensures AI comprehension and cost efficiency

📖 Supporting Documentation

CLAUDE.md: AI assistant SOP with V&V procedures, skill usage guidelines
DEPENDENCIES.md: Runtime requirements (Python 3.10+, libraries, environment variables)
docs/CHANGELOG.md: Version history, standards updates, migration notes
skill_overview.md: Input-to-output registry for each skill
PROJECT_BRIEF.md: Quick overview for new users
ARCHITECTURE.md: Technical architecture and design decisions
docs/deterministic-governance.md: Clause-level gate checklist that extends the ISO/IEEE 29119 deterministic model to other phases.

🎯 Example Workflows

Workflow 1: Waterfall Medical Device SRS

# Step 1: Initialize
Run skill: 02-requirements-engineering/waterfall/01-initialize-srs

# Step 2: Populate context files (manually)
Edit `projects/<ProjectName>/_context/vision.md`
Edit `projects/<ProjectName>/_context/features.md`
Edit `projects/<ProjectName>/_context/tech_stack.md`
Edit `projects/<ProjectName>/_context/business_rules.md`
Edit `projects/<ProjectName>/_context/quality_standards.md`
Edit `projects/<ProjectName>/_context/glossary.md`

# Step 3: Generate SRS sections sequentially
Run skill: 02-requirements-engineering/waterfall/02-context-engineering
Run skill: 02-requirements-engineering/waterfall/03-descriptive-modeling
Run skill: 02-requirements-engineering/waterfall/04-interface-specification
Run skill: 02-requirements-engineering/waterfall/05-feature-decomposition
Run skill: 02-requirements-engineering/waterfall/06-logic-modeling
Run skill: 02-requirements-engineering/waterfall/07-attribute-mapping
Run skill: 02-requirements-engineering/waterfall/08-semantic-auditing

# Output: generated SRS artifacts in `projects/<ProjectName>/02-requirements-engineering/...`

Workflow 2: Agile E-commerce Startup

# Step 1: Create PRD and vision
Run skill: 01-strategic-vision/01-prd-generation

# Step 2: Generate user stories
Run skill: 02-requirements-engineering/agile/01-user-story-generation

# Step 3: Create story map
Run skill: 02-requirements-engineering/agile/03-story-mapping

# Step 4: Sprint planning
Run skill: 07-agile-artifacts/01-sprint-planning

# Output: generated Agile artifacts in `projects/<ProjectName>/02-requirements-engineering/...` and `projects/<ProjectName>/07-agile-artifacts/...`

Workflow 3: Hybrid SaaS Platform

# Backend (Regulated, needs formal SRS)
Run skill: 02-requirements-engineering/waterfall/ (full pipeline)

# Frontend (Agile, rapid iteration)
Run skill: 02-requirements-engineering/agile/01-user-story-generation

# Shared Design Documentation
Run skill: 03-design-documentation/01-high-level-design

# Output: SRS for backend, User Stories for frontend, Unified HLD

🔧 Domain-Specific Skills

The skills/ directory contains 25+ reusable domain patterns that integrate with documentation phases:

Architecture Skills

multi-tenant-saas-architecture: Backend isolation, tenant management
modular-saas-architecture: Microservices patterns

Database Skills

mysql-best-practices: MANDATORY for all database work - Schema design, migrations, multi-tenant isolation

Security Skills

dual-auth-rbac: Session + JWT authentication, role-based access control
vibe-security-skill: MANDATORY for web apps - OWASP Top 10, secure coding

UI/UX Skills

webapp-gui-design: Web app UI patterns, responsive design
pos-sales-ui-design: Point-of-sale UI standards

Process Skills

feature-planning: Complete feature planning from spec to implementation
doc-architect: Generate Triple-Layer AGENTS.md documentation

Technology Skills

gis-mapping: OpenStreetMap integration, geofencing
report-print-pdf: PDF generation, auto-print workflows
api-error-handling: Standardized error responses

Usage: Load domain skills alongside phase skills for specialized guidance.

Example:

# Use multi-tenant skill with HLD generation
Run skill: 03-design-documentation/01-high-level-design
+ Reference: skills/multi-tenant-saas-architecture/

🚨 Critical Rules

Database Work (MANDATORY)

All database-related work MUST use skills/mysql-best-practices/

This includes:

Database migrations (tables, columns, indexes)
Schema design and modifications
Stored procedures, triggers, views
Query optimization
Multi-tenant isolation patterns

Failure to follow the migration checklist causes production failures.

Documentation Standards (MANDATORY)

All .md files MUST follow strict formatting:

500-line hard limit - No exceptions
Two-tier structure - High-level TOC + Deep dive docs
Smart subdirectory grouping - Logical organization

See skills/doc-standards.md for complete requirements.

Security Baseline (MANDATORY for Web Apps)

All web application work MUST apply skills/vibe-security-skill/

Security principles are non-negotiable:

Input validation and sanitization
Authentication and authorization
OWASP Top 10 protection
Secure data handling

📊 Verification & Validation (V&V)

IEEE 1012 Evaluation Framework

Every generated document undergoes V&V:

Correctness: Confirms alignment with stakeholder intent
Consistency: Ensures uniform terminology and logic
Completeness: Verifies all edge cases are covered
Verifiability: Confirms deterministic test criteria exist

Audit Execution (Phase 09)

Phase 09 skills perform:

Traceability Verification: Every requirement links to business goals
Logic Scrutiny: Validates all formulas and algorithms
Conflict Resolution: Identifies contradictions between sections
Standards Compliance: Checks IEEE/ISO conformance

Output: Audit_Report.md, Traceability_Matrix.md

🔄 Migration from v2.x

Existing users: The original 8-phase SRS pipeline has been moved to 02-requirements-engineering/waterfall/.

Update Your Workflows

# Old path (deprecated)
01-initialize-srs/

# New path
02-requirements-engineering/waterfall/01-initialize-srs/

Backward Compatibility

Legacy entry points still work but will show deprecation notices:

# 01-initialize-srs (DEPRECATED)
Use: 02-requirements-engineering/waterfall/01-initialize-srs

See docs/MIGRATION_V2_TO_V3.md for complete migration guide.

📈 Roadmap

v3.6.0 (Current - 2026-04-13)

Requirements fundamentals expanded with 5 new skills covering BA planning, process modeling, business rules, prototyping, and transition
Phase 03 extended with IoT System Design
Phase 06 extended with Go-Live Readiness
Added book-driven gap-closure analysis in docs/2026-04-13-book-driven-gap-closure.md
Expanded SDLC-engine coverage across all 10 phases without restructuring the repository

v3.5.0 (2026-03-08)

Design Documentation Enhancement: 5 new skills + 9 reference files + 5 existing skill enhancements
Phase 03: UX Specification (IA, wireframes, design systems), Infrastructure Design (scalability, caching, reliability)
Phase 02: Use Case Modeling (UML use cases, activity diagrams) for waterfall pipeline
Phase 01: Lean Canvas & Impact Mapping (MVP/startup alternative to PRD)
New cross-cutting skill: Cognitive UX Framework (Six Minds, cognitive walkthroughs)
Enhanced HLD with scalability patterns (ByteByteGo), API Spec with advanced patterns (Geewax)
Sources: ByteByteGo, Dennis/Wixom/Tegarden, Whalen, Effective Product Designer, Geewax, BA Methodology Book
63 total documentation generation skills across 10 SDLC phases

v3.4.0 (2026-03-07)

Requirements Engineering Fundamentals: 11 new methodology-agnostic RE skills
Before/During/After lifecycle wrapping both Waterfall and Agile pipelines
Stakeholder Analysis, Elicitation Toolkit, BRD Generation, Requirements Analysis, Conceptual Data Modeling, Requirements Patterns, Validation, Management, Traceability Engineering, Metrics & Quality Gates, Requirements Reuse
Sources: Laplante, Wiegers & Beatty, Leffingwell, Business Requirements & Data Architecture
57 total documentation generation skills across 10 SDLC phases

v3.3.0 (2026-03-01)

Phase 04-09: 23 new documentation skills completing 100% phase coverage
Development Artifacts, Testing, Deployment, Agile, End-User, Governance phases
46 total documentation generation skills across 10 SDLC phases

v3.2.0 (2026-02-28)

Phase 01: Strategic Vision skills (Vision Statement, PRD, Business Case)
Phase 02: Agile track completion (Acceptance Criteria, Story Mapping, Backlog Prioritization)
Phase 03: Design Documentation skills (HLD, LLD, API Specification, Database Design)
Setup scripts for new project bootstrapping (PowerShell + Bash)

v3.1.0 (2026-02-07)

AI-Assisted Development Skills (4 skills + 3 reference guides)
Token efficiency improvements (50-75% savings)

v3.0.0 (2026-02-06)

Multi-methodology support (Waterfall + Agile)
Reorganized phase structure (00-09)
Agile user story generation skill

v4.0.0 (Planned - Q3 2026)

⏳ Automated doc generation from code (API docs, schema docs)
⏳ Integration with CI/CD pipelines
⏳ Multi-language support (docs in Spanish, French, etc.)

🤝 Contributing

We welcome contributions! To add or improve skills:

Review existing skills for format and structure
Follow the skills/skill-writing/ meta-skill guidelines
Ensure 500-line limit and two-tier documentation structure
Add examples and anti-patterns
Update README.md and PROJECT_BRIEF.md
Submit PR with clear description

See skills/claude-guides/skill-creation-workflow.md for detailed workflow.

📄 License

This project is licensed under the MIT License. See LICENSE.txt for details.

💬 Support

Issues: https://github.com/peterbamuhigire/srs-skills/issues
Discussions: https://github.com/peterbamuhigire/srs-skills/discussions
Documentation: See CLAUDE.md for AI assistant guidance

🙏 Acknowledgments

This project builds on industry standards:

IEEE Computer Society for SRS and V&V standards
Agile Alliance for user story best practices
Bill Wake for INVEST criteria
Jeff Patton for story mapping methodology
ISO/IEC for quality and process standards

Built with precision. Powered by standards. Designed for portability.

Maintained by: Peter Bamuhigire Version: 3.6.0 Last Updated: 2026-04-13

Quick Reference

Task	Command	Output
Waterfall SRS	`02-requirements-engineering/waterfall/01-initialize-srs`	IEEE 830 SRS
Agile User Stories	`02-requirements-engineering/agile/01-user-story-generation`	User story backlog
Methodology Selection	`00-meta-initialization`	Documentation roadmap
Design Docs	`03-design-documentation/01-high-level-design`	HLD, architecture diagrams
Traceability	`09-governance-compliance/01-traceability-matrix`	RTM, audit report

Name	initialize-srs
Description	Set up IEEE Std 830-1998 and US ISO/IEC 25051 compliant project context files so downstream SRS skills can operate with stakeholder data, quality criteria, and definitions.

initialize-srs

SKILL.md

SDLC-Docs-Engine: Standards-Driven Documentation Across the Software Lifecycle

Active Projects

What's New in v3.6

What's New in v3.3

What's New in v3.2

What's New in v3.0

📚 Supported Documentation Types

Strategic & Vision Documents (Phase 01)

Requirements Engineering (Phase 02)

RE Fundamentals (NEW):

Waterfall Track:

Agile Track:

Design Documentation (Phase 03)

Testing Documentation (Phase 05)

Deployment & Operations (Phase 06)

Agile Artifacts (Phase 07)

End-User Documentation (Phase 08)

Governance & Compliance (Phase 09)

🛠 Supported Standards

🚀 Integration & Workflow

Starting a New Client Project

Installation

Quick Start

Step 1: Select Your Methodology

Step 2: Choose Your Documentation Path

Step 3: Execute Your Documentation Pipeline

🗂 Repository Structure

Pathing Model

📋 Documentation Pipelines

Waterfall SRS Pipeline (Phase 02)

Agile User Story Pipeline (Phase 02)

🤖 AI-Assisted Development Skills (New in v3.1)

Core AI Development Skills

1. ai-assisted-development - Multi-Agent Orchestration

2. ai-error-prevention - Trust But Verify Workflow

3. orchestration-best-practices - The 10 Commandments

4. ai-error-handling - 5-Layer Validation Stack

Reference Guides

prompting-patterns-reference.md

orchestration-patterns-reference.md

encoding-patterns-into-skills.md

How AI Skills Work Together

✅ Methodology Selection Guide

When to Use Waterfall SRS Pipeline

When to Use Agile User Story Pipeline

Hybrid Approach

🔁 Iterative Development & Re-running Phases

When Context Changes

Maintenance Mode

🧠 Design Philosophy

📖 Supporting Documentation

🎯 Example Workflows

Workflow 1: Waterfall Medical Device SRS

Workflow 2: Agile E-commerce Startup

Workflow 3: Hybrid SaaS Platform

🔧 Domain-Specific Skills

Architecture Skills

Database Skills

Security Skills

UI/UX Skills

Process Skills

Technology Skills

🚨 Critical Rules

Database Work (MANDATORY)

Documentation Standards (MANDATORY)

Security Baseline (MANDATORY for Web Apps)

📊 Verification & Validation (V&V)

IEEE 1012 Evaluation Framework

Audit Execution (Phase 09)

🔄 Migration from v2.x

Update Your Workflows

Backward Compatibility

📈 Roadmap

v3.6.0 (Current - 2026-04-13)

v3.5.0 (2026-03-08)

v3.4.0 (2026-03-07)

v3.3.0 (2026-03-01)

v3.2.0 (2026-02-28)