Drop markdown files into your IDE workspace and your AI coding agent gains structured expertise — it knows what to ask, what to produce, and when to hand off to the next stage. No plugins. No APIs. No vendor lock-in. Just professional process knowledge, packaged so an AI assistant can execute it with human oversight at every gate.
No reviews yetBe the first to leave a review for AIPDLC
Maker
📌
**The problem it solves:**
AI coding agents are powerful but directionless. They write code fast but skip architecture, ignore governance, produce no test strategy, and deliver nothing a team can actually ship with confidence.
AIPDLC gives them structure — the same stage-gate discipline a senior engineering org would follow, delivered as injectable files.
**How it works:**
11 packages chain across two layers:
- **Portfolio Layer** — AI-ILC (idea evaluation) → AI-PILC (project initiation) → AI-PPM (portfolio governance)
- **Project Layer** — AI-POLC (product ownership) → AI-UXD (UX design) → AI-ADLC (architecture) → AI-DWG (workspace generation) → build
- **Continuous** — AI-GCE (compliance) + AI-TGE (test accountability) run alongside
Each package makes the agent adopt a professional role (PMO advisor, CTO, DevOps engineer, QA lead) and produce real deliverables with approval gates at every stage.
**Key facts:**
- Works with Cursor, Claude Code, Kiro, Amazon Q, Cline, GitHub Copilot
- Each package works standalone OR chained
- Human-in-the-loop — you approve every gate
- Apache 2.0 licensed, free to use
- Install in 60 seconds
**One-command install:**
```
npx skills add mbmd/AIPDLC
Report
Drop markdown files into the workspace and the agent picks up structured expertise. Nice approach, no vendor lock-in is a big plus. One thing that would make this more useful for my team: a small CLI or watcher that validates the markdown structure against a schema before the agent ingests it, so we catch missing gates or broken handoffs at commit time instead of mid-run.
Report
Would love to see a built-in diff view that shows which parts of the markdown process docs the agent actually consulted during a session, so I can audit what shaped its decisions. Right now I have to guess why it asked certain clarifying questions or produced specific artifacts, and that opacity makes the human oversight loop feel less tight than it should.
Report
One thing that would really help me adopt this is a starter library of templated PDLCs for common workflows like bug triage, API design reviews, or onboarding new repo contributors. Right now figuring out the right structure and gate definitions for each team seems like a lot of upfront work, and a few battle tested templates would lower the barrier to trying it out on a real project.
Drop markdown files into the workspace and the agent picks up structured expertise. Nice approach, no vendor lock-in is a big plus. One thing that would make this more useful for my team: a small CLI or watcher that validates the markdown structure against a schema before the agent ingests it, so we catch missing gates or broken handoffs at commit time instead of mid-run.
Would love to see a built-in diff view that shows which parts of the markdown process docs the agent actually consulted during a session, so I can audit what shaped its decisions. Right now I have to guess why it asked certain clarifying questions or produced specific artifacts, and that opacity makes the human oversight loop feel less tight than it should.
One thing that would really help me adopt this is a starter library of templated PDLCs for common workflows like bug triage, API design reviews, or onboarding new repo contributors. Right now figuring out the right structure and gate definitions for each team seems like a lot of upfront work, and a few battle tested templates would lower the barrier to trying it out on a real project.