This sounds like something that should be handled by the deployers and the services they install. I.e. the #1 work is encapsulated in one or more services and the deployer attaches a listener to that service's ServiceController. When all services are started, a second set of services that handles #2 is started.
It's possible to register a deployment with the server without starting it. But that's not what you are looking for; all that does is make the deployment content known to server and get it copied into the deployment repository; "starting" it means actually deploying it. You're looking for more of a 2 step deployment notion.