speccrew 0.1.0

package/.speccrew/skills/speccrew-dev-frontend/templates/TASK-RECORD-TEMPLATE.md

@@ -0,0 +1,115 @@
+# Frontend Development Task Record - {feature-name}
+
+<!-- AI-NOTE: This is the task record template. Fill all {placeholders} when creating the actual task record. -->
+
+> Platform: {platform_id}  
+> Iteration: {iteration-path}  
+> Created: {date}  
+> Developer: Dev Agent
+
+---
+
+## Design Document References
+
+| Document | Path | Status |
+|----------|------|--------|
+| Platform INDEX | `03.system-design/{platform_id}/INDEX.md` | Reference |
+| Module Design 1 | `03.system-design/{platform_id}/{module1}-design.md` | Reference |
+| Module Design 2 | `03.system-design/{platform_id}/{module2}-design.md` | Reference |
+| API Contract | `02.feature-design/{feature-name}-api-contract.md` | Reference |
+
+---
+
+## Task Checklist
+
+<!-- AI-NOTE: Generate one row per implementation task. Status values: Pending / In Progress / Done / Blocked. Dependencies must reference Task IDs. -->
+
+| Task ID | Module | Description | Target Files | Dependencies | Status | Notes |
+|---------|--------|-------------|--------------|--------------|--------|-------|
+| FE-001 | {module} | {description} | `{file-path}` | - | Pending | <!-- AI-NOTE: Add implementation notes here --> |
+| FE-002 | {module} | {description} | `{file-path}` | FE-001 | Pending | |
+| FE-003 | {module} | {description} | `{file-path}` | - | Pending | |
+
+> **Status Legend**: Pending / In Progress / Done / Blocked
+
+---
+
+## Deviation Log
+
+<!-- AI-NOTE: Record ANY deviation from design with clear reasons. This is mandatory for traceability. -->
+
+| Task ID | Design Intent | Actual Implementation | Reason |
+|---------|---------------|----------------------|--------|
+| <!-- AI-NOTE: Example: FE-002 --> | <!-- AI-NOTE: Example: Use Pinia store --> | <!-- AI-NOTE: Example: Used React Context --> | <!-- AI-NOTE: Example: Project uses React, not Vue --> |
+
+<!-- AI-NOTE: If no deviations, write: "No deviations. All implementations followed design documents." -->
+
+---
+
+## Local Check Results
+
+<!-- AI-NOTE: Record check results per task batch. Update as tasks complete. -->
+
+### Batch: {batch-name}
+
+| Check Type | Command | Result | Notes |
+|------------|---------|--------|-------|
+| Lint | `npm run lint` | Pass / Fail | |
+| Type Check | `npx tsc --noEmit` | Pass / Fail | <!-- AI-NOTE: Only for TypeScript projects --> |
+| Unit Tests | `npm test` | Pass / Fail | |
+| Quick Verify | Manual | Pass / Fail | |
+
+### Issues Found
+
+<!-- AI-NOTE: List any issues encountered during local checks. -->
+
+| Task ID | Issue | Severity | Resolution |
+|---------|-------|----------|------------|
+| | | High / Medium / Low | |
+
+---
+
+## Tech Debt References
+
+<!-- AI-NOTE: Link to tech-debt files created during development. Tech debt is written to iterations/{iter}/tech-debt/ (not platform-specific). -->
+
+| Debt ID | Title | File Path | Priority |
+|---------|-------|-----------|----------|
+| TD-001 | {title} | `tech-debt/{debt-id}.md` | High / Medium / Low |
+
+<!-- AI-NOTE: If no tech debt, write: "No tech debt identified during this development." -->
+
+---
+
+## Completion Summary
+
+<!-- AI-NOTE: Fill this section when all tasks are complete. -->
+
+### Statistics
+
+| Metric | Value |
+|--------|-------|
+| Total Tasks | {count} |
+| Completed | {count} |
+| Deviated | {count} |
+| Blocked | {count} |
+
+### Ready for Test
+
+<!-- AI-NOTE: Check all items before marking ready for test. -->
+
+- [ ] All tasks implemented
+- [ ] Local checks passed
+- [ ] No blocking issues
+- [ ] Deviations documented
+- [ ] Tech debt recorded (if any)
+
+### Handoff Notes
+
+<!-- AI-NOTE: Add any notes for the test agent or user. -->
+
+{handoff-notes}
+
+---
+
+*Task record generated by speccrew-dev-frontend skill*

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

@@ -0,0 +1,200 @@
+---
+name: speccrew-dev-mobile
+description: Mobile Development SOP. Guide System Developer Agent to implement mobile app code (Flutter/React Native) according to system design documents. Reads design blueprints, extracts task checklist, and executes implementation task by task with local quality checks.
+tools: Bash, Edit, Write, Glob, Grep, Read
+---
+
+# Trigger Scenarios
+
+- System design documents confirmed, user requests mobile development
+- User asks "Start mobile development", "Implement mobile app", "Write mobile code"
+- System Developer Agent dispatches this skill with platform context (platform_id, techs paths)
+
+# Workflow
+
+## Step 1: Read Design Documents
+
+Read in order:
+
+1. **INDEX.md**: `speccrew-workspace/iterations/{iteration}/03.system-design/{platform_id}/INDEX.md`
+2. **Module design documents**: `speccrew-workspace/iterations/{iteration}/03.system-design/{platform_id}/{module}-design.md`
+3. **API Contract**: `speccrew-workspace/iterations/{iteration}/02.feature-design/{feature-name}-api-contract.md`
+4. **Task record template**: `speccrew-dev-mobile/templates/TASK-RECORD-TEMPLATE.md`
+
+## Step 2: Read Techs Knowledge
+
+Read platform-specific development conventions:
+
+| Document | Path | Purpose |
+|----------|------|---------|
+| conventions-dev.md | `knowledges/techs/{platform_id}/conventions-dev.md` | Code style, naming, patterns |
+| architecture.md | `knowledges/techs/{platform_id}/architecture.md` | Layer structure, state management |
+| tech-stack.md | `knowledges/techs/{platform_id}/tech-stack.md` | Framework version, dependencies |
+
+### Platform-Specific Patterns
+
+**Flutter:**
+- Widget patterns (StatelessWidget vs StatefulWidget)
+- State management (Provider, Bloc, Riverpod)
+- Navigation (GoRouter, Navigator)
+- Platform channels for native integration
+
+**React Native:**
+- Component patterns (Functional components with Hooks)
+- State management (Redux, MobX, Zustand)
+- Navigation (React Navigation)
+- Native modules bridge
+
+## Step 3: Extract Task List
+
+Parse module design documents to extract all implementation tasks.
+
+### Mobile-Specific Task Types
+
+| Task Type | Description | Example |
+|-----------|-------------|---------|
+| Screen/Page | Full screen UI implementation | LoginScreen, ProductDetailPage |
+| Widget/Component | Reusable UI components | ProductCard, SearchBar |
+| Navigation flow | Route configuration | GoRouter config, Stack navigator |
+| State management | Store/provider setup | CartBloc, UserStore |
+| API service | HTTP client integration | ProductService, AuthApi |
+| Local storage | Persistence layer | Hive box, SQLite schema |
+| Platform channel | Native module integration | BiometricAuth, CameraAccess |
+| Asset management | Images, fonts, icons | pubspec.yaml, asset bundling |
+
+### Task ID Prefix
+
+Use `MB-001`, `MB-002`, etc. for mobile tasks.
+
+### Task Checklist Table
+
+```markdown
+| Task ID | Module | Description | Target Files | Platform Specific | Offline Support | Dependencies | Status |
+|---------|--------|-------------|--------------|-------------------|-----------------|--------------|--------|
+| MB-001 | Auth | LoginScreen implementation | lib/screens/auth/ | iOS/Android | Yes | - | ⏳ Pending |
+| MB-002 | Auth | BiometricAuth channel | lib/channels/ | iOS (Face ID) / Android (Biometric) | Yes | MB-001 | ⏳ Pending |
+```
+
+**Status Values**: ⏳ Pending | 🔄 In Progress | ✅ Complete | 🚫 Blocked
+
+**Checkpoint A: Present task extraction summary to user for confirmation.**
+
+## Step 4: Create Task Record File
+
+Before writing code, create task record file:
+
+**Path**: `speccrew-workspace/iterations/{iteration}/04.development/{platform_id}/{module}-task.md`
+
+Use `TASK-RECORD-TEMPLATE.md` for structure.
+
+## Step 5: Execute Task by Task
+
+Implement tasks sequentially, following dependencies.
+
+### Implementation Principles
+
+1. **Follow Design Blueprint**: Strictly follow file paths, naming, structure from design documents
+2. **Direct Code Writing**: Write actual code directly according to design (no template filling for source code)
+3. **Reuse Existing Code**: Use Glob/Grep to find existing widgets/stores before creating new ones
+4. **Platform Conventions**: Follow techs knowledge for naming, patterns, directory structure
+5. **Cross-Platform Consideration**: Handle iOS/Android differences where specified
+
+### Local Checks (After Each Task)
+
+Before marking task complete, run these checks:
+
+| Check | Flutter Command | React Native Command |
+|-------|-----------------|---------------------|
+| Static analysis | `flutter analyze` | `npx react-native lint` |
+| Build verification | `flutter build [ios/android]` | `npx react-native build-ios/build-android` |
+| Unit tests | `flutter test` | `npm test` |
+| Quick verify | App launches on simulator without crash | App launches on emulator without crash |
+
+**Check Failure Handling:**
+- Fix issues before marking task complete
+- Complex issues: record in task file "Known Issues" section
+- Design issues: stop and describe problem to user
+
+### Blocked Task Diagnosis
+
+When task is blocked (build failure, test failure, environment issues):
+
+1. **Check Logs**
+   - Flutter: `flutter logs` or IDE debug console
+   - React Native: Metro bundler output, `adb logcat` (Android), Xcode console (iOS)
+
+2. **Verify Dependencies**
+   - Flutter: `flutter pub get`, check `pubspec.yaml`
+   - React Native: `npm install`, check `package.json`
+
+3. **Platform-Specific Issues**
+   - iOS: Check Xcode build settings, CocoaPods
+   - Android: Check Gradle config, SDK versions
+
+4. **Record Diagnosis**
+   - In task file: Symptom → Investigation Steps → Root Cause → Solution
+
+## Step 6: Record Deviations
+
+If actual implementation differs from design, record in task file:
+
+```markdown
+### Deviation Notes
+- MB-003: Originally designed with Provider, switched to Riverpod due to [reason]
+- MB-005: Added iOS-specific permission handling not in original design
+```
+
+## Step 7: Record Technical Debt
+
+If technical debt identified during implementation:
+
+**Path**: `speccrew-workspace/iterations/{iteration}/tech-debt/{feature-name}-tech-debt.md`
+
+Common mobile technical debts:
+- Platform-specific workarounds
+- Temporary offline sync solutions
+- Missing error handling for edge cases
+- Deferred accessibility features
+- Incomplete test coverage
+
+## Step 8: Completion Notification
+
+After all tasks complete, update task record and notify user:
+
+```
+Mobile Development Complete:
+- Tasks implemented: [X]
+- Deviation records: [Y] (see task file)
+- Technical debt records: [Z] (see tech-debt file)
+- Task record: speccrew-workspace/iterations/{iteration}/04.development/{platform_id}/{module}-task.md
+
+Ready for QA Agent acceptance testing.
+```
+
+# Key Rules
+
+| Rule | Description |
+|------|-------------|
+| **Direct Implementation** | Write code directly according to design documents, NOT template filling |
+| **Platform-Specific Handling** | Properly handle iOS/Android differences, permissions, native integrations |
+| **Offline-First Consideration** | Consider offline patterns where applicable |
+| **API Contract READ-ONLY** | API Contract is reference only - do not modify |
+| **Status Markers Consistent** | Use same markers as design: [EXISTING], [MODIFIED], [NEW] |
+| **Follow Techs Conventions** | Naming, directory structure, patterns must follow techs knowledge |
+| **Tech Debt to Unified Path** | Write technical debt to `iterations/{iter}/tech-debt/` directory |
+
+# Checklist
+
+- [ ] Design documents loaded (INDEX.md + module designs)
+- [ ] Techs knowledge loaded (conventions-dev, architecture, tech-stack)
+- [ ] Task record file created
+- [ ] All design tasks extracted to checklist
+- [ ] Each task has local checks passed (analyze/build/test/quick verify)
+- [ ] Code follows architecture layer conventions
+- [ ] Naming follows conventions-dev.md
+- [ ] Platform-specific features properly handled
+- [ ] Navigation flow matches design
+- [ ] All deviations recorded
+- [ ] Technical debt written to `iterations/{iter}/tech-debt/`
+- [ ] Task record status updated to complete
+- [ ] Checkpoint A passed: task extraction confirmed with user

package/.speccrew/skills/speccrew-dev-mobile/templates/TASK-RECORD-TEMPLATE.md

@@ -0,0 +1,125 @@
+# Mobile Development Task Record - [Feature Name]
+
+> Based on design documents: [Link to 03.system-design/{platform_id}/{module}-design.md]
+> Platform: [flutter-app / react-native-app]
+> Iteration: [iteration ID]
+
+---
+
+## Task Checklist
+
+| Task ID | Module | Description | Target Files | Platform Specific | Offline Support | Dependencies | Status |
+|---------|--------|-------------|--------------|-------------------|-----------------|--------------|--------|
+| MB-001 | [module] | [task description] | `lib/screens/...` or `src/screens/...` | iOS/Android | Yes/No | - | ⏳ Pending |
+| MB-002 | [module] | [task description] | `lib/widgets/...` or `src/components/...` | No | Yes | MB-001 | ⏳ Pending |
+
+> **Status Values**: ⏳ Pending | 🔄 In Progress | ✅ Complete | 🚫 Blocked
+> **Platform Specific**: Mark if iOS/Android has different implementation (e.g., "iOS (Face ID) / Android (Biometric)")
+> **Offline Support**: Mark if feature works offline
+
+---
+
+## Implementation Progress
+
+### Completed Tasks
+
+#### MB-001: [Task Title]
+- **Status**: ✅ Complete
+- **Files Modified/Created**:
+  - `lib/screens/auth/login_screen.dart`
+- **Local Checks**:
+  - [x] Static analysis passed
+  - [x] Build verification passed
+  - [x] Unit tests passed
+  - [x] Quick verify: App launches on simulator
+- **Notes**: [Any implementation notes]
+
+---
+
+## Platform-Specific Notes
+
+### iOS Implementation
+- [Document iOS-specific implementation details]
+
+### Android Implementation
+- [Document Android-specific implementation details]
+
+### Permissions Required
+
+| Permission | iOS | Android | Purpose |
+|------------|-----|---------|---------|
+| Camera | NSCameraUsageDescription | CAMERA | Profile photo upload |
+| Location | NSLocationWhenInUseUsageDescription | ACCESS_FINE_LOCATION | Store locator |
+
+---
+
+## Offline Support Status
+
+| Feature | Works Offline | Sync Strategy |
+|---------|---------------|---------------|
+| Login | No | N/A |
+| Product Catalog | Yes | Cache on first load, refresh when online |
+| Cart | Yes | Local queue, sync on reconnect |
+
+---
+
+## Navigation Flow Verification
+
+| Screen Transition | Design Route | Implementation Status |
+|-------------------|--------------|----------------------|
+| Login → Home | `/login` → `/home` | ✅ Matches design |
+| Product List → Detail | `/products` → `/products/:id` | ✅ Matches design |
+
+---
+
+## Known Issues
+
+| Issue | Severity | Affected Platforms | Workaround | Status |
+|-------|----------|-------------------|------------|--------|
+| [Issue description] | 🔴 High / 🟡 Medium / 🟢 Low | iOS/Android/Both | [Workaround if any] | ⏳ Open |
+
+---
+
+## Deviation Notes
+
+| Task ID | Design | Implementation | Reason |
+|---------|--------|----------------|--------|
+| MB-003 | Provider state management | Riverpod | Better integration with existing codebase |
+
+> If no deviations, write: "No deviations from design documents."
+
+---
+
+## Technical Debt
+
+> Technical debt details written to: `iterations/{iteration}/tech-debt/{feature-name}-tech-debt.md`
+
+| Debt ID | Description | Priority | Status |
+|---------|-------------|----------|--------|
+| TD-001 | [Brief description] | 🔴 High | ⏳ Pending |
+
+---
+
+## Summary
+
+- **Total Tasks**: [X]
+- **Completed**: [Y]
+- **In Progress**: [Z]
+- **Blocked**: [W]
+- **Deviations**: [N] deviation(s) recorded
+- **Technical Debt**: [M] debt item(s) recorded
+
+---
+
+## Completion Sign-off
+
+- [ ] All tasks marked complete
+- [ ] Local checks passed for all tasks
+- [ ] Platform-specific implementations verified
+- [ ] Navigation flow matches design
+- [ ] Deviations documented
+- [ ] Technical debt documented
+- [ ] Ready for QA Agent testing
+
+**Completed Date**: [Date]
+**Developer**: Dev Agent

package/.speccrew/skills/speccrew-fd-api-contract/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: speccrew-fd-api-contract
+description: API Contract Generation SOP. Based on feature spec document, outputs structured frontend-backend API contract document. Once confirmed, the contract cannot be modified in downstream stages.
+tools: Read, Write, Glob, Grep
+---
+
+# Trigger Scenarios
+
+- Automatically triggered by speccrew-fd-feature-design Skill after feature spec document completion
+- User requests "Generate API documentation" or "Define API contract"
+
+# Workflow
+
+## Step 1: Read Input
+
+1. Feature spec document: `speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-feature-spec.md`
+2. API Contract template: `speccrew-fd-api-contract/templates/API-CONTRACT-TEMPLATE.md`
+3. System architecture (API specification part): Refer to project tech-stack-mappings.json for API naming conventions
+
+## Step 2: Organize API List
+
+Extract all APIs from feature spec document and organize into a list:
+
+| API Name | Method | URL | Description | Caller |
+|----------|--------|-----|-------------|--------|
+| [API] | GET/POST/PUT/DELETE | `/api/v1/...` | [Description] | Frontend |
+
+Naming conventions:
+- URL uses RESTful style, plural nouns
+- Follow API specifications in project tech-stack-mappings.json
+
+## Step 3: Define Contract for Each API
+
+Complete definition for each API:
+- Request method, URL, authentication required or not
+- Request parameters (including type, required or not, example values)
+- Response structure (including type and description for each field)
+- Success response example (JSON)
+- Error code list
+
+## Step 4: Write to File
+
+Write path: `speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-api-contract.md`
+
+## Step 5: Joint Confirmation
+
+After both documents (Feature Spec + API Contract) are ready, request confirmation from user:
+
+```
+Feature design phase deliverables are ready:
+- Feature Spec: speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-feature-spec.md
+- API Contract: speccrew-workspace/iterations/{number}-{type}-{name}/02.feature-design/[feature-name]-api-contract.md
+
+Please confirm the following key points:
+1. Is the overall technical solution feasible?
+2. Does the API definition meet frontend requirements?
+3. Is the data model reasonable?
+
+⚠️ After confirmation, the API contract will be the sole baseline for frontend-backend collaboration.
+   Read-only reference in design/development phase, no modifications allowed.
+   If changes are needed, must return to this phase for re-confirmation.
+
+After confirmation, you can start frontend and backend Designer Agents separately.
+```
+
+# Checklist
+
+- [ ] All APIs mentioned in feature spec have defined contracts
+- [ ] Each API has complete request/response structure definition
+- [ ] URL naming conforms to backend architecture specifications
+- [ ] Error code list is complete
+- [ ] File has been written to correct path
+- [ ] Summary of both documents has been shown to user and confirmation requested

package/.speccrew/skills/speccrew-fd-api-contract/templates/API-CONTRACT-TEMPLATE.md

@@ -0,0 +1,96 @@
+# API Contract - [Feature Name]
+
+> Based on Solution: [Link to corresponding Solution file]
+>
+> **Important**: This document is output by Feature Designer Agent and is the sole baseline for frontend-backend collaboration.
+> *Read-only reference in design/development phase, no modifications allowed.* If changes are needed, must trace back to Feature Designer Agent for correction and re-confirmation.
+
+---
+
+## Change Log
+
+| Version | Date | Changes | Changed By |
+|---------|------|---------|------------|
+| v1.0 | [Date] | Initial version | Feature Designer Agent |
+
+---
+
+## API List
+
+| API Name | Method | URL | Description |
+|----------|--------|-----|-------------|
+| [API 1] | POST | `/api/v1/xxx` | [Description] |
+| [API 2] | GET | `/api/v1/xxx/:id` | [Description] |
+
+---
+
+## API Details
+
+### [API Name]
+
+**Basic Information**
+
+| Item | Content |
+|------|---------|
+| Method | `POST` |
+| URL | `/api/v1/xxx` |
+| Description | [API Description] |
+| Authentication | Required / Not Required |
+
+**Request Headers**
+
+| Field | Value | Description |
+|-------|-------|-------------|
+| `Content-Type` | `application/json` | |
+| `Authorization` | `Bearer {token}` | When authentication is required |
+
+**Request Parameters**
+
+| Field | Type | Required | Description | Example |
+|-------|------|----------|-------------|---------|
+| [Field] | string | Yes/No | [Description] | `"example"` |
+| [Field] | int | Yes/No | [Description] | `1` |
+
+**Request Example**
+
+```json
+{
+  "[field]": "[value]"
+}
+```
+
+**Response Structure**
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `code` | int | 0=Success, non-zero=Failure |
+| `message` | string | Result description |
+| `data` | object | Response data |
+| `data.[field]` | [Type] | [Description] |
+
+**Response Example (Success)**
+
+```json
+{
+  "code": 0,
+  "message": "success",
+  "data": {
+    "[field]": "[value]"
+  }
+}
+```
+
+**Error Codes**
+
+| Error Code | HTTP Status | Description | Handling Suggestion |
+|------------|-------------|-------------|---------------------|
+| 4001 | 400 | Parameter validation failed | Check request parameters |
+| 4003 | 403 | No permission | Check user permissions |
+| 4004 | 404 | Resource not found | Confirm resource ID |
+| 5000 | 500 | Internal server error | Contact backend for troubleshooting |
+
+---
+
+**Contract Status:** 📝 Draft / 👀 In Review / ✅ Confirmed  
+**Confirmation Date:** [Date]  
+**Confirmed By:** [Name]