In addition to the maintenance plans listed above, you should also code a job that checks file sizes verses available disk space to make sure you aren't running out of hard drive. Your server will crash (or at least SQL Server will not start) if the entire hard drive gets filled out by data and log files.

Other thoughts are to run regular DBCC CheckDB commands, restore your backups on a Dev or sandbox server to ensure the backups are valid (this can be automated) and schedule file cleanup jobs to archive off old ftp or text files.

EDIT: But as Gail said, no maintenance plan takes the place of a Disaster Recovery plan. There is no guarantee that maintenance plans will not lose data.