bms-speckit-plugin 5.2.0 → 5.2.1
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.
|
@@ -157,3 +157,13 @@ Remaining (needs user review): X
|
|
|
157
157
|
- Run tests after EVERY fix to prevent regressions
|
|
158
158
|
- Commit fixes with descriptive messages
|
|
159
159
|
- If you cannot fix an issue, explain why and what the user should do
|
|
160
|
+
|
|
161
|
+
**Completion Signal:**
|
|
162
|
+
|
|
163
|
+
After your report, you MUST output exactly one of these lines as the **last line** of your response:
|
|
164
|
+
|
|
165
|
+
- `QC_RESULT: PASS` — build, lint, and tests all pass; no unfixed critical security issues
|
|
166
|
+
- `QC_RESULT: PASS_WITH_NOTES` — all critical checks pass but some items flagged for user review (e.g., major dependency updates)
|
|
167
|
+
- `QC_RESULT: FAIL` — unfixed build errors, test failures, or critical security vulnerabilities remain
|
|
168
|
+
|
|
169
|
+
Both `PASS` and `PASS_WITH_NOTES` allow the pipeline to proceed to merge. Only `FAIL` blocks progression.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "bms-speckit-plugin",
|
|
3
|
-
"version": "5.2.
|
|
3
|
+
"version": "5.2.1",
|
|
4
4
|
"description": "Chain-orchestrated development pipeline: /bms-speckit takes requirements and runs brainstorm → constitution → specify → plan → tasks → analyze → implement → verify with per-step error handling",
|
|
5
5
|
"files": [
|
|
6
6
|
".claude-plugin/",
|
|
@@ -178,7 +178,7 @@ After the subagent completes, update tasks 1-7 as completed using TaskUpdate, th
|
|
|
178
178
|
- **D. Accessibility** — alt text, form labels, keyboard nav, heading hierarchy
|
|
179
179
|
- **E. Integration check** — verify all components work together end-to-end
|
|
180
180
|
- The agent fixes everything it can. Major dependency updates are flagged for user review.
|
|
181
|
-
-
|
|
181
|
+
- **Completion rule:** When the QC agent returns its report, proceed to Step 11 **unless** the report contains unfixed build errors, unfixed test failures, or unfixed critical security vulnerabilities. Informational findings, flagged-for-review items, and already-fixed issues do NOT block progression. If uncertain, proceed — the QC agent already fixed what it could.
|
|
182
182
|
- **Post-action:** Commit all fixes and push. Message: `fix(speckit): final QC — security, deps, UX consistency, accessibility`
|
|
183
183
|
- **Done:** Update task 10 as completed. Output `[Step 10/11] DONE — quality gate passed`
|
|
184
184
|
|