Skip to main content

Task Breakdown: Collections

Feature ID: collections Status: Done (Retrospective) Last updated: 2026-05-01

Phase 1 — Service​

  • T1. Add Collection shape to taxonomy types in @ever-works/contracts.
  • T2. Extend WorkTaxonomyService with getCollections / createCollection / updateCollection / deleteCollection.
  • T3. Slug generation + duplicate-name guard.
  • T4. Delete cleanup: clear collection field on all referencing items.

Phase 2 — Pipeline integration​

  • T5. generate_collections toggle on Standard Pipeline plugin settings.
  • T6. Categorization step assigns collections when toggle is on.

Phase 3 — API​

  • T7. Controller endpoints in apps/api/src/works/.
  • T8. Include collections in the categories-tags list endpoint.
  • T9. e2e tests covering CRUD + delete cascade.

Phase 4 — Web​

  • T10. Items → Collections tab UI.
  • T11. Website-settings toggle for collections_enabled.

Phase 5 — Storage​

  • T12. Reader/writer for collections.yml in the data repo.
  • T13. Items YAML includes optional collection field.

Phase 6 — Docs​

  • T14. User-facing doc docs/features/collections.md.
  • T15. Cross-link from taxonomy-system.md.
  • T16. Retrospective spec/plan/tasks.

Definition of Done​

  • All tasks shipped, tests pass, docs present, constitution gates verified.