Your entire software delivery lifecycle. AI-driven. IDE-native. Seven families built — from strategy through architecture to product development.
AIFLC is a brand of injectable workflow packages that guide AI coding agents through professional software delivery — from raw idea to governed code — with a human approval gate at every step.
Packages are organised into families. Each family is its own repository you can drop into your workspace. Your AI agent becomes a PMO advisor, an architect, a compliance engine. No SaaS. No vendor lock-in. Just markdown files that make your AI agent structured. Licensing is per family — the PDLC family is free under Apache 2.0; future families set their own terms.
This is the AIFLC umbrella repo — the front door to the brand. It carries the story and points you to each family. The packages themselves live in the family repositories linked below.
AI coding agents are powerful. But without lifecycle governance, they produce confident work that violates your team's own architecture. The problem isn't AI capability — it's AI direction.
AIFLC solves this: structured workflows that chain decisions forward so nothing is lost, re-asked, or silently ignored.
AIFLC is the umbrella. Each family is a self-contained product line — a chain of packages that cover one domain of delivery end to end. Pick the family that fits your work and clone its repo.
| Family | Repo | What It Covers | License | Status |
|---|---|---|---|---|
| PDLC — Product Development Life Cycle | mbmd/AIPDLC | Idea → initiation → architecture → UX → backlog → workspace → governance → test. 11 packages. | Apache 2.0 + Attribution | ✅ Live (beta) |
| SFLC — Strategy Formulation Life Cycle | coming | Enterprise strategy formulation: scan → diagnose → vision → choose → articulate. 5 packages. | Source-Available Commercial (DRAFT) | ✅ Built |
| SXLC — Strategy Execution Life Cycle | coming | Strategy execution: intake → OKRs → scorecard → initiative portfolio → review. 5 packages. | Source-Available Commercial (DRAFT) | ✅ Built |
| BALC — Business Architecture Life Cycle | coming | Business architecture: vision → capabilities → value streams → operating model → governance. 5 packages. | Source-Available Commercial (DRAFT) | ✅ Built |
| DALC — Data Architecture Life Cycle | coming | Data architecture: discovery → governance → modeling → pipelines → MDM → privacy → reference arch. 7 packages. | Source-Available Commercial (DRAFT) | ✅ Built |
| AALC — Application Architecture Life Cycle | coming | Application architecture: discovery → portfolio → integration → design → AI orchestration → governance. 6 packages. | Source-Available Commercial (DRAFT) | ✅ Built |
| TALC — Technology Architecture Life Cycle | coming | Technology architecture: discovery → cloud → resilience → security → platform/MLOps → FinOps → roadmap. 7 packages. | Source-Available Commercial (DRAFT) | ✅ Built |
| BPLC — Business Process Life Cycle | coming | BPM: discover → model → analyze → redesign → automate → monitor → govern. 7 packages. | TBD | 🔜 Planned |
| SMLC — Service Management Life Cycle | coming | Service management: design/transition → incident → problem → change → request → SLA → governance. 7 packages. | TBD | 🔜 Planned |
| ROLC — Reliability & Operations Life Cycle | coming | Reliability & ops: discovery → observability → SLOs → AIOps → resilience → capacity/FinOps → governance. 7 packages. | TBD | 🔜 Planned |
| VRIC — Value & Continual Improvement | coming | Value & improvement: discovery → experience → CSI → benefits → feedback routing. 5 packages. | TBD | 🔜 Planned |
Each family launches as its own
mbmd/AI{CODE}repository and sets its own license — check the family repo for terms. The PDLC family is free under Apache 2.0. Strategy and EA families carry a DRAFT Source-Available Commercial License (pending attorney review). Remaining families' licenses are TBD.
The PDLC family (mbmd/AIPDLC) chains eleven packages across a portfolio layer and a project layer:
- AI-ILC — evaluate raw ideas → approved brief
- AI-PILC — run project initiation → Project Initiation Package
- AI-PPM — govern a portfolio of projects
- AI-FLO — route handoffs between packages
- AI-ADLC — design architecture → Architecture Package
- AI-UXD — design the user experience → UX Design Package
- AI-POLC — own the product backlog → Product Backlog Package
- AI-DWG — generate a ready-to-code workspace
- AI-GCE — derive compliance governance from the architecture
- AI-TGE — derive test strategy and coverage from the workspace
- AI-DFE — data fabric engine: gather structured status from every package for dashboards and roll-ups
Each package's output is the next package's input. That's the chain. See the full chain diagram, package table, and install steps in the AIPDLC repo.
The PDLC chain produces the workspace that AI-DLC (awslabs/aidlc-workflows) consumes. We produce what it builds from.
AIFLC has grown from the shipping PDLC family into a full life cycle across five pillars — Strategy (decide), Enterprise Architecture (architect), Process (model), Product Development (build), and Downstream (run/operate). Seven families are now built (PDLC + Strategy + EA), covering 46 domain packages. The next families to build are the Process track (BPLC) and the Downstream track (SMLC · ROLC · VRIC). See the AIFLC Roadmap for the full landscape, how families chain, the release sequence, and what makes the AI-native approach different.
- Pick a family — start with AIPDLC.
- Clone the family repo into a temporary
.aiflc-src/folder (not your workspace root), run the family installer against your workspace, then delete.aiflc-src. The installer places packages under.aiflc/{family}/and writes all outputs to{family}-ws/— so your workspace root stays clean. - Activate in your AI-enabled IDE — tell your agent
Using AI-ADLC, design the architecture for this project. - Chain — feed each package's output into the next.
Full per-package instructions live in each family repo's README and INSTALL_GUIDE_*.md files.
| Traditional Tools | AI Rules/Skills | AIFLC | |
|---|---|---|---|
| Coverage | One phase | One phase | Full lifecycle (idea → code) |
| Decisions | Siloed per tool | Not tracked | Chained forward across phases |
| Governance | Manual / honor system | Static rules | Derived from architecture automatically |
| Where it runs | Separate SaaS app | In IDE | In IDE |
| Cost | $$$$/month | Varies | Free (PDLC) · per family |
| Lock-in | High (data in their cloud) | Low | Zero (your files, your repo) |
- 🔗 Chained lifecycle — output of one package = input to the next. Decisions flow forward.
- 👤 Human at every gate — AI structures, human decides. Never auto-progresses.
- 📁 File-based — everything is markdown. Version-controlled. Auditable. Portable.
- 🔌 IDE-native — runs inside your editor. No context switching.
- 📐 Methodology-backed — Industry-standard project-governance practice, C4, ADRs. Not made-up process.
- 🎚️ Progressive — start with one package, one tier. Scale when ready.
- 🏗️ Brownfield-aware — handles "something already exists" as a first-class mode.
- ⚡ Standalone + composable — each package works alone or as part of the chain.
AIFLC works with any AI IDE that supports steering/rules files:
| Platform | Status | Notes |
|---|---|---|
| Kiro | ✅ Full support | Reference implementation |
| Cursor | ✅ Works | Via .cursorrules or .cursor/rules/ |
| Claude Code | ✅ Works | Via CLAUDE.md |
| Amazon Q Developer | ✅ Works | Via workspace context |
| GitHub Copilot | Workspace-level instructions only | |
| Cline | ✅ Works | Via .clinerules |
| Windsurf | ✅ Works | Via .windsurfrules |
Each family repo ships platform-specific install guides.
Licensing is per family. Each family repository sets and declares its own license — there is no single license that covers the whole brand. Always check the family repo for its terms.
| Family | License |
|---|---|
| PDLC (AIPDLC) | Apache License 2.0 with Attribution Addendum |
| SFLC · SXLC · BALC · DALC · AALC · TALC | AIFLC Source-Available Commercial License (DRAFT) |
| Future families (BPLC, SMLC, ROLC, VRIC) | Set per family — see each repo (may differ) |
The PDLC family is Apache 2.0 with Attribution Addendum — the same base license as Kubernetes, Spark, and Android:
- ✅ Free — no cost, no tiers, no trial limits
- ✅ Commercial use — build and sell products on top of it
- ✅ Modify & fork — make it yours
- ✅ Redistribute — share it freely
⚠️ One condition — credit the original work in distributed products:
"Built on AIFLC by Mohammad Maheri — LinkedIn"
See the AIPDLC LICENSE for full terms.
This umbrella repo's own LICENSE covers only the landing-page content here — it does not license the families.
- 💬 Discussions — questions, ideas, show & tell
- 🐛 Found a bug in a package? Open an issue in that family's repo (e.g. AIPDLC issues)
- 🤝 Contributing — how to contribute (CLA required)
The PDLC family is free. Expert guidance is available for teams that want faster adoption:
| Service | What |
|---|---|
| Implementation advisory | Guided rollout tailored to your org |
| Training & workshops | Team enablement on AIFLC methodology |
| Consulting | Expert help on architecture, governance, initiation challenges |
| Certification (planned) | Official AIFLC practitioner credential |
Contact: Mohammad Maheri · mohammad.maheri.work@gmail.com
Add the badge to your README:
[](https://github.com/mbmd/AIFLC)Created by Mohammad Maheri — LinkedIn
Designed from real-world PMO, architecture, and delivery practice. Built using AI to build AI lifecycle tools.
Star this repo if AIFLC is useful. It helps others discover it. ⭐