bms-speckit-plugin 2.0.0 → 2.0.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.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "bms-speckit-plugin",
3
- "version": "2.0.0",
3
+ "version": "2.0.1",
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/",
@@ -11,10 +11,6 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Skill, Agent, WebSearch, Web
11
11
  Takes a single requirement and runs the complete engineering workflow automatically:
12
12
  **constitution → specify → plan → tasks → analyze → implement → verify**
13
13
 
14
- ## Input Requirement
15
-
16
- $ARGUMENTS
17
-
18
14
  ## Engineering Constitution
19
15
 
20
16
  All work follows these principles:
@@ -38,7 +34,8 @@ All work follows these principles:
38
34
  - Commit: `feat: establish engineering constitution`
39
35
 
40
36
  ### Step 2: Create Specification
41
- - Analyze the requirement: $ARGUMENTS
37
+ - The user's requirement is provided as the command argument: $ARGUMENTS
38
+ - Analyze this requirement thoroughly
42
39
  - If database access is needed and MCP tools are available (list_tables, describe_table, query), explore the actual database schema
43
40
  - Create `specs/{feature-name}/specification.md` containing:
44
41
  - Overview and user requirements