2 Commits

• fix(skills): move top-level origin frontmatter key under metadata

  The official Agent Skills spec (agentskills.io/specification) whitelists exactly
  6 top-level frontmatter keys (name/description/license/compatibility/metadata/
  allowed-tools). A top-level `origin` key fails the official validator
  (anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate).
  
  This moves `origin: X` -> `metadata.origin: X` across the canonical skills/
  tree, preserving each value verbatim. Frontmatter-only, minimal diff.
  
  - 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata)
  - origin values preserved verbatim (verified 251/251)
  - YAML validated on all changed files
  - scoped to canonical skills/ only (docs/<lang> translations + tool mirrors
    .cursor/.kiro/.agents left untouched; presumably regenerated from canonical)
  
  Addresses #2233

  BERORINPO · 2026-06-11 21:12:21 +09:00
  db7f2a6fd5
• feat: add orch-* orchestrator skill family (#2153)

  * feat: add orch-* orchestrator skill family
  
  Lightweight wrappers that orchestrate existing ECC agents through a gated Research -> Plan -> TDD -> Review -> Commit pipeline, right-sized per task.
  
  - orch-pipeline: shared engine (phases, size classifier, two gates, agent map)
  - orch-add-feature/change-feature/fix-defect/refine-code/build-mvp: thin wrappers delegating to the engine
  
  * chore: register orch-* family in catalog, command registry, and agent.yaml (post-rebase onto green main)
  
  ---------
  
  Co-authored-by: ECC Test <ecc@example.test>

  David W Miller · 2026-06-07 16:15:31 +08:00
  90dfd9505d