Manage the defer/restore state of ECC skills to reduce init token consumption.
Instructions
Run the script at this skill's directory: ecc-skill-defer/ecc-skill-defer.sh (relative to the skills repo root), or the installed copy at ~/.claude/scripts/ecc-skill-defer.sh.
Available commands
| Command | Description |
|---|---|
status |
Show active/deferred counts |
list |
Show all skills with their status |
apply |
Defer skills listed in config (use after ECC update) |
restore <name> |
Activate a single deferred skill |
restore --all |
Restore all deferred skills |
apply --reason "<text>" |
Defer with explicit reason logged to DEFER_LOG.md |
Default behavior
If no argument is provided by the user, run status then list.
Config
The defer list is at ecc-skill-defer.conf (same directory as the script). To add/remove skills from the defer list, edit this file then run apply.
After restoring a skill
Tell the user: "Skill restored. It will be available in the next session (or after context reload)."
Notes
- Defer reason tracking:
apply --reasonwill record the defer reason inDEFER_LOG.md(append-only), with the format<date> | <skill> | <reason>。listThe command can optionally display the most recent defer reason. - Portfolio health check: After a defer/restore operation, it is recommended to run
/skill-healthto check whether the current skill portfolio has redundancy or gaps.
Core skill protection (HITL Guard)
Before executing apply , you must first scan the list of skills about to be deferred (ecc-skill-defer.conf):
If the list contains design or assist, use AskUserQuestion to force confirmation (this is Hard Stop, and must not be skipped):
The list about to be deferred contains a core planning skill:
- [list detected core skills]
design / assist are core planning skills; after deferring them, industry/academic reference capability and ECC resource allocation quality will be lost.
- Confirm defer — I understand the impact and still want to continue
- Cancel — keep these skills and do not execute apply
Only continue executing apply after the user explicitly selects "Confirm defer".
apply operation verification (basis: DAMA-DMBOK Completeness — manifest vs. actual)
Execute apply After that, you must re-verify the status via list :
-
Before executing apply, record the list of skills expected to be deferred (manifest)
-
After apply completes, run
listto obtain the current status -
Verify item by item against the manifest (basis: OpenAI Developer Community consensus — Checklist-driven):
Skill Expected status Actual status Result foo deferred deferred PASS bar deferred active FAIL -
If there is any FAIL → output a warning and prompt manual checking of
ecc-skill-defer.confand the script execution result -
All PASS → output the current list of available skills to ensure the user understands the existing resources
restore operation verification (basis: DAMA-DMBOK Completeness)
Execute restore <name> or restore --all After:
- Execute
listto verify that the target skill status isactive - Output the verification result:
[PASS] <skill> 已恢復為 activeor[FAIL] <skill> 狀態仍為 deferred - Inform the user: "Skill restored. It will be available in the next session (or after context reload).」