Launching today
AIPDLC
Idea > Project > Portfolio > Product > UX > Architecture >..
8 followers
Idea > Project > Portfolio > Product > UX > Architecture >..
8 followers
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.
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.
the whole approach of dropping markdown files into your workspace and letting the agent pick it up is honestly pretty clever, feels way more natural than another config-heavy tool.