openspec-artifact-links

ARCHIVED

`/openspec-propose a way to make sure that when I call my openspec flow, regardless of schema, it always shows me a link to the artifacts produced so I can open them easily`

STAGES

  1. proposal05-19
  2. requirements05-19
  3. design05-19predates the Figma as-is + proposed pair
  4. tasks05-19
  5. build—
  6. archived—

CAPABILITY

  • openspec-workflow-artifact-links5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ✓1.1After `/opsx:propose` writes an artifact, I can click a link in the agent reply to open that file immediately (e.g. `proposal.md` on the first propose turn).not stated
  • ✓1.2After `/opsx:apply`, the agent summary links every context file it used (e.g. `proposal.md`, `tasks.md`) so I do not hunt under the change folder.not stated
  • ✓1.3After `/opsx:archive`, the agent reply links the archived change folder under `openspec/changes/archive/`.not stated
  • ✓1.4When propose finishes all lite artifacts for a change, the completion summary links every artifact file—not only the last one written.not stated
  • ✓1.5Instructions for opsx commands tell agents to build the **Artifacts** block from CLI JSON so a `quickstart` change is covered without a hardcoded lite filename list.not stated

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-05-19
    • chore(openspec): archive artifact links, readme callout, sso figma pass

History read from a manifest built at 2026-09-30 (09e7bcc).

0 pull requests, found by commits touching the change folder · 1 commit(s) carry no pull request number