ecc-recipes

原文涵盖的主题

• ECC Recipes
• When to Activate
• Do Not Use When
• Core Principle
• Live reads
• Family Classification (by prefix)
• How It Works
• Catalog mode (no description)

One entry point for "which group of ECC slash-commands runs my workflow, in what order, and when do I stop." Also browses every command-group recipe family. Fills the gap between two existing skills: ecc-guide — lists commands and where to read docs, but as a flat catalog. prompt-optimizer — matches a task to components, but outputs a single prompt, not a multi-command group with run-order and stop condition. This skill adds: family grouping + run-order + stop condition. "Which command group do I run for ?" "What's the command sequence to build an MVP / fix a defect / refactor?" "Show me all ECC command-group recipes" (catalog mode) "How many workflow pipelines does ECC have?" User invokes /ecc-recipes with or without a description. User wants the task done now — route to the actual command, don't describe it. User wants deep docs for ONE command — use ecc-guide. User wants a draft prompt rewritten — use prompt-optimizer. Answer from current files, not memory. The command set changes; never hardcode counts or member lists. Read the live commands/ directory each run, then classify into families. Resolve the commands directory (first that exists), then list names: Optionally read man

这里只展示节选，请以完整原文和当前要求为准。