I wouldn't, they can start by writing requirements and a design first, then break it up into manageable components. Or just refuse to review and let the author

I wouldn't, they can start by writing requirements and a design first, then break it up into manageable components. Or just refuse to review and let the author take full responsibility in running and maintaining the thing, if that's possible. A PR is asking someone else to share responsibility in the thing.