@spec-driven-steroids/standards 0.2.2 → 0.2.4

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.
Files changed (6) hide show
  1. package/package.json +2 -2
  2. package/src/templates/antigravity/workflows/spec-driven.md +3 -1
  3. package/src/templates/github/agents/spec-driven.agent.md +4 -2
  4. package/src/templates/opencode/agents/spec-driven.agent.md +4 -2
  5. package/src/templates/universal/skills/spec-driven-task-decomposer/SKILL.md +3 -1
  6. package/src/templates/universal/skills/spec-driven-task-implementer/SKILL.md +2 -1
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@spec-driven-steroids/standards",
3
- "version": "0.2.2",
4
- "description": "Universal prompt standards and platform templates for Spec Driven Steroids",
3
+ "version": "0.2.4",
4
+ "description": "Universal prompt standards and platform templates for Spec-Driven Steroids",
5
5
  "type": "module",
6
6
  "files": [
7
7
  "src",
package/src/templates/antigravity/workflows/spec-driven.md CHANGED
@@ -1,5 +1,5 @@
1
1
  ---
2
- name: Spec Driven
2
+ name: Spec-Driven
3
3
  description: Full Spec-Driven flow (Requirements → Design → Tasks → Code).
4
4
  ---
5
5
 
@@ -41,6 +41,8 @@ If a user asks for direct implementation before requirements, respond with:
41
41
  ## 3. Atomic Tasks
42
42
  - **Action**: Invoke the `spec-driven-task-decomposer` skill.
43
43
  - **Goal**: Break the design into numbered implementation tasks in `specs/changes/<slug>/tasks.md`.
44
+ - **Validation**: Call `mcp:verify_tasks_file` with tasks content and design content to validate phase format, checkbox structure, and traceability.
45
+ - **Validation**: Call `mcp:verify_complete_spec` for `<slug>` to confirm the full requirements/design/tasks workflow before implementation.
44
46
  - **Review**: After writing the file, confirm the task list with the human.
45
47
 
46
48
  ## 4. Implementation
package/src/templates/github/agents/spec-driven.agent.md CHANGED
@@ -1,5 +1,5 @@
1
1
  ---
2
- name: Spec Driven
2
+ name: Spec-Driven
3
3
  description: End-to-end Spec-Driven planner (Requirements → Design → Tasks).
4
4
  ---
5
5
 
@@ -45,7 +45,9 @@ If a user asks for direct implementation before requirements, respond with:
45
45
  **Invoke the `spec-driven-task-decomposer` skill to execute this phase.**
46
46
  1. **Decomposition**: Break the design into small, atomic, and numbered implementation tasks.
47
47
  2. **Traceability**: Link each task to its corresponding `DES-X` and `REQ-X`.
48
- 3. **Artifact**: Save to `specs/changes/<slug>/tasks.md`.
48
+ 3. **Validation**: Call `mcp:verify_tasks_file` with both tasks content and design content. Correct all traceability and structure errors.
49
+ 4. **Artifact**: Save to `specs/changes/<slug>/tasks.md`.
50
+ 5. **Final Planning Validation**: Call `mcp:verify_complete_spec` for `<slug>` before asking to proceed to implementation.
49
51
 
50
52
  ### 4. Implementation Phase
51
53
  **Invoke the `spec-driven-task-implementer` skill to execute this phase.**
package/src/templates/opencode/agents/spec-driven.agent.md CHANGED
@@ -1,5 +1,5 @@
1
1
  ---
2
- name: Spec Driven
2
+ name: Spec-Driven
3
3
  description: Primary agent for Spec-Driven flow (Requirements → Design → Tasks → Build Agent Handoff)
4
4
  mode: primary
5
5
  tools:
@@ -64,7 +64,9 @@ If a user asks for direct implementation before requirements, respond with:
64
64
 
65
65
  1. **Decomposition**: Break the design into small, atomic, and numbered implementation tasks.
66
66
  2. **Traceability**: Link each task to its corresponding `DES-X` and `REQ-X`.
67
- 3. **Artifact**: Save to `specs/changes/<slug>/tasks.md`.
67
+ 3. **Validation**: Call `mcp:verify_tasks_file` with both tasks content and design content. Correct all traceability and structure errors.
68
+ 4. **Artifact**: Save to `specs/changes/<slug>/tasks.md`.
69
+ 5. **Final Planning Validation**: Call `mcp:verify_complete_spec` for `<slug>` before requesting implementation approval.
68
70
 
69
71
  **After saving the file, STOP and ask**: "Human, confirm the task list. Ready for implementation?"
70
72
 
package/src/templates/universal/skills/spec-driven-task-decomposer/SKILL.md CHANGED
@@ -22,7 +22,9 @@ description: Specialized agent for decomposing designs into atomic implementatio
22
22
  7. Order by dependencies
23
23
  8. Add test tasks per TESTING.md strategy
24
24
  9. Include final checkpoint
25
- 10. **Write Before Review**: Save to `specs/changes/<slug>/tasks.md` before asking the human to review or approve
25
+ 10. **Validate Tasks**: Call `mcp:verify_tasks_file` using tasks content and design content; resolve all errors
26
+ 11. **Validate Full Spec**: Call `mcp:verify_complete_spec` for `<slug>` to ensure cross-file traceability is complete
27
+ 12. **Write Before Review**: Save to `specs/changes/<slug>/tasks.md` before asking the human to review or approve
26
28
 
27
29
  ## Output Format
28
30
 
package/src/templates/universal/skills/spec-driven-task-implementer/SKILL.md CHANGED
@@ -68,6 +68,7 @@ specs/changes/<feature-id>/
68
68
  - `specs/changes/<feature-id>/requirements.md` - What to build
69
69
  - `specs/changes/<feature-id>/design.md` - How to build it
70
70
  - `specs/changes/<feature-id>/tasks.md` - Task breakdown
71
+ - Call `mcp:verify_complete_spec` for `<feature-id>` and resolve any blocking errors before starting implementation
71
72
 
72
73
  3. **Discover Context** (use agent engine tools):
73
74
  - Use `Glob` to find relevant files mentioned in design
@@ -85,7 +86,7 @@ Use the checkbox state to track progress:
85
86
  Example:
86
87
 
87
88
  ```markdown
88
- ### Phase 1
89
+ ## Phase 1: Implementation
89
90
 
90
91
  - [ ] 1.1 Add JSON-RPC dispatcher
91
92
  - [ ] 1.2 Add health.check method