speccrew 0.5.9 → 0.5.11
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/.speccrew/agents/speccrew-feature-designer.md +67 -0
- package/.speccrew/agents/speccrew-product-manager.md +69 -0
- package/.speccrew/agents/speccrew-system-designer.md +77 -0
- package/.speccrew/agents/speccrew-system-developer.md +311 -8
- package/.speccrew/agents/speccrew-task-worker.md +34 -0
- package/.speccrew/agents/speccrew-team-leader.md +84 -0
- package/.speccrew/agents/speccrew-test-manager.md +27 -0
- package/.speccrew/skills/{speccrew-dev-desktop → speccrew-dev-desktop-electron}/SKILL.md +38 -50
- package/.speccrew/skills/{speccrew-dev-desktop → speccrew-dev-desktop-electron}/templates/TASK-RECORD-TEMPLATE.md +14 -28
- package/.speccrew/skills/speccrew-dev-desktop-tauri/SKILL.md +341 -0
- package/.speccrew/skills/speccrew-dev-desktop-tauri/templates/TASK-RECORD-TEMPLATE.md +145 -0
- package/.speccrew/skills/speccrew-dev-review-backend/SKILL.md +212 -0
- package/.speccrew/skills/speccrew-dev-review-backend/templates/REVIEW-REPORT-TEMPLATE.md +94 -0
- package/.speccrew/skills/speccrew-dev-review-desktop/SKILL.md +181 -0
- package/.speccrew/skills/speccrew-dev-review-desktop/templates/REVIEW-REPORT-TEMPLATE.md +90 -0
- package/.speccrew/skills/speccrew-dev-review-frontend/SKILL.md +177 -0
- package/.speccrew/skills/speccrew-dev-review-frontend/templates/REVIEW-REPORT-TEMPLATE.md +83 -0
- package/.speccrew/skills/speccrew-dev-review-mobile/SKILL.md +181 -0
- package/.speccrew/skills/speccrew-dev-review-mobile/templates/REVIEW-REPORT-TEMPLATE.md +90 -0
- package/docs/GETTING-STARTED.ar.md +249 -176
- package/docs/GETTING-STARTED.bn.md +108 -412
- package/docs/GETTING-STARTED.bs.md +103 -407
- package/docs/GETTING-STARTED.da.md +267 -190
- package/docs/GETTING-STARTED.de.md +190 -115
- package/docs/GETTING-STARTED.el.md +245 -169
- package/docs/GETTING-STARTED.en.md +97 -22
- package/docs/GETTING-STARTED.es.md +179 -104
- package/docs/GETTING-STARTED.fr.md +191 -116
- package/docs/GETTING-STARTED.it.md +233 -156
- package/docs/GETTING-STARTED.ja.md +242 -167
- package/docs/GETTING-STARTED.ko.md +211 -136
- package/docs/GETTING-STARTED.md +97 -22
- package/docs/GETTING-STARTED.no.md +86 -417
- package/docs/GETTING-STARTED.pl.md +213 -135
- package/docs/GETTING-STARTED.pt-BR.md +94 -396
- package/docs/GETTING-STARTED.ru.md +241 -162
- package/docs/GETTING-STARTED.th.md +104 -405
- package/docs/GETTING-STARTED.tr.md +223 -144
- package/docs/GETTING-STARTED.uk.md +273 -194
- package/docs/GETTING-STARTED.vi.md +98 -399
- package/docs/GETTING-STARTED.zh-TW.md +213 -138
- package/lib/commands/init.js +18 -0
- package/package.json +1 -1
- package/.speccrew/skills/speccrew-dev-review/SKILL.md +0 -451
|
@@ -0,0 +1,181 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: speccrew-dev-review-mobile
|
|
3
|
+
description: SpecCrew Mobile Code Review Skill. Reviews mobile app implementation code against system design documents, API contracts, and platform-specific standards. Generates structured review reports with PASS/PARTIAL/FAIL verdict.
|
|
4
|
+
tools: Read, Glob, Grep
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Trigger Scenarios
|
|
8
|
+
|
|
9
|
+
- When speccrew-system-developer dispatches mobile code review for a completed module
|
|
10
|
+
- When user requests "Review this mobile module's implementation"
|
|
11
|
+
- When user asks "Check if mobile code matches design"
|
|
12
|
+
- When incremental review is needed after partial mobile implementation
|
|
13
|
+
|
|
14
|
+
# Input Parameters
|
|
15
|
+
|
|
16
|
+
| Parameter | Required | Description |
|
|
17
|
+
|-----------|----------|-------------|
|
|
18
|
+
| `design_doc_path` | Yes | Path to mobile module design document |
|
|
19
|
+
| `implementation_report_path` | Yes | Path to mobile development report |
|
|
20
|
+
| `source_root` | Yes | Root directory of mobile source code |
|
|
21
|
+
| `platform_id` | Yes | Mobile platform (mobile-uniapp, mobile-flutter, mobile-react-native) |
|
|
22
|
+
| `api_contract_path` | No | Path to API contract file |
|
|
23
|
+
| `task_id` | Yes | Task identifier from dispatch context |
|
|
24
|
+
| `previous_review_path` | No | Path to previous review report |
|
|
25
|
+
|
|
26
|
+
# Workflow
|
|
27
|
+
|
|
28
|
+
## Absolute Constraints
|
|
29
|
+
|
|
30
|
+
> **Violation = review failure.**
|
|
31
|
+
|
|
32
|
+
1. **READ-ONLY OPERATION** — NEVER modify source code files.
|
|
33
|
+
2. **FORBIDDEN: Code fixes** — Do NOT attempt to fix issues. Only document them.
|
|
34
|
+
3. **MANDATORY: Actionable output** — PARTIAL/FAIL results MUST include specific "Re-dispatch Guidance".
|
|
35
|
+
4. **INCREMENTAL REVIEW SUPPORT** — Skip items already marked as passed in previous review.
|
|
36
|
+
|
|
37
|
+
## Step 1: Load Documents
|
|
38
|
+
|
|
39
|
+
### 1.1 Validate Inputs
|
|
40
|
+
|
|
41
|
+
Verify all required parameters provided. If any missing → Report error, stop.
|
|
42
|
+
|
|
43
|
+
### 1.2 Read Design Document
|
|
44
|
+
|
|
45
|
+
Extract: Module Overview, Page/Component Structure, Native Features, Offline Support requirements.
|
|
46
|
+
|
|
47
|
+
### 1.3 Read Implementation Report
|
|
48
|
+
|
|
49
|
+
Extract: Completed Files, Implementation Status, Known Issues.
|
|
50
|
+
|
|
51
|
+
### 1.4 Read API Contract (if provided)
|
|
52
|
+
|
|
53
|
+
Extract API endpoints for validation against mobile API calls.
|
|
54
|
+
|
|
55
|
+
## Step 2: File Completeness Check
|
|
56
|
+
|
|
57
|
+
### 2.1 Build Expected File List
|
|
58
|
+
|
|
59
|
+
Mobile file categories:
|
|
60
|
+
|
|
61
|
+
| Category | Pattern | Example |
|
|
62
|
+
|----------|---------|---------|
|
|
63
|
+
| Pages | `pages/**/*` or `screens/**/*` | `pages/user/index.vue` |
|
|
64
|
+
| Components | `components/**/*` | `components/UserCard.vue` |
|
|
65
|
+
| Store | `store/**/*` | `store/user.js` |
|
|
66
|
+
| API | `api/**/*` or `services/**/*` | `api/user.js` |
|
|
67
|
+
| Utils | `utils/**/*` | `utils/permission.js` |
|
|
68
|
+
| Native Modules | `native/**/*` or `plugins/**/*` | `native/bridge.js` |
|
|
69
|
+
|
|
70
|
+
### 2.2 Scan Actual Files
|
|
71
|
+
|
|
72
|
+
Use `Glob` to scan `source_root` for implemented files.
|
|
73
|
+
|
|
74
|
+
### 2.3 Calculate Completeness
|
|
75
|
+
|
|
76
|
+
Generate completeness matrix and percentage.
|
|
77
|
+
|
|
78
|
+
## Step 3: Mobile-Specific Compliance Check
|
|
79
|
+
|
|
80
|
+
### 3.1 Mobile Component Check
|
|
81
|
+
|
|
82
|
+
| Check | Rule | Severity |
|
|
83
|
+
|-------|------|----------|
|
|
84
|
+
| Platform Components | Uses correct platform-specific components | ERROR |
|
|
85
|
+
| Component Reuse | Components appropriately reusable | WARN |
|
|
86
|
+
| Native Component Usage | Proper use of native UI components | WARN |
|
|
87
|
+
|
|
88
|
+
### 3.2 Platform Adaptation Validation
|
|
89
|
+
|
|
90
|
+
| Check | Rule | Severity |
|
|
91
|
+
|-------|------|----------|
|
|
92
|
+
| iOS/Android Differences | Platform-specific differences handled | ERROR |
|
|
93
|
+
| Screen Adaptation | Different screen sizes handled | ERROR |
|
|
94
|
+
| Safe Area | Safe area insets respected | ERROR |
|
|
95
|
+
| Platform APIs | Platform-specific APIs correctly used | WARN |
|
|
96
|
+
|
|
97
|
+
### 3.3 Permission Handling Check
|
|
98
|
+
|
|
99
|
+
| Check | Rule | Severity |
|
|
100
|
+
|-------|------|----------|
|
|
101
|
+
| Runtime Permissions | Runtime permission requests implemented | ERROR |
|
|
102
|
+
| Permission Rationale | User-friendly permission explanations | WARN |
|
|
103
|
+
| Denial Handling | Graceful handling of permission denial | ERROR |
|
|
104
|
+
|
|
105
|
+
### 3.4 Offline Support Validation
|
|
106
|
+
|
|
107
|
+
| Check | Rule | Severity |
|
|
108
|
+
|-------|------|----------|
|
|
109
|
+
| Local Storage | Data caching implemented where required | ERROR |
|
|
110
|
+
| Sync Mechanism | Offline data sync strategy implemented | ERROR |
|
|
111
|
+
| Network State | Network connectivity handling | ERROR |
|
|
112
|
+
| Queue Management | Pending request queue management | WARN |
|
|
113
|
+
|
|
114
|
+
### 3.5 Performance Check
|
|
115
|
+
|
|
116
|
+
| Check | Rule | Severity |
|
|
117
|
+
|-------|------|----------|
|
|
118
|
+
| List Rendering | Virtual scrolling for long lists | ERROR |
|
|
119
|
+
| Image Optimization | Image lazy loading and caching | WARN |
|
|
120
|
+
| Memory Management | Proper cleanup of listeners/timers | ERROR |
|
|
121
|
+
| Bundle Size | Code splitting where appropriate | WARN |
|
|
122
|
+
|
|
123
|
+
## Step 4: Generate Review Report
|
|
124
|
+
|
|
125
|
+
### 4.1 Determine Result
|
|
126
|
+
|
|
127
|
+
| Result | Criteria |
|
|
128
|
+
|--------|----------|
|
|
129
|
+
| **PASS** | 100% files created, 0 ERROR-level issues |
|
|
130
|
+
| **PARTIAL** | 70-99% files created, or non-critical ERROR issues |
|
|
131
|
+
| **FAIL** | <70% files created, or critical blockers present |
|
|
132
|
+
|
|
133
|
+
### 4.2 Write Report
|
|
134
|
+
|
|
135
|
+
Generate report at: `speccrew-workspace/iterations/{number}-{type}-{name}/04.development/{platform_id}/[module]-review-report.md`
|
|
136
|
+
|
|
137
|
+
Use template from `templates/REVIEW-REPORT-TEMPLATE.md`.
|
|
138
|
+
|
|
139
|
+
## Step 5: Task Completion Report
|
|
140
|
+
|
|
141
|
+
```markdown
|
|
142
|
+
## Task Completion Report
|
|
143
|
+
- **Status**: SUCCESS
|
|
144
|
+
- **Task ID**: review-{original_task_id}
|
|
145
|
+
- **Platform**: {platform_id}
|
|
146
|
+
- **Module**: {module_name}
|
|
147
|
+
- **Output Files**: {review_report_path}
|
|
148
|
+
- **Summary**: Review {result}: {completed}/{total} files, {error_count} errors
|
|
149
|
+
```
|
|
150
|
+
|
|
151
|
+
# Severity Levels
|
|
152
|
+
|
|
153
|
+
| Level | Definition | Action Required |
|
|
154
|
+
|-------|------------|-----------------|
|
|
155
|
+
| **CRITICAL** | Security vulnerability or data integrity issue | Must fix immediately |
|
|
156
|
+
| **ERROR** | Blocking functionality or violating core requirements | Must fix before PASS |
|
|
157
|
+
| **WARN** | Best practice violation or missing documentation | Should fix |
|
|
158
|
+
| **LOW** | Code style or minor optimization suggestion | Optional |
|
|
159
|
+
|
|
160
|
+
# Key Rules
|
|
161
|
+
|
|
162
|
+
| Rule | Description |
|
|
163
|
+
|------|-------------|
|
|
164
|
+
| **Read-Only** | NEVER modify any source code |
|
|
165
|
+
| **Blueprint-Driven** | Validate against design document specifications |
|
|
166
|
+
| **Actionable Output** | PARTIAL/FAIL must include specific fix guidance |
|
|
167
|
+
| **Platform-Specific** | Consider iOS/Android platform differences |
|
|
168
|
+
| **Completeness First** | File existence is primary check before content validation |
|
|
169
|
+
|
|
170
|
+
# Checklist
|
|
171
|
+
|
|
172
|
+
- [ ] All required inputs validated
|
|
173
|
+
- [ ] Design document loaded and parsed
|
|
174
|
+
- [ ] File completeness check completed
|
|
175
|
+
- [ ] Mobile components validated
|
|
176
|
+
- [ ] Platform adaptation checked
|
|
177
|
+
- [ ] Permission handling verified
|
|
178
|
+
- [ ] Offline support validated
|
|
179
|
+
- [ ] Performance checks completed
|
|
180
|
+
- [ ] Review report written with clear verdict
|
|
181
|
+
- [ ] Re-dispatch guidance provided for PARTIAL/FAIL
|
|
@@ -0,0 +1,90 @@
|
|
|
1
|
+
# Mobile Code Review Report
|
|
2
|
+
|
|
3
|
+
## Summary
|
|
4
|
+
|
|
5
|
+
- **Task ID**: {task_id}
|
|
6
|
+
- **Platform**: {platform_id}
|
|
7
|
+
- **Module**: {module_name}
|
|
8
|
+
- **Review Date**: {review_date}
|
|
9
|
+
- **Review Result**: PASS | PARTIAL | FAIL
|
|
10
|
+
- **Completeness**: {completed_files}/{total_files} ({percentage}%)
|
|
11
|
+
|
|
12
|
+
## File Completeness
|
|
13
|
+
|
|
14
|
+
| Category | Required | Created | Missing |
|
|
15
|
+
|----------|----------|---------|---------|
|
|
16
|
+
| Pages | {n} | {n} | {n} |
|
|
17
|
+
| Components | {n} | {n} | {n} |
|
|
18
|
+
| Store | {n} | {n} | {n} |
|
|
19
|
+
| API | {n} | {n} | {n} |
|
|
20
|
+
| Utils | {n} | {n} | {n} |
|
|
21
|
+
| Native Modules | {n} | {n} | {n} |
|
|
22
|
+
| **Total** | **{n}** | **{n}** | **{n}** |
|
|
23
|
+
|
|
24
|
+
## Missing Files
|
|
25
|
+
|
|
26
|
+
1. `{expected_path_1}`
|
|
27
|
+
2. `{expected_path_2}`
|
|
28
|
+
...
|
|
29
|
+
|
|
30
|
+
## Mobile Component Issues
|
|
31
|
+
|
|
32
|
+
| Severity | File | Issue Description |
|
|
33
|
+
|----------|------|-------------------|
|
|
34
|
+
| ERROR | `{file}` | {description} |
|
|
35
|
+
| WARN | `{file}` | {description} |
|
|
36
|
+
|
|
37
|
+
## Platform Adaptation Issues
|
|
38
|
+
|
|
39
|
+
| Severity | Aspect | Issue Description |
|
|
40
|
+
|----------|--------|-------------------|
|
|
41
|
+
| ERROR | iOS/Android | {description} |
|
|
42
|
+
| ERROR | Screen Adapt | {description} |
|
|
43
|
+
| ERROR | Safe Area | {description} |
|
|
44
|
+
| WARN | Platform API | {description} |
|
|
45
|
+
|
|
46
|
+
## Permission Handling Issues
|
|
47
|
+
|
|
48
|
+
| Severity | Permission | Issue Description |
|
|
49
|
+
|----------|------------|-------------------|
|
|
50
|
+
| ERROR | `{permission}` | {description} |
|
|
51
|
+
| WARN | `{permission}` | {description} |
|
|
52
|
+
|
|
53
|
+
## Offline Support Issues
|
|
54
|
+
|
|
55
|
+
| Severity | Aspect | Issue Description |
|
|
56
|
+
|----------|--------|-------------------|
|
|
57
|
+
| ERROR | Local Storage | {description} |
|
|
58
|
+
| ERROR | Sync Mechanism | {description} |
|
|
59
|
+
| ERROR | Network State | {description} |
|
|
60
|
+
| WARN | Queue Management | {description} |
|
|
61
|
+
|
|
62
|
+
## Performance Issues
|
|
63
|
+
|
|
64
|
+
| Severity | Aspect | Issue Description |
|
|
65
|
+
|----------|--------|-------------------|
|
|
66
|
+
| ERROR | List Rendering | {description} |
|
|
67
|
+
| ERROR | Memory Management | {description} |
|
|
68
|
+
| WARN | Image Optimization | {description} |
|
|
69
|
+
| WARN | Bundle Size | {description} |
|
|
70
|
+
|
|
71
|
+
## Verdict
|
|
72
|
+
|
|
73
|
+
{Detailed verdict explanation based on findings.}
|
|
74
|
+
|
|
75
|
+
## Re-dispatch Guidance
|
|
76
|
+
|
|
77
|
+
Priority items for next dev worker:
|
|
78
|
+
|
|
79
|
+
1. **{priority_item_1}** - {detailed description}
|
|
80
|
+
2. **{priority_item_2}** - {detailed description}
|
|
81
|
+
3. **{priority_item_3}** - {detailed description}
|
|
82
|
+
|
|
83
|
+
## Issue Statistics
|
|
84
|
+
|
|
85
|
+
| Severity | Count |
|
|
86
|
+
|----------|-------|
|
|
87
|
+
| CRITICAL | {n} |
|
|
88
|
+
| ERROR | {n} |
|
|
89
|
+
| WARN | {n} |
|
|
90
|
+
| LOW | {n} |
|