Ralph Specum Tasks

It doesn't write tasks itself. Instead, it coordinates by resolving which spec you're working on, loading requirements and design docs, then delegating the actual planning to a task-planner sub-agent. The handoff is careful: it counts tasks, updates state with phase markers and approval gates, writes progress notes, and stops to ask permission before moving to implementation unless you're in quick mode. You'd use this when you want structured, atomic tasks with exact file targets and verification commands based on your spec docs. The strict stop behavior keeps you in control of each phase transition, which matters when you're turning design into deliverables.