joda-money

40 files · 758 findings · analysed 11 days ago

Ask anything about this codebase

Every answer is grounded in the extracted findings and cites file and line.

e.g.

Agent views — choose your perspective

🏢 Management Executive summary — capabilities, risks, spec coverage Ready →

📋 Product Owner Feature inventory, spec alignment, behavioural gaps Ready →

⚙ Engineer Implementation detail, patterns, dependencies, gotchas →

🏗 Architect Coupling, patterns, Zones of Pain, refactoring priorities Ready →

🔒 Security Verified security findings — no false positives Ready →

🧪 Tester Untested behaviours, edge cases, test gap inventory Ready →

Documentation & tools

Component diagram and cross-module dependencies

Product overview

What this product does, in plain English — no code knowledge needed

File-by-file structural breakdown with dependencies

Spec vs Reality

What the spec promised vs what the code actually delivers — gaps, undocumented behaviors, and risk flags. Every finding grounded in file:line evidence.

Complete MkDocs documentation

Intent document

● Auto-detected — using the project README. Paste your PRD or spec to override.

Set spec document