gmc-openspec 1.4.4 → 1.4.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -107,11 +107,18 @@ ${SHARED_GUARDRAILS}
|
|
|
107
107
|
|
|
108
108
|
Each story must have independent review value, clear AC, scope, non-goals, dependencies, and a traceable requirement source. Avoid one giant change and avoid tiny implementation-only fragments.
|
|
109
109
|
|
|
110
|
+
## Story Title Format
|
|
111
|
+
|
|
112
|
+
- In \`stories.md\`, each story heading/title MUST include a split marker in \`[S-x]\` form, using the story sequence visible to reviewers, for example \`## [S-1] Add refund endpoint\`.
|
|
113
|
+
- If the affected repository is known from Jira fields, requirement text, workspace context, or existing mapping, include the short repository abbreviation in bracket form before the story marker, for example \`## [api] [S-1] Add refund endpoint\`.
|
|
114
|
+
- For multi-repo stories, include each known repository abbreviation as its own bracket, for example \`## [web] [api] [S-2] Wire checkout status\`.
|
|
115
|
+
- If the affected repository cannot be determined with confidence, omit the repo bracket instead of inventing one.
|
|
116
|
+
|
|
110
117
|
## Steps
|
|
111
118
|
|
|
112
119
|
1. Run \`openspec jira validate <JIRA-ID> --stage requirement --json\`.
|
|
113
120
|
2. Read \`intake.yaml\` to get \`documentLanguage\`, plus \`requirement.md\`, \`mapping.yaml\`, and existing OpenSpec specs if capability choices are unclear.
|
|
114
|
-
3. Write \`stories.md\` using \`documentLanguage\`, with stable English/code story ids, titles, scope, non-goals, AC, dependencies, risks, and suggested OpenSpec change names.
|
|
121
|
+
3. Write \`stories.md\` using \`documentLanguage\`, with stable English/code story ids, titles following the Story Title Format, scope, non-goals, AC, dependencies, risks, and suggested OpenSpec change names.
|
|
115
122
|
4. Update \`mapping.yaml\` so every Jira AC maps to at least one story.
|
|
116
123
|
5. Set \`intake.yaml\` status to \`split\` and ask the user to review the story split.
|
|
117
124
|
6. After explicit user approval, set status to \`stories-reviewed\` and run \`openspec jira validate <JIRA-ID> --stage stories\`.
|