Is there any specific reason(s) to not have support for test specs (e.g., unit, functional, perf)?

[artemoks]

I think it would be nice to have test spec artifacts as first class citizens too with cross-check validations against requirements/scenarios. Or, the idea is to have test specs under a separate capability and/or change?

[artemoks]

Test spec/plan artifact can added/enforced by modifying schema.yaml. For example,

1. Update "description:"

description: Default OpenSpec workflow - proposal → specs → design → test plan → tasks

2. Add test-plan artifact

- id: test-plan
    generates: test-plan.md
    description: Verification strategy, coverage matrix, and concrete test inventory
    template: test-plan.md
    instruction: |
      Create the test plan that explains HOW the specified behavior will be verified.
      ...
    requires:
      - specs
      - design

3. Update "- id: tasks"

  requires:
      - specs
      - design
      - test-plan

4. Update "apply:"

apply:
  requires: [test-plan, tasks]
  tracks: tasks.md

[guru1306]

I would also need something similar to this. Once the feature gets implemented using openspec, how do we implement the end to end automation using the openspec?

[laurentftech]

Completely agree. I have in my AGENTS.md a rule to force the creation of a traceability matrix between each requirement and the tests to demonstrate the full coverage. I consider that the job is not to be considered done if there's no full coverage. I have seen several times during final validation that the requirements were not actually covered. A good safety net.