There is an alternative approach that I have used in just such a situation that I think is worth considering.

You can place all your POD in a single file for documentation/admin and then have a script that creates the individual PODs for each script either as .POD or rewriting the original file.

This is a bit of a kludge and only really works with small groups of closely related files where updating one will directly impact another (ie if A requires B then B doc may say required by A). It is also nice for due diligence when you can extract an overview that maps to the spec and show how it maps all the way down to the code level.

You can also use this approach when starting a project if you have a clear functional/technical specification to auto create documented stubs for your packages or scripts.

Hope this is not too confused
UnderMine