feat(openspec): add spec artifact to my-workflow schema

Introduce the `spec` artifact to the workflow pipeline, positioned between delta and proposal phases. The spec combines interface boundaries, test contract, and TDD tasks into a single executable XML document.

Changes:
- Updated workflow description to reflect new phase: delta → spec | proposal
- Added spec artifact definition with template and construction rules
- Created specification.md template with XML structure for boundaries, test contract, and tasks
- Added evidence-linking rules for spec artifacts in openspec/config.yaml

The spec artifact bridges analysis (delta) and implementation (tasks) by defining interface contracts and test expectations in structured XML format.

Author: WesleyMFrederick

openspec/config.yaml

@@ -43,6 +43,10 @@ context: |
   - Action-based file organization: files named by transformation verb
 
 rules:
+  spec:
+    - "Trace claims to evidence: key assertions (context, decisions, risk mitigations) should include inline markdown links to their source in dependency artifacts or prior documents. A reader should be able to click any major claim and land on the evidence."
+    - "Always link to a specific header or block anchor, not bare files. jact extracts content at anchors for context — a bare file link does not guarantee extraction. Use #Header%20Name (raw with %20 for spaces, NOT #header-name kebab-case) or #^block-anchor for Obsidian block references."
+    - "Link naturally in prose, not as footnotes. The link text IS the claim: '[shallow page copies](../evidence.md#Root%20Cause)' not 'shallow page copies [1]'."
   proposal:
 
     - "Trace claims to evidence: key assertions (context, decisions, risk mitigations) should include inline markdown links to their source in dependency artifacts or prior documents. A reader should be able to click any major claim and land on the evidence."

openspec/schemas/my-workflow/schema.yaml

@@ -1,6 +1,6 @@
 name: my-workflow
 version: 2
-description: OpenSpec workflow - whiteboard → baseline → ideal → delta → proposal → specs → design → tasks
+description: OpenSpec workflow - whiteboard → baseline → ideal → delta → spec | proposal → specs → design → tasks
 artifacts:
   - id: whiteboard
     generates: whiteboard.md
@@ -225,6 +225,56 @@ artifacts:
       - baseline
       - ideal
 
+  - id: spec
+    generates: spec.md
+    description: Structured XML specification with interface boundaries, test contract, and TDD tasks
+    template: specification.md
+    instruction: >
+      Create a structured XML specification that combines interface boundaries,
+      test contract, and TDD tasks into a single executable document.
+
+
+      Before writing, read these context files from the change directory:
+
+      - delta.md (required — defines scope via ADD/CHANGE rows)
+
+      - baseline.md (required — current system traces and measurements)
+
+      - ideal.md (required — target system state)
+
+
+      Reference the spec glossary at design-docs/workflows/spec-glossary.md
+      for vocabulary and element definitions.
+
+
+      Construction rules:
+
+      1. Map each ADD/CHANGE row in delta → one <boundary> in
+      <interface_boundaries>. Each boundary defines: name, inputs, outputs,
+      constraints, and location in the codebase.
+
+      2. Derive <test_contract> assertions from boundaries. Each boundary
+      should have at least one positive assertion. Add negative assertions
+      for guard conditions (empty input, unchanged state, error paths).
+
+      3. Scale tasks to delta scope:
+         - Single-file change (patch): 1 dev task + 1 review task
+         - Multi-file change (feature): N dev tasks + N review tasks
+         - Each dev task follows TDD phases: RED → GREEN → COMMIT
+         - Review tasks have checklist + verdict (APPROVED | FIX_REQUIRED)
+
+      4. The <artifacts> section lists the primary target file(s) and links
+      back to context files (baseline, ideal, delta).
+
+      5. The <success_criteria> section defines pass/fail conditions derived
+      from the test contract assertions and reviewer verdict.
+
+
+      Output format: Markdown file containing a single XML code block with
+      root element <specification>. Follow the template structure exactly.
+    requires:
+      - delta
+
   - id: proposal
     generates: proposal.md
     description: Initial proposal document outlining the change

openspec/schemas/my-workflow/templates/specification.md

@@ -0,0 +1,40 @@
+```xml
+<specification>
+  <name>{{change-name}}</name>
+  <overview>...</overview>
+  <artifacts>
+    <target>...</target>
+    <context>
+      <file role="baseline_trace">../baseline.md</file>
+      <file role="ideal_trace">../ideal.md</file>
+      <file role="delta">../delta.md</file>
+    </context>
+  </artifacts>
+  <interface_boundaries>
+    <boundary id="B1" type="" location="">
+      <name/> <in/> <out/> <constraints/>
+    </boundary>
+  </interface_boundaries>
+  <test_contract>
+    <fixtures>...</fixtures>
+    <assertions>...</assertions>
+    <negative_assertions>...</negative_assertions>
+  </test_contract>
+  <!-- Scale tasks to match scope:
+       Patch: 1 dev task + 1 review task
+       Feature: N dev tasks + N review tasks -->
+  <task id="1" name="" agent="dev_agent">
+    <step number="1" phase="RED">...</step>
+    <step number="2" phase="GREEN">...</step>
+    <step number="3" phase="COMMIT">...</step>
+  </task>
+  <task id="2" name="" agent="reviewer" blocked_by="1">
+    <checklist>...</checklist>
+    <verdict>APPROVED | FIX_REQUIRED</verdict>
+  </task>
+  <success_criteria>
+    <pass>...</pass>
+    <fail>...</fail>
+  </success_criteria>
+</specification>
+```