Auto Trigger

This is pure infrastructure. It's a configuration layer that lets skills automatically chain together based on hooks like after_complete, on_error, or before_start. You define triggers in YAML front matter, set modes like auto, ask_first, or background, and skills fire each other off when conditions are met. The vision is clear: PRD planner finishes, kicks off self-improving-agent in the background, which triggers create-pr with a confirmation prompt, which logs to session-logger. In practice, you're architecting workflow choreography instead of hardcoding sequences. The risk is obvious though. Get your conditions wrong and you'll either spam the user with confirmations or create circular dependencies that never terminate.