bms-speckit-plugin 3.7.0 → 3.8.0
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.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "bms-speckit-plugin",
|
|
3
|
-
"version": "3.
|
|
3
|
+
"version": "3.8.0",
|
|
4
4
|
"description": "Single-command automated development pipeline: /bms-speckit takes requirements and runs constitution → specify → plan → tasks → analyze → implement → verify",
|
|
5
5
|
"files": [
|
|
6
6
|
".claude-plugin/",
|
|
@@ -19,17 +19,17 @@ Subagent prompt:
|
|
|
19
19
|
"""
|
|
20
20
|
You are running the BMS Speckit specification and planning phase. Execute these steps in order using the Skill tool. Do NOT ask for confirmation.
|
|
21
21
|
|
|
22
|
-
Step 1: Use the Skill tool to invoke "speckit
|
|
22
|
+
Step 1: Use the Skill tool to invoke "speckit.constitution" with this argument: "Establish and enforce a comprehensive set of engineering principles that prioritize high code quality, strict adherence to Test-Driven Development (TDD) practices, and well-defined testing standards across unit, component, integration, and API levels to ensure system reliability and maintainability; maintain a consistent, user-friendly, and professional user interface aligned with strong user experience (UX) guidelines; optimize application performance through efficient architecture and resource management; enforce disciplined version control practices with frequent, atomic commits to minimize risk and improve traceability; promote the development and reuse of modular components and functions while centralizing business logic to avoid duplication and ensure consistency; provide clear, informative user feedback and progress reporting throughout system interactions; and leverage all available tools, frameworks, and domain-specific expertise to support developers in delivering robust, scalable, and high-quality applications."
|
|
23
23
|
|
|
24
24
|
Step 2: Read CLAUDE.md and verify it complies with the constitution in specs/constitution.md. Update CLAUDE.md if needed.
|
|
25
25
|
|
|
26
|
-
Step 3: Use the Skill tool to invoke "speckit
|
|
26
|
+
Step 3: Use the Skill tool to invoke "speckit.specify" with this argument: "$ARGUMENTS"
|
|
27
27
|
|
|
28
|
-
Step 4: Use the Skill tool to invoke "speckit
|
|
28
|
+
Step 4: Use the Skill tool to invoke "speckit.plan"
|
|
29
29
|
|
|
30
|
-
Step 5: Use the Skill tool to invoke "speckit
|
|
30
|
+
Step 5: Use the Skill tool to invoke "speckit.tasks"
|
|
31
31
|
|
|
32
|
-
Step 6: Use the Skill tool to invoke "speckit
|
|
32
|
+
Step 6: Use the Skill tool to invoke "speckit.analyze"
|
|
33
33
|
|
|
34
34
|
Step 7: Commit all files and push to remote if configured.
|
|
35
35
|
|
|
@@ -42,4 +42,4 @@ After the subagent completes:
|
|
|
42
42
|
|
|
43
43
|
8. Run `/compact` to free context window.
|
|
44
44
|
|
|
45
|
-
9. Run: `/ralph-loop:ralph-loop "use the Skill tool to invoke speckit
|
|
45
|
+
9. Run: `/ralph-loop:ralph-loop "use the Skill tool to invoke speckit.implement until all tasks in specs/*/tasks.md are finished;do not ask for any confirmation; once all tasks are done, use the Skill tool to invoke speckit.analyze to recheck and update tasks, accept any recommendations, and output <promise>FINISHED</promise> only after all tasks are completed and revalidated" --completion-promise "FINISHED" --max-iterations 10`
|