opencode-agile-agent 1.0.1

package/templates/.opencode/rules/git-conventions.md

@@ -0,0 +1,149 @@
+# Git Conventions
+
+Standardized git workflow and commit conventions.
+
+## Branch Strategy
+
+### Branch Types
+
+| Type | Pattern | Purpose |
+|------|---------|---------|
+| Feature | `feature/description` | New features |
+| Fix | `fix/description` | Bug fixes |
+| Refactor | `refactor/description` | Code improvements |
+| Docs | `docs/description` | Documentation |
+| Release | `release/v1.0.0` | Release preparation |
+| Hotfix | `hotfix/description` | Production fixes |
+
+### Branch Workflow
+
+```
+main ─────●─────●─────●─────●─────→
+          \           /
+feature/a  ●───●───●  merge
+               
+          \       /
+feature/b  ●───●───●  merge
+```
+
+## Commit Messages
+
+### Format
+
+```
+<type>(<scope>): <description>
+
+[optional body]
+
+[optional footer]
+```
+
+### Types
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation only |
+| `style` | Formatting, no code change |
+| `refactor` | Code refactoring |
+| `test` | Adding/updating tests |
+| `chore` | Maintenance tasks |
+| `perf` | Performance improvement |
+
+### Examples
+
+```bash
+# Feature
+feat(auth): add JWT refresh token support
+
+# Fix
+fix(api): handle null response from user service
+
+# Breaking change
+feat(api)!: change user endpoint response format
+
+BREAKING CHANGE: The /api/user endpoint now returns
+a different structure. See migration guide.
+```
+
+## Pull Request Process
+
+### PR Title
+
+Use the same format as commit messages:
+
+```
+feat(auth): add JWT refresh token support
+```
+
+### PR Description
+
+```markdown
+## What
+Brief description of changes.
+
+## Why
+Why this change is needed.
+
+## How
+Technical approach taken.
+
+## Testing
+- [ ] Unit tests added
+- [ ] Integration tests added
+- [ ] Manual testing done
+
+## Screenshots
+[If applicable]
+
+## Checklist
+- [ ] Code follows conventions
+- [ ] Tests pass
+- [ ] Documentation updated
+- [ ] No breaking changes (or documented)
+```
+
+### Review Process
+
+1. Create PR with description
+2. Assign reviewers
+3. Address review comments
+4. Get approval
+5. Squash and merge
+
+## Merge Strategies
+
+### Squash and Merge (Default)
+
+- Combines all commits into one
+- Clean history on main
+- PR description preserved
+
+### Rebase and Merge
+
+- Preserves individual commits
+- Linear history
+- Use for feature branches with clean commits
+
+### Merge Commit
+
+- Preserves branch history
+- Use for release branches
+- Creates merge commit
+
+## Git Aliases
+
+```bash
+# Useful aliases
+git config --global alias.co checkout
+git config --global alias.br branch
+git config --global alias.ci commit
+git config --global alias.st status
+git config --global alias.lg "log --oneline --graph"
+git config --global alias.unstage "reset HEAD --"
+```
+
+---
+
+**Consistent git practices enable smooth collaboration.**

package/templates/.opencode/skills/api-patterns/SKILL.md

@@ -0,0 +1,162 @@
+---
+name: api-patterns
+description: REST and GraphQL API design patterns and best practices.
+version: 1.0.0
+---
+
+# API Patterns
+
+Best practices for designing REST and GraphQL APIs.
+
+## REST API Design
+
+### Resource Naming
+
+```
+✅ GOOD:
+GET    /users                 # List users
+GET    /users/{id}            # Get user
+POST   /users                 # Create user
+PUT    /users/{id}            # Replace user
+PATCH  /users/{id}            # Update user
+DELETE /users/{id}            # Delete user
+GET    /users/{id}/orders     # Get user's orders
+
+❌ BAD:
+GET    /getUsers
+POST   /createUser
+GET    /user-orders/{userId}
+```
+
+### HTTP Status Codes
+
+| Code | Use When |
+|------|----------|
+| 200 | Successful GET, PUT, PATCH |
+| 201 | Resource created (POST) |
+| 204 | Success with no content (DELETE) |
+| 400 | Invalid request |
+| 401 | Not authenticated |
+| 403 | Not authorized |
+| 404 | Resource not found |
+| 409 | Conflict (duplicate) |
+| 422 | Validation error |
+| 429 | Rate limited |
+| 500 | Server error |
+
+### Response Envelope
+
+```json
+// Success
+{
+  "success": true,
+  "data": { ... },
+  "meta": {
+    "timestamp": "2024-01-15T10:30:00Z",
+    "requestId": "abc-123"
+  }
+}
+
+// Error
+{
+  "success": false,
+  "error": {
+    "code": "VALIDATION_ERROR",
+    "message": "Invalid input",
+    "details": [...]
+  }
+}
+```
+
+### Pagination
+
+```json
+// Cursor-based (preferred)
+{
+  "data": [...],
+  "pagination": {
+    "nextCursor": "eyJpZCI6MTAwfQ==",
+    "hasMore": true
+  }
+}
+
+// Offset-based
+{
+  "data": [...],
+  "pagination": {
+    "page": 1,
+    "pageSize": 20,
+    "totalCount": 100
+  }
+}
+```
+
+## GraphQL Design
+
+### Schema Structure
+
+```graphql
+type Query {
+  user(id: ID!): User
+  users(filter: UserFilter, pagination: PaginationInput): UserConnection!
+}
+
+type Mutation {
+  createUser(input: CreateUserInput!): User!
+  updateUser(id: ID!, input: UpdateUserInput!): User!
+}
+
+type User {
+  id: ID!
+  name: String!
+  email: String!
+  orders: [Order!]!
+}
+```
+
+### Best Practices
+
+- Use meaningful names (camelCase for fields)
+- Provide descriptions
+- Use enums for fixed values
+- Implement pagination for lists
+- Use input types for mutations
+
+## Authentication Patterns
+
+### JWT Pattern
+
+```typescript
+// Access token: short-lived (15 min)
+const accessToken = jwt.sign(payload, secret, { expiresIn: '15m' });
+
+// Refresh token: long-lived (7 days)
+const refreshToken = crypto.randomBytes(64).toString('hex');
+
+// Store: httpOnly cookie for refresh, memory for access
+```
+
+### API Key Pattern
+
+```typescript
+// Header-based
+Authorization: Bearer sk_live_xxx
+
+// Query param (less secure)
+?api_key=sk_live_xxx
+```
+
+## Rate Limiting
+
+```typescript
+// Per-user limiting
+const limiter = rateLimit({
+  windowMs: 15 * 60 * 1000, // 15 minutes
+  max: 100, // 100 requests per window
+  keyGenerator: (req) => req.user.id
+});
+```
+
+---
+
+**Consistent APIs enable great developer experience.**

package/templates/.opencode/skills/brainstorming/SKILL.md

@@ -0,0 +1,255 @@
+---
+name: brainstorming
+description: Socratic questioning and discovery techniques for exploring ideas and requirements.
+version: 1.0.0
+---
+
+# Brainstorming
+
+Socratic questioning and discovery techniques for exploring ideas and clarifying requirements.
+
+## The Socratic Method
+
+Ask questions to guide discovery rather than providing answers.
+
+### Core Questions
+
+1. **What is the problem?**
+   - What are you trying to solve?
+   - Who has this problem?
+   - Why does it matter?
+
+2. **What are the constraints?**
+   - What's the timeline?
+   - What's the budget?
+   - What technical limitations exist?
+
+3. **What does success look like?**
+   - How will you measure success?
+   - What's the definition of done?
+   - What would failure look like?
+
+## Question Frameworks
+
+### 5 Whys
+
+Dig deeper into root causes:
+
+```
+Problem: Users aren't completing checkout
+
+Why? → Form is too long
+Why? → We're asking for too much information
+Why? → We want complete user profiles
+Why? → Marketing wants demographic data
+Why? → To improve targeting
+
+Root cause: Marketing needs vs. UX needs conflict
+```
+
+### SCAMPER
+
+Explore alternatives:
+
+| Question | Prompt |
+|----------|--------|
+| **S**ubstitute | What can be replaced? |
+| **C**ombine | What can be merged? |
+| **A**dapt | What can be adjusted? |
+| **M**odify | What can be changed? |
+| **P**ut to other use | What else can it do? |
+| **E**liminate | What can be removed? |
+| **R**everse | What can be inverted? |
+
+### Six Thinking Hats
+
+Explore from different perspectives:
+
+| Hat | Focus |
+|-----|-------|
+| **White** | Facts and data |
+| **Red** | Emotions and feelings |
+| **Black** | Risks and problems |
+| **Yellow** | Benefits and value |
+| **Green** | Creativity and alternatives |
+| **Blue** | Process and control |
+
+## Discovery Process
+
+### Phase 1: Understand the Request
+
+```markdown
+Initial request: "Build a dashboard"
+
+Questions to ask:
+- Who will use this dashboard?
+- What decisions will they make from it?
+- What data do they need?
+- How often will they use it?
+- What devices will they use?
+```
+
+### Phase 2: Explore Options
+
+```markdown
+Options for dashboard:
+1. Real-time monitoring dashboard
+2. Analytics dashboard with charts
+3. Task management dashboard
+4. Executive summary dashboard
+
+Trade-offs:
+- Real-time vs. historical data
+- Simple vs. detailed
+- Mobile vs. desktop priority
+```
+
+### Phase 3: Define Scope
+
+```markdown
+In Scope:
+- [Feature 1]
+- [Feature 2]
+
+Out of Scope:
+- [Feature X]
+- [Feature Y]
+
+MVP:
+- [Minimum viable feature set]
+```
+
+### Phase 4: Validate Understanding
+
+```markdown
+"So what I'm hearing is:
+- You need [X]
+- For [audience]
+- To solve [problem]
+- With [constraints]
+
+Is that correct?"
+```
+
+## Question Templates
+
+### For New Features
+
+```markdown
+1. What problem does this solve?
+2. Who is the target user?
+3. How are they solving this today?
+4. What would make this feature a success?
+5. What are the must-haves vs. nice-to-haves?
+6. What's the timeline?
+7. Are there any technical constraints?
+8. Are there any design preferences?
+```
+
+### For Bug Fixes
+
+```markdown
+1. What's the expected behavior?
+2. What's the actual behavior?
+3. When did this start happening?
+4. Can you reproduce it reliably?
+5. What steps reproduce it?
+6. What have you tried to fix it?
+7. Who is affected by this?
+8. How urgent is this?
+```
+
+### For Performance Issues
+
+```markdown
+1. What's slow?
+2. How slow is it? (measure)
+3. When is it slow?
+4. Has it always been slow?
+5. What changed recently?
+6. What's the target performance?
+7. What metrics matter most?
+```
+
+### For Architecture Decisions
+
+```markdown
+1. What are we trying to achieve?
+2. What are the constraints?
+3. What are the options?
+4. What are the trade-offs of each?
+5. What's the impact of each option?
+6. How reversible is this decision?
+7. What's the cost of waiting?
+```
+
+## Facilitation Techniques
+
+### Dot Voting
+
+```markdown
+Options:
+- Option A •••• (4 votes)
+- Option B •• (2 votes)
+- Option C ••• (3 votes)
+
+→ Proceed with Option A
+```
+
+### Impact/Effort Matrix
+
+```
+         High Impact
+              │
+   Quick Wins │ Major Projects
+──────────────┼──────────────
+  Fill-ins    │ Money Pits
+              │
+         Low Impact
+    Low Effort      High Effort
+```
+
+### Affinity Mapping
+
+```markdown
+Group related ideas:
+
+[Performance]     [Security]      [UX]
+- Load time      - Auth          - Navigation
+- Caching        - Encryption    - Responsive
+- CDN            - Validation    - Accessibility
+```
+
+## Anti-Patterns to Avoid
+
+### Leading Questions
+
+```
+❌ "Don't you think we should use React?"
+✅ "What frontend framework are you considering?"
+```
+
+### Yes/No Questions
+
+```
+❌ "Do you need authentication?"
+✅ "Tell me about your authentication requirements."
+```
+
+### Assumptions
+
+```
+❌ "I assume you want dark mode."
+✅ "Do you have preferences for the visual theme?"
+```
+
+### Solutionizing
+
+```
+❌ "We should build it with microservices."
+✅ "What are your scalability requirements?"
+```
+
+---
+
+**Good questions lead to better solutions.**