Skip to content

chore: Restructure specs to proper OpenSpec format#49

Open
rubenvdlinde wants to merge 1 commit intodevelopmentfrom
chore/restructure-specs-to-changes
Open

chore: Restructure specs to proper OpenSpec format#49
rubenvdlinde wants to merge 1 commit intodevelopmentfrom
chore/restructure-specs-to-changes

Conversation

@rubenvdlinde
Copy link
Contributor

Summary

  • Add status: reviewed frontmatter to 13 specs that were missing it
  • All 20 specs document implemented functionality — no specs moved to changes/
  • Specs cover: admin-settings, component-tokens, css-architecture, custom-css-overrides, docs-content, extended-token-sets, hide-slogan, menu-labels, nextcloud-variable-mapping, nl-design, prometheus-metrics, theming-sync, theming-sync-dialog, token-editor-ui, token-import-export, token-set-apply-dialog, token-set-dropdown, token-sets, token-sync-workflow, vng-token-set

Test plan

  • Verify all specs have status: reviewed or status: enriched frontmatter
  • Verify no content was lost

All 20 nldesign specs document implemented functionality. Add missing
status: reviewed frontmatter to 13 specs that were missing it. No
specs needed to move to changes/ — all features are implemented.
Base automatically changed from feature/enrich-openspec-specs to development March 23, 2026 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant