sdlc-tier-selection

Guide for selecting the appropriate SDLC tier based on project complexity. Use when planning features, assessing scope, or starting new work.

⭐23stars🔀25forks📁View on GitHub🕐Updated Jan 8, 2026⬇️3downloads

When & Why to Use This Skill

The SDLC Tier Selection skill is a strategic framework designed to optimize software development workflows by accurately assessing project complexity. It categorizes development tasks into five distinct tiers—Micro, Small, Medium, Large, and Enterprise—ensuring that teams apply the appropriate level of documentation, architectural design, and quality gates. By standardizing the transition from requirements to deployment, this skill helps developers and project managers avoid over-engineering simple fixes while maintaining rigorous standards for complex system architectures.

Use Cases

  • Project Scoping & Planning: Automatically determine the appropriate SDLC tier when starting a new feature to set realistic human-hour estimates and resource requirements.
  • Documentation Governance: Identify exactly which design documents (e.g., use-cases, architecture, API, or database schemas) are mandatory based on the project's complexity tier to ensure compliance.
  • Workflow Standardization: Establish clear phase sequences for the development team, ranging from rapid 'Implementation-Testing' cycles for micro-tasks to comprehensive 'Discovery-Compliance-Deployment' flows for enterprise systems.
  • Repository Initialization: Analyze the current state of a codebase to decide whether to generate fresh design templates or update existing documentation before beginning development work.
namesdlc-tier-selection
descriptionGuide for selecting the appropriate SDLC tier based on project complexity. Use when planning features, assessing scope, or starting new work.

SDLC Tier Selection

Repository State (Check First)

State Action
Empty (no src/) Start fresh with full design templates
Has code + designs Update existing designs, maintain compatibility
Has code, no designs Analyze codebase, generate designs, then proceed

SDLC Tiers

⚠️ Time estimates are HUMAN hours for complexity assessment only. Never refuse scope based on time.

Tier Scope Design Docs Required
Micro Bug fixes (<1 day) use-cases.md (if needed)
Small Single feature (1-3 days) use-cases.md + architecture.md + api.md
Medium Multiple features (3-7 days) + database.md
Large Major changes (1-2 weeks) All 6 docs
Enterprise Full system (2+ weeks) All 6 docs

Phase Sequences

Micro: Requirements → Design Update (if needed) → Implementation → Testing

Small: Requirements → Design → Implementation → Testing → Deployment

Medium: Requirements → System Design → Documentation → Implementation → QA → Deployment

Large: Requirements → Architecture → Detailed Design → Documentation → Development → Testing → Quality Gates → Deployment

Enterprise: Discovery → System Architecture → Detailed Design → Compliance → Phased Development → Comprehensive Testing → Quality Gates → Infrastructure → Deployment → Post-Release

Design Documents (in .gaia/designs/)

  • use-cases.md - Use cases, user flows, API/UI journeys
  • architecture.md - System design and components
  • api.md - API endpoints and contracts
  • database.md - Schema and data models
  • security.md - Authentication and authorization
  • frontend.md - UI/UX patterns and components

After Selection

mcp__gaia__remember("sdlc", "type", "[micro/small/medium/large/enterprise]", "ProjectWide")
mcp__gaia__remember("sdlc", "phases", "[phase list]", "ProjectWide")