AI PDLC

The AI-native Product Development Lifecycle: a phase-gated development model where a governed AI agent works inside every stage of the standard discovery-to-release pipeline, grounded in a curated knowledge/context substrate and terminated by an explicit evaluation gate. The pattern generalizes what leading organizations converged on independently — this topic tracks the implementations, their disclosed mechanics, and the org consequences.

Summary

Three strata of evidence describe the same emerging playbook. Process disclosures (Freshworks: releases went from every 6 months to every 2 weeks after wrapping agent-parseable design systems, an internal knowledge platform called Prism, and a 12-phase Cursor harness /fw-innit around one governed agent per lifecycle phase). Org mandates (Shopify's April 2025 memo making reflexive AI usage a baseline expectation with prototype-before-headcount. Duolingo's AI-first contractor displacement — and its partial walk-back). Productized standards (GitHub Spec Kit's constitution → specify → clarify → plan → checklist → tasks → analyze → implement → converge chain, 1.0 since August 2026, and AWS Kiro's requirements/design/tasks specs in EARS notation, GA since November 2025). The invariants across all of them are the interesting part. The vendor names are instantiations.

Key Facts

Fact	Value
Category	Process pattern (not a product): phase-gated product lifecycle with an AI agent per phase
Flagship disclosure	Freshworks, narrated by then-CPO Srini Raghavan (CPO 2024-12-02 to 2026-07/08)
Reported outcome	Release cadence 6 months -> 2 weeks; 1 PM : 1 engineer (vendor-reported)
Open-source instance	GitHub Spec Kit — Latest Version 1.0.11 (2026-09-24), MIT, 40 named agent integrations
Commercial instance	AWS Kiro — GA 2025-11-17; Latest IDE Version 1.1 (2026-09-14); Free to $200/user/month
Requirements notation	EARS (WHEN <trigger> THE SYSTEM SHALL <response>)
Mandate instances	Shopify memo (2025-04-07), Duolingo "AI-first" memo (late April 2025) and walk-back (May 2025)
Evidence level	No independent benchmark; process claims are single-vendor narratives

Full fact sheets: Reference.

Architecture At A Glance

The shared shape: a context substrate feeds one governed agent per phase, and every run ends at a quality gate before release. The same roles appear under different names in each instance:

flowchart LR
    subgraph SUB["Context substrate"]
        direction TB
        PRISM["Freshworks Prism hubs"]
        CONST["Spec Kit constitution"]
        STEER["Kiro specs and hooks"]
    end
    subgraph PH["Phase agents"]
        direction TB
        REQ["Requirements + clarify"]
        PLN["Plan / design"]
        BLD["Tasks + implement"]
    end
    subgraph GATE["Quality gates"]
        direction TB
        CPO["CPO check (human)"]
        CHK["checklist / analyze / converge"]
        PBT["Kiro property-based tests"]
    end
    SUB --> PH
    REQ --> PLN --> BLD
    PH --> GATE
    GATE --> REL["2-week release train"]

Layer-by-layer detail: Explanation.

Implementation Landscape

Instance	Archetype	Disclosed Mechanism	Headline Signal	Depth
Freshworks	Full process disclosure	Data-first foundation + Prism (knowledge hub / context hub / AI builder artifacts) + /fw-innit 12-phase harness w/ evals + CPO-check gate [F]	Release cadence 6 months -> 2 weeks. Staffing 1 PM : 1 engineer (was 1 PM + 1 designer : 10-20 eng). CEO: "more than half of our code" AI-generated (May 2026)	Deepest public machinery narrative to date (2026)
GitHub Spec Kit	Open-source productization	specify CLI installs commands or skills into 40 named agents (+ generic). Artifact chain constitution -> spec -> plan -> tasks -> implement -> converge (+ clarify, checklist, analyze gates). Opt-in assess and bug processes	1.0.0 on 2026-08-21, now 1.0.11 (2026-09-24). MIT licensed	Fully public, reproducible
AWS Kiro	Commercial IDE + CLI productization	Spec-driven workflow: requirements.md (EARS notation) -> design.md -> tasks.md. Feature (requirements-first or design-first), bugfix and quick specs. Hooks, property-based tests since GA	EARS acceptance criteria (WHEN ... THE SYSTEM SHALL ...) make agent-consumed requirements testable. GA 2025-11-17, IDE 1.1 on 2026-09-14	Public docs, proprietary tool
Shopify	Org mandate (culture)	Lütke memo (2025-04-07): reflexive AI usage is baseline expectation. Teams must prototype with AI before requesting headcount. AI usage enters performance reviews	Signals top-down restructure of who does what, no PDLC machinery published	Memo + coverage only
Duolingo	Org mandate (cautionary)	von Ahn "AI-first" memo (late April 2025): gradually stop contractors for AI-handleable work. Hiring gated on automation-proofing. Preceded by a ~10% contractor cut in January 2024. 148 AI-assisted courses followed	Consumer backlash forced a partial walk-back ("I do not see AI as replacing what our employees do") — mandates without worker consent have a PR cost curve	Memo + aftermath

The Invariant Pattern

Across all five, regardless of stratum, the same roles recur (reference architecture):

1. A knowledge/context substrate before agents. Encoded design systems, written standards, single source-of-truth repos (Freshworks' explicit precondition). Spec Kit gets to the same place via project constitutions.
2. One governed agent per lifecycle phase, not one omniscient chatbot — Freshworks embeds them in each PDLC stage. Kiro materializes it as three named spec phases. Spec Kit now ships separate processes for idea assessment, feature delivery and bug fixing.
3. Interrogation before generation. Freshworks' demoed agent asked persona/drill-down/success-metrics questions before building. Spec Kit ships a dedicated /speckit.clarify recommended before planning.
4. An explicit quality/eval gate. Freshworks appends an evals phase plus a human "CPO check". Spec Kit provides /speckit.checklist (reviewer-owned "unit tests for your requirements"), /speckit.analyze (read-only cross-artifact consistency) and /speckit.converge (code vs artifacts, repeated until Converged). Kiro gates on reviewable requirement documents and, since GA, property-based tests derived from the spec.
5. Org-ratio consequences, eventually political. Whoever runs the whole assembly line owns the outcome: ratios compress (Freshworks 1 PM : 1 engineer), roles blur into "Product Builder", and the change arrives either as engineered transition (Freshworks) or as memo-driven mandate (Shopify/Duolingo) with very different reception.

Why The Strata Matter

Mandates tell you adoption pressure is real but publish no machinery. Process disclosures publish machinery but are unauditable single-vendor narratives. Productized standards are auditable but stack-agnostic — they prove the workflow shape transfers, not that any specific claim about outcomes does. Cross-referencing all three is how this vault prevents over-trust of any one.

Evaluation

• Why it matters: It replaces the ad-hoc "everyone gets a chatbot" model with process structure — phase-scoped authority, grounding requirements, and evaluation gates — which is the difference between AI-assisted vibes and an auditable delivery pipeline.
• When the pattern fits: Multi-team orgs with existing design systems/docs culture and usage data worth grounding against. Regulated contexts needing traceable requirement->test chains (EARS/SDD both target this).
• When it does not fit: Solo/greenfield work where ceremony outweighs risk. Orgs unwilling to maintain artifact libraries or accept reviewer-hours at higher cadence.

Pros	Cons
Requirements interrogation front-loads clarity (all instances converge here independently)	Machinery varies wildly between instances. Cross-company comparability today is poor
Eval/checklist gates make quality claims inspectable (checklist as testable prose)	Process disclosures rest on vendor narratives. Nobody published independent benchmarks yet
Ratio compression raises per-person leverage	Mandate-first rollouts carry real backlash risk (Duolingo walk-back)
Model-agnostic instances prevent single-vendor lock-in (Freshworks stance. Spec Kit supports 40 named agents)	Knowledge/artifact substrates rot silently and degrade every downstream phase

• Common Use Cases: Enterprise transformation programs comparing adoption routes (mandate vs process vs tooling). PM/engineering leadership designing AI-era team topology. Platform teams deciding whether to buy (Kiro), adopt (Spec Kit), or build (Prism-equivalent) their lifecycle substrate.
• Licensing & Commercial Use: Pattern itself unownable. Instantiations span full spectrum: Spec Kit MIT (free). Kiro proprietary, credit-based plans from Free (50 credits) to Power ($200/month, 10,000 credits) plus Enterprise (pricing). Prism not a product.
• Ecosystem & Connections: Agents (Cursor, Claude Code, Codex, Kiro), prototyping surfaces (Figma Make), grounding warehouses (Databricks in the Freshworks case), eval frameworks (promptfoo and peers).
• Status & Maturity: Active convergence period. Tooling reached "1.0" in 2026 (Spec Kit 1.0.0 on 2026-08-21, Kiro IDE 1.0 in August 2026) faster than any cross-org benchmarking. Freshworks' disclosing executive left (announced 2026-07-28; Ryan Manning took a merged CPTO role from 2026-08-10) — a live test of whether the process outlives its evangelist.
• Alternatives: Status quo SDLC w/ point AI tools (pre-PDLC baseline). Pure vibe-coding for throwaway scope. Heavyweight formal methods lineage (EARS itself predates this wave).
• Migration & Lock-in Risks: Lock-in migrated from tools to artifacts: whichever side owns your spec templates, checklists, and rules corpus owns your velocity. Keep corpora in plain markdown under version control.
• Community Health / Evidence Level: See the per-instance rows in the Implementation Landscape table. Treat single-source mechanical detail accordingly.

Topic Map

• Reference — reported outcomes, Freshworks timeline, Spec Kit and Kiro fact sheets (versions, commands, pricing), EARS patterns, mandates timeline
• Explanation — reference architecture, instance mapping table, spec-driven instantiation (Spec Kit chain, Kiro spec states), flagship Freshworks case study, threat model
• How-to Guides — replication playbook, Spec Kit adoption and upgrade recipes, writing EARS criteria, verification recipes, failure modes
• Ref: Srini Raghavan Product Builder Playbook — provenance intake of the flagship disclosure source URL

Related Topics

• LLM Wiki — sibling thesis: curated interlinked repo-knowledge beats ad-hoc retrieval as agent substrate (the personal-scale cousin of Prism-style knowledge hubs)
• Zero Data Retention — directly relevant to the egress surface created when lifecycle context flows to external model endpoints
• OpenClaw vs Hermes Agent vs Claude Code — the agent harnesses that Spec Kit-style processes run inside
• AI Platform Engineering — the platform layer (GPUs, model serving, MLOps) underneath internal agent tooling
• Tools Catalogue — entries for spec-kit, Cursor, Claude Code, Codex and other harnesses referenced across instances

Sources

Primary (flagship case study): - Freshworks CPO on the AI PDLC and Product Builder Role — Aakash Gupta newsletter - The Product Builder Playbook (Full Breakdown) — YouTube - Raghavan's shared deck (Google Slides)

Productized standards: - github/spec-kit — README & docs · Spec-driven methodology doc · CHANGELOG · SDD command reference · Supported integrations · Project history - Kiro Specs documentation (EARS-based requirements/design/tasks) · Introducing Kiro · Kiro GA announcement · Kiro IDE 1.1 changelog · Kiro pricing

Mandates: - CNBC — Shopify CEO: Prove AI cannot do jobs before asking for headcount (memo shared by Tobi Lütke, Apr 2025) - First Round Review — From Memo to Movement (Shopify) - The Verge — Duolingo AI-first: replacing contract workers with AI - Fortune — Duolingo CEO walks back AI-first comments

Verification anchors: - Freshworks Appoints Srinivasan Raghavan as CPO (Dec 2, 2024) - Freshworks Q1 2026 results (revenue baseline) · Q2 2026 results (guidance raised to $963.5M-$966.5M) - Freshworks appoints Ryan Manning as CPTO (2026-07-28 release) · Inc42 — Ryan Manning appointed CPTO, Raghavan exits - Benzinga — Freshworks cuts 11% of workforce, CEO says over half of code is AI-written (May 2026) - Bloomberg — Duolingo cuts 10% of contractors (2024-01-08)

Questions

Open

• Will mandate-style orgs (Shopify, Duolingo) eventually publish PDLC machinery, or do mandates stay substitution-talk while engineers quietly assemble Prism-equivalents themselves?
• Does Spec Kit's checklist-as-tests idea ("unit tests for English") converge with Freshworks' undisclosed evals suite, or do enterprise eval suites need warehouse-grounded assertions checklists cannot express?
• Which Grok models exactly powered the Freshworks demo, and does quality hold outside latency-sensitive interactive loops?
• Does the 1 PM : 1 engineer ratio survive Freshworks' own leadership transition to a merged CPTO role?
• Are there counter-examples — companies running agent-per-phase PDLC without ratio compression?
• Does Spec Kit's new assess process (go / needs-clarification / kill) get adopted as the open-source equivalent of the idea-brief phases, or do product teams keep that work outside the repo?
• Kiro's property-based tests check code against specs; does anything equivalent check requirements against usage data (the Bel-grounding step), or does that stay custom?

Answered

• Q: Is "AI PDLC" one company's branding? — No. The term circulates in practitioner ecosystems (and inside Freshworks' own disclosure), but the pattern recurs across independent instances with different vocabularies: spec-driven development (Spec Kit/Kiro), AI-first engineering mandates (Shopify/Duolingo), builder pipelines (Freshworks).
• Q: Did Srini Raghavan really leave Freshworks? — Yes. Freshworks announced on 2026-07-28 (about 20 months after his 2024-12-02 appointment) that he was leaving "to pursue an entrepreneurial venture", and that Ryan Manning would join on 2026-08-10 as Chief Product and Technology Officer (release).
• Q: Is Spec Kit still experimental? — It reached 1.0.0 on 2026-08-21 and ships patch releases every few days (1.0.11 on 2026-09-24). The maintainers describe 1.0 as marking a year of work, not a frozen interface (history).