القائمة
Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers are live, broken, redundant, or missing before fixing anything.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
| name | automation-audit-ops |
| description | Evidence-first automation inventory and overlap audit workflow for ECC. Use when the user wants to know which jobs, hooks, connectors, MCP servers, or wrappers are live, broken, redundant, or missing before fixing anything. |
| origin | ECC |
Use this when the user asks what automations are live, which jobs are broken, where overlap exists, or what tooling and connectors are actually doing useful work right now.
This is an audit-first operator skill. The job is to produce an evidence-backed inventory and a keep / merge / cut / fix-next recommendation set before rewriting anything.
Pull these ECC-native skills into the workflow when relevant:
workspace-surface-audit for connector, MCP, hook, and app inventoryknowledge-ops when the audit needs to reconcile live repo truth with durable contextgithub-ops when the answer depends on CI, scheduled workflows, issues, or PR automationecc-tools-cost-audit when the real problem is webhook fanout, queued jobs, or billing burn in the sibling app reporesearch-ops when local inventory must be compared against current platform support or public docsverification-loop for proving post-fix state instead of relying on assumed recoveryRead the current live surface before theorizing:
Group them by surface:
For every surfaced automation, mark:
Then classify the problem type:
Back every important claim with a concrete source:
If the current state is ambiguous, say so directly instead of pretending the audit is complete.
For each overlapping or suspect surface, return one call:
The value is in collapsing noisy automation into one canonical ECC lane, not in preserving every historical path.
CURRENT SURFACE
- automation
- source
- live state
- proof
FINDINGS
- active breakage
- overlap
- stale status
- missing capability
RECOMMENDATION
- keep
- merge
- cut
- fix next
NEXT ECC MOVE
- exact skill / hook / workflow / app lane to strengthen