speccrew 0.5.8 → 0.5.9

package/.speccrew/skills/speccrew-sd-backend/SKILL.md

@@ -266,6 +266,9 @@ After completing all steps, output a structured completion report for the System
 | **Explicit Transaction Boundaries** | Transaction boundaries must be explicitly marked |
 | **Exception Code Mapping** | Exception handling must map to API Contract error codes |
 | **Follow Techs Conventions** | Naming, directory structure, patterns from techs knowledge |
+| **FORBIDDEN: TODO/FIXME Placeholders** | Design documents MUST contain complete implementation logic. Do NOT use TODO, FIXME, HACK, or any placeholder comments. Every method, validation rule, and business logic MUST be fully specified with actual pseudocode. |
+| **API Route Consistency** | All API routes in the design document MUST exactly match the routes defined in the API Contract document. Before writing any route, READ the API Contract and copy routes verbatim. Do NOT invent or modify routes. |
+| **Cross-Feature Dependency Marking** | When referencing functionality from another Feature (e.g., conflict detection from F-APPT-002), MUST explicitly mark it as `[DEPENDENCY: F-XXX-NNN]` and define a degradation strategy for when that Feature is not yet implemented. |
 
 # Mermaid Diagram Requirements
 
@@ -296,3 +299,6 @@ When generating Mermaid diagrams, follow compatibility guidelines:
 - [ ] INDEX.md generated with complete module list
 - [ ] All files written to correct paths under 03.system-design/{platform_id}/
 - [ ] All Mermaid diagrams follow compatibility guidelines
+- [ ] **No TODO/FIXME placeholders** — all methods have complete pseudocode implementation
+- [ ] **API routes match API Contract exactly** — verified route-by-route
+- [ ] **Cross-Feature dependencies explicitly marked** — all `[DEPENDENCY: F-XXX-NNN]` tags present with degradation strategy

package/.speccrew/skills/speccrew-sd-frontend/SKILL.md

@@ -263,6 +263,10 @@ After completing all steps, output a structured completion report for the System
 | **One Module Per Function Group** | Each module design document maps to one or more related Feature Spec functions |
 | **Status Markers Required** | Use [EXISTING], [MODIFIED], [NEW] markers for all components and store modules |
 | **Follow Techs Conventions** | Naming, directory structure, patterns must follow techs knowledge |
+| **FORBIDDEN: TODO/FIXME Placeholders** | Design documents MUST contain complete implementation logic. Do NOT use TODO, FIXME, HACK, or any placeholder comments. Every component, method, and interaction MUST be fully specified with actual pseudocode. |
+| **API Route Consistency** | All API routes in the design document MUST exactly match the routes defined in the API Contract document. Before writing any route, READ the API Contract and copy routes verbatim. Do NOT invent or modify routes. |
+| **Cross-Feature Dependency Marking** | When referencing functionality from another Feature (e.g., conflict detection from F-APPT-002), MUST explicitly mark it as `[DEPENDENCY: F-XXX-NNN]` and define a degradation strategy (e.g., hide button, show placeholder) for when that Feature is not yet implemented. |
+| **Mermaid for All Diagrams** | ALL component trees, interaction flows, and state management diagrams MUST use Mermaid syntax (`graph TB`, `sequenceDiagram`, `flowchart`). Plain text ASCII diagrams are FORBIDDEN for these sections. |
 
 # Checklist
 
@@ -277,3 +281,7 @@ After completing all steps, output a structured completion report for the System
 - [ ] INDEX.md generated with complete module list
 - [ ] All files written to correct paths under 03.system-design/{platform_id}/
 - [ ] Checkpoint A passed: function extraction confirmed with user
+- [ ] **No TODO/FIXME placeholders** — all components and methods have complete pseudocode
+- [ ] **API routes match API Contract exactly** — verified route-by-route
+- [ ] **Cross-Feature dependencies explicitly marked** — all `[DEPENDENCY: F-XXX-NNN]` tags present with degradation strategy
+- [ ] **Mermaid diagrams used** — no ASCII text diagrams for flows or component trees

package/.speccrew/skills/speccrew-sd-mobile/SKILL.md

@@ -253,6 +253,10 @@ After completing all steps, output a structured completion report for the System
 | **Follow Techs Conventions** | Naming, directory structure, patterns must follow techs knowledge |
 | **Platform-Specific Handling** | Properly handle iOS/Android differences, permissions, and native integrations |
 | **Offline Support** | Consider offline-first patterns where applicable |
+| **FORBIDDEN: TODO/FIXME Placeholders** | Design documents MUST contain complete implementation logic. Do NOT use TODO, FIXME, HACK, or any placeholder comments. Every screen, component, and method MUST be fully specified with actual pseudocode. |
+| **API Route Consistency** | All API routes in the design document MUST exactly match the routes defined in the API Contract document. Before writing any route, READ the API Contract and copy routes verbatim. Do NOT invent or modify routes. |
+| **Cross-Feature Dependency Marking** | When referencing functionality from another Feature (e.g., conflict detection from F-APPT-002), MUST explicitly mark it as `[DEPENDENCY: F-XXX-NNN]` and define a degradation strategy (e.g., hide button, show placeholder) for when that Feature is not yet implemented. |
+| **Mermaid for All Diagrams** | ALL screen trees, navigation flows, interaction sequences, and state diagrams MUST use Mermaid syntax (`graph TB`, `sequenceDiagram`, `flowchart`). Plain text ASCII diagrams are FORBIDDEN for these sections. |
 
 # Checklist
 
@@ -269,4 +273,8 @@ After completing all steps, output a structured completion report for the System
 - [ ] App lifecycle handling documented
 - [ ] INDEX.md generated with complete module list
 - [ ] All files written to correct paths under 03.system-design/{platform_id}/
-- [ ] Checkpoint A passed: function extraction confirmed with user
+- [ ] **Checkpoint A passed**: function extraction confirmed with user
+- [ ] **No TODO/FIXME placeholders** — all screens and methods have complete pseudocode
+- [ ] **API routes match API Contract exactly** — verified route-by-route
+- [ ] **Cross-Feature dependencies explicitly marked** — all `[DEPENDENCY: F-XXX-NNN]` tags present with degradation strategy
+- [ ] **Mermaid diagrams used** — no ASCII text diagrams for flows or screen trees

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "speccrew",
-  "version": "0.5.8",
+  "version": "0.5.9",
   "description": "Spec-Driven Development toolkit for AI-powered IDEs",
   "author": "charlesmu99",
   "repository": {