ProjectLens
ProjectLens looks at a project from above: whether the goal is clear, the architecture fits, dependencies make sense, document truth conflicts, and what humans and AI should do next with less waste.
How it relates to the guide
The guide argues that ordinary people and small teams need technical exits. ProjectLens applies that at the project-governance layer: help founders, developers, and AI see the real project state before stale plans and polished suggestions pull them off course.
Why build it
AI is good at writing code and docs, but it can also make projects heavier. ProjectLens audits goals, architecture, dependencies, validation, and document boundaries from above so the owner can decide what to keep, fix, or leave untouched.
What makes it strong
It is not a PR review bot or an automatic refactoring tool. It produces owner briefs, audit briefs, and evidence logs so advice, evidence, cost, risk, and the option to do nothing are visible together.
What comes next
The current step is turning the method and first real audits into a public-safe version. GitHub should become public after local paths and history are cleaned; publishing an npm package should wait until there is a stable CLI or installable surface.