feat: add standard openspec skills and workflow

[switzerb]

Closes PATH-1583

Why this change?

We are going to be moving more towards spec-driven development as a part of our AI goals. In order to support that, we want to initialize the skills and workflow in the standard-toolkit repo as a first step.

To get more information about openspec: https://openspec.dev/ – and more docs that are actually quite a bit more useful than the website: https://github.com/Fission-AI/OpenSpec/tree/main/docs

To get a better idea about the kinds of workflows we are looking at supporting: https://docs.accelint.dev/doc/spec-driven-development-high-level-overview-KOD4BAmF6O this is an overview of spec driven development here and this is the work-in-progress on backporting things: https://docs.accelint.dev/doc/backport-handoff-process-XScj7iNUHd

Note that at the moment, these are all still a bit in progress, so no immediate changes are being made to the way we work and the expectations around how we code. In the next few weeks there will be some "spec science" to develop guidelines around how we want to use this tool.

An experiment already in progress:

• Using openspec to initialize a new package

If you are inspired to experiment on your own, go for it, but expect there to be churn and some pushback as we are feeling our way through this.

Note that I am including all the potential options here with the "expanded workflow" https://github.com/Fission-AI/OpenSpec/?tab=readme-ov-file#quick-start. There doesn't seem to be any downside to having more features available?

✅ Pull Request Checklist

• Included link to corresponding GitHub Issue.
• The commit message follows conventional commit extended guidelines.
• Added/updated unit tests and storybook for this change (for bug fixes / features).
• Added/updated visual regression tests for this change (for bug fixes / features).
• Added/updated documentation (for bug fixes / features)
• Filled out test instructions.
• Added changeset (for bug fixes / features).

📝 Test Instructions

No testing required -- this is all internal tooling and should have no effect on behavior.

❓ Does this PR introduce a breaking change?

• Yes
• No

🤖 AI Usage

• Added corresponding label (ai / human) to PR:

If ai was used, select all that apply:

• Ideation / brainstorming
• Documentation
• Testing
• Implementation

💬 Other information

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
design-toolkit	Ready	Preview, Comment	Mar 16, 2026 2:49pm
map-toolkit	Ready	Preview, Comment	Mar 16, 2026 2:49pm

[github-actions]

📊 Coverage Reports

Coverage Changes by Package

Click to expand 29 package details

apps/next (No diff)

packages/bus (No diff)

packages/constants (No diff)

packages/converters (No diff)

packages/core (No diff)

packages/dataset (No diff)

packages/design-foundation (No diff)

packages/design-toolkit (No diff)

packages/formatters (No diff)

packages/geo (No diff)

packages/hotkey-manager (No diff)

packages/icons (No diff)

packages/logger (No diff)

packages/map-toolkit (No diff)

packages/math (No diff)

packages/ntds (No diff)

packages/postcss-tailwind-css-modules (No diff)

packages/predicates (No diff)

packages/temporal (No diff)

packages/web-worker (No diff)

packages/websocket (No diff)

tooling/biome-config (No diff)

tooling/constellation-tracker (No diff)

tooling/eslint-config (No diff)

tooling/prettier-config (No diff)

tooling/smeegl (No diff)

tooling/turbo-filter (No diff)

tooling/typescript-config (No diff)

tooling/vitest-config (No diff)

_{Coverage data collected from all packages in the monorepo.}

[ArrayKnight]

Did you really use AI to install these? I strongly suspect you just ran the install script which doesn't involve AI

[switzerb]

Did you really use AI to install these? I strong suspect you just ran the install script which doesn't involve AI

fair point.