sdlc-lang-swift

Table of Contents

• AI-First SDLC Practices
  • Prerequisites
  • Setup
    • Plugin Install (Recommended)
    • SDLC Method Selection
    • Available Plugins
    • Available Skills
    • Agent-Based Setup (Pre-release / Development)
    • Script-Based Setup (Legacy)
  • How It Works
    • Rules
    • Validation
    • Agents
  • Documentation
    • Agent Development
  • Integration Testing
  • Known Limitations
  • Zero Technical Debt Policy
  • Development
    • Using the Framework (Your Project)
    • Developing the Framework (This Repo)
    • Current Version: 1.8.0
  • Contributing
  • License

AI-First SDLC Practices

A framework for integrating AI agents as primary developers while maintaining quality and process compliance. Ships 56 specialist agents across 12 plugins covering AI/ML, full-stack, cloud, security, project management, documentation, and containerised delegation. Automates the specify-architect-implement-review workflow with skills that enforce zero technical debt from day one.

Prerequisites

• Claude Code CLI (the host application for all plugins)
• Python 3.10+ (validation tools and scripts)
• Git
• Optional: GitHub CLI (gh) for PR-related features
• Optional: Docker (for sdlc-workflows containerised delegation)

Setup

Plugin Install (Recommended)

Install the plugin family from the Claude Code marketplace. This is the standard approach for using the framework in your projects.

Step 1: Add the marketplace and install the core plugin

/plugin marketplace add SteveGJones/ai-first-sdlc-practices
/plugin install sdlc-core@ai-first-sdlc

Step 2: Configure your team

/sdlc-core:setup-team

This presents project types (Full-stack, AI/ML, Cloud, API, Security, Custom) and installs the matching team plugins. For example, a full-stack web app installs:

Plugin	Description
sdlc-core	Rules, validators, enforcement, workflows (always installed)
sdlc-team-common	Solution architect, research agent, performance engineer, database architect
sdlc-team-fullstack	Web full-stack — frontend, backend, API, data, DevOps, UX, integration architects
sdlc-team-mobile + sdlc-team-ios / sdlc-team-android	Mobile — shared base (architecture, interaction UX) + platform design (Apple HIG / Material Design 3)

Step 3: Start working

/sdlc-core:new-feature 1 my-feature "Description of the feature"

SDLC Method Selection

The framework supports four SDLC delivery structures. The setup-team skill asks which one applies to your project; you can also pick later via /sdlc-core:commission. Most projects pick single-team (the default).

Method	When to use	Team size	What you install
Single-team (default)	Organic delivery, no formal phase gates. Most projects pick this.	3–10	sdlc-core + team plugins (no extra bundle)
Solo	Fast-iteration, lightweight constitution overlay.	1–2	sdlc-core + team plugins; commission with --option solo
Programme (Method 1)	Multi-team programme work with formal phase gates (requirements → design → test → code) and mandatory cross-phase review.	11–50 across 2–5 teams	sdlc-programme bundle + commission
Assured (Method 2)	Regulated industries (DO-178C, IEC 62304, ISO 26262, FDA 21 CFR Part 820). Bidirectional traceability, positional namespace IDs, DDD decomposition, typed evidence statuses, standard-specific exports.	Any	sdlc-assured bundle (v0.2.0 audit-ready at the tooling layer) + commission

Decision tree, comparison table, trade-offs, and migration notes: see docs/METHODS-GUIDE.md.

Available Plugins