wp scaffold plugin writes the boilerplate you would have typed

Starting a plugin means a header comment, a directory layout, a text domain, a readme and — if you intend to test it — a PHPUnit configuration wired to WordPress’s own test library. That last part is an afternoon of reading, which is most of the reason so many plugins have no tests at all. wp scaffold writes all of it.

wp scaffold plugin catalogue-feeds --plugin_name="Catalogue Feeds" --activate

# the one that earns the command: phpunit.xml, a bootstrap, and the installer
wp scaffold plugin-tests catalogue-feeds

bash bin/install-wp-tests.sh wordpress_test root '' localhost latest
phpunit

# and the smaller ones, which are mostly about not mistyping the arguments
wp scaffold post-type datasheet --label="Datasheet" --textdomain=catalogue
wp scaffold taxonomy series --post_types=datasheet

install-wp-tests.sh is the piece worth the whole command: it downloads the core test library at the version you name, creates a throwaway database and writes the config the bootstrap expects, so phpunit runs against a real WordPress rather than against mocks of it. The scaffolds are generators and not a framework — they emit ordinary files that you then own, and running one again over a plugin you have edited overwrites your work file by file, so this is a starting point rather than something to re-run. The value in the smaller ones is consistency: passing --textdomain and a prefix once produces labels, capabilities and translation calls that all agree, which is precisely the tedium that gets skipped by hand on a site running twelve plugins.