jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity

openspec: to-issues renamed to to-tickets (Pocock v1.1) in issue-backlog spec 

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VgG2g9ooqbnBiZYGAonGYG
This commit is contained in:
jared 2026-07-16 16:24:36 -04:00
parent 06fff77d75
commit f2fe45bab8
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
openspec/specs/issue-backlog/spec.md
View File

@ -61,11 +61,11 @@ locally. Priority/autonomy labeling of the filed issue remains the receiving pro
### Requirement: One tracker holds both state and specs ### Requirement: One tracker holds both state and specs
A project SHALL have exactly one configured tracker destination; durable specs A project SHALL have exactly one configured tracker destination; durable specs
(tracer-bullet slices from /to-issues, PRDs) and task-state items are issues on that same (tracer-bullet slices from /to-tickets, PRDs) and task-state items are issues on that same
tracker. The system SHALL NOT create pointer artifacts on a second tracking surface. tracker. The system SHALL NOT create pointer artifacts on a second tracking surface.
#### Scenario: /to-issues publishes a slice chain #### Scenario: /to-tickets publishes a slice chain
- **WHEN** /to-issues publishes tracer-bullet slices for a project with a configured git - **WHEN** /to-tickets publishes tracer-bullet slices for a project with a configured git
tracker tracker
- **THEN** the slices become issues on that tracker and no pointer card or secondary - **THEN** the slices become issues on that tracker and no pointer card or secondary
tracking artifact is created anywhere tracking artifact is created anywhere