bms-speckit-plugin 3.0.0 → 3.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bms-speckit-plugin",
-  "version": "3.0.0",
+  "version": "3.1.0",
   "description": "Single-command automated development pipeline: /bms-speckit takes requirements and runs constitution → specify → plan → tasks → analyze → implement → verify",
   "files": [
     ".claude-plugin/",

package/skills/speckit/SKILL.md

@@ -8,39 +8,92 @@ allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Skill, Agent, WebSearch, Web
 
 # BMS Speckit — Automated Development Pipeline
 
-Takes a single requirement and runs the complete engineering workflow automatically by calling sub-skills in sequence. Do NOT ask for confirmation between steps.
+Takes a single requirement and runs the complete engineering workflow. Do NOT ask for confirmation between steps.
 
 ## Step 1: Constitution
-Invoke skill `bms-speckit:constitution` with the following constitution text:
+
+Create `specs/constitution.md` with these principles:
 
 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.
 
+Also verify CLAUDE.md complies with the constitution. Update if needed.
+Commit: `feat: establish engineering constitution`
+
 ## Step 2: Specify
-Invoke skill `bms-speckit:specify` with this requirement: $ARGUMENTS
+
+Analyze this requirement: $ARGUMENTS
+
+If database access is needed and MCP tools are available (list_tables, describe_table, query), explore the actual database schema.
+
+Create `specs/{feature-name}/specification.md` containing:
+- Overview and user requirements
+- Functional requirements (numbered, testable)
+- Non-functional requirements (performance, security, UX)
+- Technical analysis (database schema, API dependencies)
+- Architecture (components, data flow)
+- UI/UX design (screens, navigation, interactions)
+- Data model (tables, relationships, queries)
+- Constraints and success criteria
+
+Commit: `feat: add specification for {feature-name}`
 
 ## Step 3: Plan
-Invoke skill `bms-speckit:plan`
+
+Read the specification and create `specs/{feature-name}/plan.md` containing:
+- Architecture overview and file structure
+- Implementation phases: Foundation → Core → UI → Integration → Testing
+- Technology stack with justification
+- Testing strategy (what to test, coverage targets)
+- Risk assessment
+
+Commit: `feat: add implementation plan for {feature-name}`
 
 ## Step 4: Compact
-Run `/compact` to free context window after heavy specification and planning work.
+
+Run `/compact` to free context window.
 
 ## Step 5: Tasks
-Invoke skill `bms-speckit:tasks`
+
+Read the plan and create `specs/{feature-name}/tasks.md` with granular tasks (5-15 min each):
+
+```
+### Task N: {Name}
+- **Status**: pending
+- **Priority**: high | medium | low
+- **Phase**: N
+- **Files**: exact file paths
+- **Description**: specific and actionable
+- **Tests**: what tests to write first
+- **Acceptance**: measurable verification criteria
+- **Commit message**: descriptive message
+```
+
+Order: setup → data layer → business logic → UI → integration → polish
+Commit: `feat: add task list for {feature-name}`
 
 ## Step 6: Analyze
-Invoke skill `bms-speckit:analyze`
+
+Review all tasks for quality:
+- Granular enough? (5-15 min each)
+- Each independently testable?
+- Dependencies correct and explicit?
+- Every task has test-first step?
+- Acceptance criteria clear and measurable?
+
+Fix any issues found in tasks.md. Commit if changes made.
 
 ## Step 7: Commit and push
+
 Commit all spec files and push to remote if configured.
 
 ## Step 8: Compact
+
 Run `/compact` to free context window before implementation.
 
 ## Step 9: Implement with ralph-loop
-Invoke ralph-loop to implement all tasks automatically:
 
 ```
-/ralph-loop:ralph-loop "Invoke skill bms-speckit:implement to execute the next pending task. Repeat until all tasks in specs/*/tasks.md are finished. Do not ask for any confirmation. Once all tasks are done, invoke skill bms-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
+/ralph-loop:ralph-loop "Read specs/*/tasks.md. Find the next pending task. Execute it using TDD: write test first, verify fail, implement, verify pass, commit. Update task status to completed. Do not ask for any confirmation. Once all tasks are done, recheck all tasks, run full test suite, fix any issues, and output <promise>FINISHED</promise> only after all tasks are completed and revalidated" --completion-promise "FINISHED" --max-iterations 10
 ```
 
 ## After ralph-loop completes
@@ -53,6 +106,7 @@ Output a final summary:
 
 ## CRITICAL RULES
 - Do NOT ask for confirmation between steps
-- Each step invokes its sub-skill — do not implement inline
+- Do NOT skip TDD — test first, always
+- Commit after EVERY completed task
 - Use MCP tools if available (bms-session for database access)
 - Push code if git remote is configured

package/skills/analyze/SKILL.md

@@ -1,33 +0,0 @@
----
-name: analyze
-description: Review tasks and implementation for quality and constitution compliance
-user-invocable: false
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent
----
-
-# Speckit Analyze
-
-Review tasks and/or implementation for quality and compliance.
-
-## Instructions
-
-1. Read `specs/constitution.md` for governing principles.
-
-2. Find and read the most recent `specs/*/tasks.md`.
-
-3. If tasks are pending — review task quality:
-   - Granular enough? (5-15 min each)
-   - Each independently testable?
-   - Dependencies correct?
-   - Every task has test-first step?
-   - Acceptance criteria clear?
-
-4. If tasks are completed — review implementation:
-   - Read the code written for completed tasks
-   - Check tests exist and are meaningful
-   - Check for code duplication
-   - Check error handling and UX feedback
-
-5. Fix any issues found in tasks.md. Add new tasks if needed.
-
-6. Commit if changes made.

package/skills/constitution/SKILL.md

@@ -1,48 +0,0 @@
----
-name: constitution
-description: Establish engineering principles that govern all speckit development work
-user-invocable: false
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
----
-
-# Speckit Constitution
-
-Establish the engineering constitution for this project.
-
-## Instructions
-
-1. Read the constitution text from the conversation context. If none provided, use the default principles below.
-
-2. Create `specs/` directory if it doesn't exist.
-
-3. Write `specs/constitution.md` with:
-
-```markdown
-# Engineering Constitution
-
-Established: {current date}
-
-## Principles
-
-{constitution text, formatted as numbered principles}
-
-## Enforcement
-
-All speckit commands must comply with these principles.
-```
-
-4. Check if CLAUDE.md exists. If it does, verify it aligns with the constitution and update if needed.
-
-5. Commit: `feat: establish engineering constitution`
-
-## Default Principles
-
-1. Code Quality — No hardcoded conditions, strict TypeScript, no shortcuts
-2. TDD — Always write tests FIRST, confirm failure, then implement
-3. Testing — Unit, component, integration, and API tests as appropriate
-4. UX — Consistent, professional, user-friendly interfaces with clear feedback
-5. Performance — Efficient architecture and resource management
-6. Version Control — Commit after every meaningful change with descriptive messages
-7. Reusability — Modular components, centralized business logic, no duplication
-8. User Feedback — Informative progress reporting and error messages
-9. Tool Leverage — Use all available skills, MCP tools, frameworks, and domain expertise

package/skills/implement/SKILL.md

@@ -1,27 +0,0 @@
----
-name: implement
-description: Execute the next pending task from tasks.md using TDD
-user-invocable: false
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, WebSearch, WebFetch
----
-
-# Speckit Implement
-
-Execute the next pending task using TDD.
-
-## Instructions
-
-1. Find `specs/*/tasks.md`. Find the first task with status `pending`.
-
-2. Update its status to `in_progress`.
-
-3. Execute TDD cycle:
-   a. Write the test first
-   b. Run tests — verify they FAIL
-   c. Write minimal implementation to pass
-   d. Run ALL tests — verify they PASS
-   e. Commit with the task's commit message
-
-4. Update task status to `completed`.
-
-5. Report: task name, tests passing, files changed, next pending task (or "all done").

package/skills/plan/SKILL.md

@@ -1,25 +0,0 @@
----
-name: plan
-description: Create an implementation plan from the most recent specification
-user-invocable: false
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
----
-
-# Speckit Plan
-
-Create a detailed implementation plan from the most recent specification.
-
-## Instructions
-
-1. Read `specs/constitution.md` for governing principles.
-
-2. Find and read the most recent `specs/*/specification.md`.
-
-3. Create `specs/{feature-name}/plan.md` containing:
-   - Architecture overview and file structure
-   - Implementation phases: Foundation → Core → UI → Integration → Testing
-   - Technology stack with justification
-   - Testing strategy (what to test, coverage targets)
-   - Risk assessment
-
-4. Commit: `feat: add implementation plan for {feature-name}`

package/skills/specify/SKILL.md

@@ -1,32 +0,0 @@
----
-name: specify
-description: Create a detailed specification from user requirements
-user-invocable: false
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep, Agent, WebSearch, WebFetch
----
-
-# Speckit Specify
-
-Create a detailed technical specification from the requirement provided in conversation context.
-
-## Instructions
-
-1. Read `specs/constitution.md` for governing principles.
-
-2. Read the requirement from conversation context.
-
-3. If database access is needed and MCP tools are available (list_tables, describe_table, query), explore the actual database schema.
-
-4. Create a feature directory name from the requirements (kebab-case).
-
-5. Write `specs/{feature-name}/specification.md` containing:
-   - Overview and user requirements
-   - Functional requirements (numbered, testable)
-   - Non-functional requirements (performance, security, UX)
-   - Technical analysis (database schema, API dependencies)
-   - Architecture (components, data flow)
-   - UI/UX design (screens, navigation, interactions)
-   - Data model (tables, relationships, queries)
-   - Constraints and success criteria
-
-6. Commit: `feat: add specification for {feature-name}`

package/skills/tasks/SKILL.md

@@ -1,34 +0,0 @@
----
-name: tasks
-description: Break an implementation plan into executable tasks with status tracking
-user-invocable: false
-allowed-tools: Read, Write, Edit, Bash, Glob, Grep
----
-
-# Speckit Tasks
-
-Break the implementation plan into granular, executable tasks.
-
-## Instructions
-
-1. Read `specs/constitution.md` for governing principles.
-
-2. Find and read the most recent `specs/*/plan.md`.
-
-3. Create `specs/{feature-name}/tasks.md` with granular tasks (5-15 min each):
-
-```
-### Task N: {Name}
-- **Status**: pending
-- **Priority**: high | medium | low
-- **Phase**: N
-- **Files**: exact file paths
-- **Description**: specific and actionable
-- **Tests**: what tests to write first
-- **Acceptance**: measurable verification criteria
-- **Commit message**: descriptive message
-```
-
-4. Order: setup → data layer → business logic → UI → integration → polish
-
-5. Commit: `feat: add task list for {feature-name}`