blueprint-executelisted

Intelligent meta command that analyzes repository state and executes the appropriate blueprint action. ## When to Use This Skill | Use this skill when... | Use blueprint-status instead when... | |---|---| | You want auto-detection of init/upgrade/derive/generate/execute steps | You only want to view status without taking action | | You're resuming a project after pulling and want "what's next?" | You want a read-only report with `--report-only` | | You want one entry point that delegates to specific blueprint skills | Use blueprint-init instead when bootstrapping a brand-new project | | You say things like "run blueprint" without specifying a command | Use blueprint-upgrade instead when you know you need to migrate | **Concept**: Run this command anytime to automatically determine what should happen next in your blueprint workflow. Safe to run repeatedly - it's idempotent and will always figure out the right action. **Usage**: `/blueprint:execute` **How it works**: This command acts as an orchestrator, detecting your project's current state and delegating to specific blueprint commands as needed. It uses parallel agents for efficient context gathering. For detailed AskUserQuestion templates, examples, and common workflows, see [REFERENCE.md](REFERENCE.md). --- ## Phase 0: Parallel Context Gathering Launch these agents **simultaneously** to gather context: | Agent | Task | |-------|------| | **Git History Analysis** | Recent commits (last 20), branches, uncommitted c