execute

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.

- 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 - 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 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" Begin full workflow.

Pass the original input argument. - Task file created at ./apex/tasks/[ID].md - Frontmatter shows phase: research - `` section populated Store `identifier` for subsequent skill invocations. Stop and report: "Research phase failed. See task file for details." Pass the identifier from step 1. - Frontmatter shows phase: plan - `` section populated - 5 mandatory artifacts present Plan phase is interactive. If user input needed: 1. Present the question to user 2. Get response 3. Continue plan phase with response Stop and report: "Plan phase failed. Run `/apex:plan [identifier]` to retry." Pass the identifier. - Frontmatter shows phase: implement - `` section populated - All tests passing If tests failing after max retries: 1. Report current state 2. Ask user: "Implementation has issues. Continue to ship (will document issues) or stop here?" 3. If stop, leave task in implement phase for manual intervention Pass the identifier. - Frontmatter shows phase: complete, status: complete - `` section populated - Git commit created - Reflection recorded Stop and report: "Ship phase failed. Run `/apex:ship [identifier]` to retry."

If any phase fails: 1. Report which phase failed 2. Report current state of task file 3. Suggest manual intervention: "Run `/apex:[phase] [identifier]` to retry" 4. Do NOT continue to next phase If any phase needs user input: 1. Present the question 2. Wait for response 3. Continue that phase with response 4. Do NOT skip the interaction If context is getting large: 1. Warn user: "Context is large. Consider continuing in new session." 2. Report current phase and identifier 3. User can restart with individual skill from current phase - All 4 phases completed successfully - Task file shows phase: complete, status: complete - Git commit exists - Reflection recorded - Final report displayed to user