Skill audit report

plan-readiness-review Audit report.

Adversarial senior/staff-engineer review of a PRD, plan, spec, RFC, design doc, or implementation plan to decide whether it is implementation-ready — detailed enough that a different senior engineer could build it without inventing requirements, architecture, schemas, API contracts, error handling, or acceptance criteria. Produces a requirement inventory with stable IDs, a per-requirement readiness verdict backed by document anchors, an unresolved-assumption register, and a counted READY / NOT READY decision. Use this whenever someone asks to review a plan, PRD, spec, RFC, design, or ticket before build; says "is this ready to implement", "is this spec complete", "review my plan", "poke holes in this", "will an engineer know what to build", "plan readiness", or "sign this off"; or hands over planning artefacts and asks whether work can start. Use it even when they only say "have a look at this spec". If working code already exists and the question is whether it ships, use production-re