apex-large-project-deliverylisted
Install: claude install-skill zltstl888/apex-large-project-delivery
# APEX Large Project Delivery
Move a complex project toward its real acceptance outcome with the least process that safely controls it. The goal is not to produce more plans, cards, checks, or logs. The goal is to protect current truth, prevent rework, and reach a verifiable delivery state.
## Decide whether this skill should govern the task
Use the full workflow when the task has several dependent steps and one or more of these delivery risks:
- several components, systems, roles, or execution surfaces must move together under one shared acceptance or recovery boundary;
- current and legacy versions, data, routes, or artifacts can be confused;
- a human-approved artifact or working path must remain frozen;
- earlier fixes caused regressions, entity-specific patches, or repeated rework;
- UAT, migration, deployment, production, sending, or customer acceptance is in scope;
- a delivery deadline makes recovery and stop decisions important.
If the request is a simple answer, a one-step read-only check, or an ordinary low-risk change—even when it touches several predictable files—exit this workflow. Complete the task through the normal implementation loop with one nearest affected check and no project cards, new logs, broad audit, or extra ceremony.
## Choose the lightest safe delivery weight
Inherit any stronger risk profile defined by the user's project or global instructions. Never downgrade a production, regulated, customer-facing, destructive, permission-changing, or