sdlc-practices

Advises on SDLC model selection, testing strategy, CI/CD pipelines, and engineering team practices.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill sdlc-practices-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sdlc-practices
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/engineering-process/skills/sdlc-practices
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill sdlc-practices-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to choose the right software delivery model, testing strategy, and CI/CD practices amid conflicting advice and hype. This Skill provides an evidence-grounded reference covering the full software development lifecycle so decisions are based on research (DORA, METR, SmartBear studies) rather than opinion. ## Core Features & Use Cases - SDLC Model Selection: Compare Waterfall, V-Model, Spiral, RUP, Scrum, Kanban, and hybrid approaches using the Cynefin framework matched to requirements volatility and regulatory constraints. - Testing & Quality Strategy: Apply the testing pyramid, trophy, and honeycomb models with concrete tooling guidance (Playwright, TestContainers, Pact, k6, mutation testing) and empirical code review limits (under 400 LOC, 60-90 minutes). - CI/CD, DevSecOps & AI-Era Practices: Implement trunk-based development, DORA metrics, SLSA/Sigstore supply-chain security, and evidence-based AI-assisted development guardrails. - Use Case: A tech lead designing a delivery pipeline for a regulated product can get guidance on V-Model applicability, SBOM requirements under EO 14028, contract testing with Pact, and DORA metric targets in one place. ## Quick Start Ask the assistant to recommend an SDLC model and testing strategy for your project context, such as a microservices platform with a compliance requirement.

Frequently Asked Questions about sdlc-practices

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Waterfall, Agile, and hybrid SDLC models?

Use the Cynefin framework: stable, known requirements suit plan-driven approaches like Waterfall or V-Model, while emergent requirements suit Agile methods like Scrum or Kanban. The 2026 enterprise norm is hybrid, wrapping phase-gate governance around Agile execution.

What is the best branching strategy for continuous delivery?

Trunk-based development is the DORA-supported default: integrate to trunk at least daily, keep three or fewer active branches, and use feature flags to decouple deploy from release. GitFlow suits versioned software like mobile or embedded releases.

Playwright vs Cypress: which E2E testing framework should I use?

Playwright overtook Cypress as the default in mid-2024 with native cross-browser support, parallelism, and trace viewing. Cypress retains superior in-browser debugging for JavaScript-centric single-page application teams.

Does AI-assisted coding actually improve developer productivity?

Evidence is mixed: a METR randomized trial found experienced developers were 19% slower on familiar codebases, while DORA 2025 shows positive throughput correlation but persistent instability. Gate AI-generated code through the same SAST and testing pipeline as human code.

What are the current DORA metrics for measuring delivery performance?

The five metrics are deployment frequency, lead time for changes, change failure rate, failed deployment recovery time, and rework rate added in 2024. The 2025 report replaced performance tiers with seven team archetypes.

When should I not use trunk-based development?

Trunk-based development fits most software, but versioned products with multiple supported releases, such as mobile apps, embedded systems, or on-premise software, often need GitFlow release branches for specific version cycles.