execute

<skill name="apex:execute" phase="orchestrator">

<overview>
Meta-skill that chains all 4 APEX phases in sequence:

1. `/apex:research` - Intelligence gathering
2. `/apex:plan` - Architecture design
3. `/apex:implement` - Build and validate
4. `/apex:ship` - Review and reflect

Use this for single-session task completion. For multi-session work, invoke individual skills.
</overview>

<when-to-use>
- Small to medium tasks that fit in one session
- When you don't need to pause between phases
- When you want full workflow without manual skill invocation
</when-to-use>

<when-not-to-use>
- Large complex tasks that need human review between phases
- When you want to pause after research to think
- When context overflow is likely
- When you want to run phases in separate sessions
</when-not-to-use>

<initial-response>
<if-no-arguments>
I'll run the full APEX workflow. Please provide:
- Task description (e.g., "implement dark mode toggle")
- Ticket ID (e.g., "APE-59")
- Path to task file

Example: `/apex:execute "add user authentication"`
</if-no-arguments>
<if-arguments>Begin full workflow.</if-arguments>
</initial-response>

<workflow>

<step id="1" title="Research phase">
<invoke skill="apex:research">
Pass the original input argument.
</invoke>

<verify>
- Task file created at ./.apex/tasks/[ID].md
- Frontmatter shows phase: research
- `<research>` section populated
</verify>

<extract>
Store `identifier` for subsequent skill invocations.
</extract>

<on-failure>
Stop and report: "Research phase failed. See task file for details."
</on-failure>
</step>

<step id="2" title="Plan phase">
<invoke skill="apex:plan">
Pass the identifier from step 1.
</invoke>

<verify>
- Frontmatter shows phase: plan
- `<plan>` section populated
- 5 mandatory artifacts present
</verify>

<on-needs-input>
Plan phase is interactive. If user input needed:
1. Present the question to user
2. Get response
3. Continue plan phase with response
</on-needs-input>

<on-failure>
Stop and report: "Plan