I can agree with that, but that's why I want to move away from them. I feel like they are too restrictive. It's true that they are a great help to get things going quickly, but it just seems easier to just use jobs if you want finer control over what happens. In fact, I wouldn't be surprised if I eventually come to the conclusion that even jobs are too restrictive or troublesome, and I just start using pure T-SQL scripts in the future.

However, I did look for a solution to my problem, and it seems that I could just add a T-SQL statement task to run my powershell script that I added to the maintenance plan job. I would just need to invoke the script with the xp_cmdshell stored procedure.