ai-playbook 1.0.0

package/prompts/developer/implement-feature.md

@@ -0,0 +1,133 @@
+# Implement Feature Prompt
+
+**Role:** Developer  
+**Type:** Feature Implementation  
+**Context Needed:** Feature spec, architecture decisions, project patterns
+
+## Template
+
+```
+Implement [feature name] with the following requirements:
+
+## Feature Spec
+[Copy relevant requirements from spec]
+
+## Constraints
+- Must follow existing [architecture/patterns]
+- Must support [specific requirements]
+- Cannot use [restricted libraries/patterns]
+- Performance target: [specific metric]
+
+## Files to Modify
+- [file1] - What changes
+- [file2] - What changes
+- [file3] - What changes
+
+## New Files Needed
+- [path/file1] - Purpose
+- [path/file2] - Purpose
+
+## Expected Output
+- Production-ready code
+- Error handling
+- Logging
+- Tests with coverage >= 80%
+- Documentation via code
+
+## Verification
+Run these checks before considering complete:
+1. All tests pass: `npm test`
+2. Lint passes: `npm run lint`
+3. Type checks pass: `npm run type-check`
+4. Build succeeds: `npm run build`
+5. Feature works in dev server: `npm run dev`
+```
+
+## When to Use
+
+- Implementing new features
+- Adding functionality to existing modules
+- Extending APIs or services
+- Creating utilities or helpers
+
+## Required Context
+
+- Feature specification
+- Existing code patterns
+- Architecture decisions
+- Related modules/dependencies
+- Error handling patterns
+
+## Expected Output
+
+- ✓ Production-ready code
+- ✓ All tests pass
+- ✓ Lint passes
+- ✓ Type checks pass
+- ✓ Error handling
+- ✓ Logging included
+- ✓ Code documented via naming
+
+## Quality Gates
+
+```
+Code Quality:
+  ✓ No linting errors
+  ✓ Type-safe
+  ✓ Follows patterns
+
+Test Coverage:
+  ✓ >= 80% coverage
+  ✓ Happy path tested
+  ✓ Error cases tested
+  ✓ Edge cases tested
+
+Performance:
+  ✓ No N+1 queries
+  ✓ Efficient algorithms
+  ✓ Caching where appropriate
+
+Documentation:
+  ✓ Clear function names
+  ✓ Comment complex logic
+  ✓ README updated if needed
+```
+
+## Example Usage
+
+```
+Implement user authentication with the following requirements:
+
+## Feature Spec
+- Support JWT tokens
+- Validate email/password
+- Create session on login
+- Refresh token on expiry
+- Logout clears session
+
+## Constraints
+- Must use bcrypt for passwords
+- Must follow existing middleware patterns
+- Must support OAuth2 integration
+- Cannot use deprecated auth libraries
+
+## Files to Modify
+- src/routes/auth.ts - Add login/logout endpoints
+- src/middleware/auth.ts - Add JWT validation
+- src/types/user.ts - Add auth types
+- src/models/user.ts - Add password methods
+
+## New Files Needed
+- src/services/auth.ts - Auth business logic
+- tests/auth.test.ts - Auth tests
+- docs/auth.md - Authentication guide
+```
+
+## Tips
+
+- Be specific about constraints
+- Include architecture context
+- List all files to modify
+- Provide expected behavior
+- Define quality gates
+- Give code examples if helpful

package/prompts/product-owner/README.md

@@ -0,0 +1,116 @@
+# Product Owner Prompts
+
+Reusable prompts for product management and feature definition.
+
+## Available Prompts
+
+### [define-feature.md](define-feature.md)
+
+**Use when:** Creating new features or defining requirements
+
+**Covers:**
+- Problem statement
+- User stories
+- Acceptance criteria
+- Business goals
+- Success metrics
+- Constraints
+
+**Good for:**
+- Feature specification
+- Product requirements
+- Prioritization
+- Release planning
+
+## Using Product Owner Prompts
+
+### Definition Process
+
+1. **Understand problem** - What needs are we solving?
+2. **Define users** - Who are they?
+3. **Write stories** - User-centric requirements
+4. **Acceptance criteria** - How to know it's done?
+5. **Goals** - Business outcomes
+6. **Metrics** - How to measure success?
+7. **Constraints** - Limitations
+8. **Scope** - What's included/excluded?
+
+## What Gets Delivered
+
+✓ Problem statement  
+✓ User stories  
+✓ Acceptance criteria  
+✓ Business goals  
+✓ Success metrics  
+✓ Constraints documented  
+✓ Out of scope clear  
+
+## Quality Gates
+
+Features must define:
+
+✓ **Clarity** - Problem understood  
+✓ **Completeness** - All requirements covered  
+✓ **Feasibility** - Realistic scope and timeline  
+✓ **Measurability** - Clear success metrics  
+✓ **Alignment** - Supports business goals  
+
+## Feature Definition Checklist
+
+- [ ] Problem clearly stated
+- [ ] User stories written
+- [ ] Acceptance criteria detailed
+- [ ] Business goals defined
+- [ ] Success metrics set
+- [ ] Constraints documented
+- [ ] Out of scope clear
+- [ ] Timeline realistic
+- [ ] Budget understood
+- [ ] Prioritization clear
+
+## User Story Format
+
+```
+As a [user type]
+I want [capability]
+So that [benefit]
+
+Acceptance Criteria:
+- [ ] Criterion 1
+- [ ] Criterion 2
+- [ ] Criterion 3
+```
+
+## Success Metrics Types
+
+- **Adoption** - % of users using feature
+- **Engagement** - How often used
+- **Business** - Revenue, retention
+- **Experience** - NPS, satisfaction
+- **Technical** - Performance, reliability
+
+## Best Practices
+
+### Effective Feature Definition
+
+- Start with user problems
+- Be specific about requirements
+- Define measurable outcomes
+- Get stakeholder alignment
+- Validate with users
+- Consider edge cases
+- Plan phases
+- Think about operations
+
+### Prioritization Framework
+
+- **Importance** - User need level
+- **Urgency** - How soon needed
+- **Effort** - Implementation cost
+- **Impact** - Business value
+
+## Related Documentation
+
+- See `../README.md` for overview
+- Check patterns/ for design patterns
+- Review knowledge/ for domain knowledge

package/prompts/product-owner/define-feature.md

@@ -0,0 +1,145 @@
+# Define Feature Prompt
+
+**Role:** Product Owner  
+**Type:** Feature Definition  
+**Context Needed:** Problem statement, user research, business goals, constraints
+
+## Template
+
+```
+Define feature: [Feature Name]
+
+## Problem Statement
+[What problem does this solve]
+
+## User Stories
+As a [user type]
+I want [capability]
+So that [benefit]
+
+Acceptance Criteria:
+- [ ] [Criterion 1]
+- [ ] [Criterion 2]
+- [ ] [Criterion 3]
+
+## Business Goals
+- [Goal 1]
+- [Goal 2]
+- [Goal 3]
+
+## Success Metrics
+- [Metric 1: Target]
+- [Metric 2: Target]
+- [Metric 3: Target]
+
+## Constraints
+- Timeline: [When needed]
+- Budget: [Resource limits]
+- Technical: [Tech constraints]
+- Legal: [Compliance requirements]
+
+## Out of Scope
+- [What's not included]
+- [What can be Phase 2]
+
+## Open Questions
+1. [Question 1]
+2. [Question 2]
+
+## Expected Deliverables
+- Detailed feature specification
+- User stories and acceptance criteria
+- Success metrics
+- Prioritization
+- Wireframes/mockups (if applicable)
+```
+
+## When to Use
+
+- Creating new features
+- Defining product requirements
+- Prioritizing work
+- Planning releases
+- Communicating with stakeholders
+
+## Required Context
+
+- Problem to solve
+- Target users
+- Business goals
+- Constraints
+- Competitive context
+- User research
+
+## Expected Output
+
+- ✓ Clear problem statement
+- ✓ User stories written
+- ✓ Acceptance criteria defined
+- ✓ Success metrics set
+- ✓ Constraints documented
+- ✓ Prioritized
+
+## Quality Gates
+
+```
+Clarity:
+  ✓ Problem understood
+  ✓ Solution clear
+  ✓ No ambiguity
+
+Completeness:
+  ✓ All user stories covered
+  ✓ Acceptance criteria detailed
+  ✓ Constraints listed
+
+Feasibility:
+  ✓ Timeline realistic
+  ✓ Budget reasonable
+  ✓ Tech feasible
+```
+
+## Example Usage
+
+```
+Define Feature: Dark Mode Support
+
+## Problem Statement
+Users request dark mode for eye strain reduction at night
+
+## User Stories
+As a user who works at night
+I want dark mode
+So that I can reduce eye strain
+
+Acceptance Criteria:
+- [ ] All pages have dark mode
+- [ ] Toggle to switch modes
+- [ ] Preference persists
+- [ ] High contrast maintained
+
+## Business Goals
+- Increase user satisfaction
+- Reduce support requests
+- Competitive feature parity
+
+## Success Metrics
+- 40% of users enable dark mode
+- Support requests decrease 5%
+- Feature rating >= 4.5 stars
+
+## Constraints
+- Timeline: 2 weeks
+- No new dependencies
+- Must support all browsers
+```
+
+## Tips
+
+- Start with user needs
+- Be specific with acceptance criteria
+- Define success metrics
+- Consider edge cases
+- Involve users/research
+- Think about phases
+- Plan follow-ups

package/prompts/reviewer/README.md

@@ -0,0 +1,91 @@
+# Reviewer Prompts
+
+Reusable prompts for code review and quality assessment.
+
+## Available Prompts
+
+### [code-review.md](code-review.md)
+
+**Use when:** Reviewing pull requests or code changes
+
+**Covers:**
+- PR context and scope
+- What to check (correctness, security, performance, style, testing)
+- Project standards
+- Acceptance criteria
+- Expected issues and feedback
+
+**Good for:**
+- PR reviews before merge
+- Code quality assessment
+- Issue identification
+- Knowledge sharing
+
+## Using Review Prompts
+
+### Review Process
+
+1. **Understand context** - PR purpose and scope
+2. **Check correctness** - Does it work? Are there bugs?
+3. **Assess security** - Vulnerabilities? Input validation?
+4. **Evaluate performance** - Regressions? Inefficiencies?
+5. **Review style** - Standards? Patterns?
+6. **Verify testing** - Coverage? Meaningful tests?
+7. **Summary** - Approve or request changes
+
+## What Gets Reviewed
+
+✓ **Correctness** - Logic is sound, no bugs  
+✓ **Security** - No vulnerabilities  
+✓ **Performance** - No regressions  
+✓ **Testing** - Adequate coverage  
+✓ **Style** - Follows conventions  
+✓ **Maintainability** - Easy to understand  
+
+## Quality Gates
+
+Reviews should verify:
+
+✓ **Correctness** - All tests pass, logic is sound  
+✓ **Security** - No vulnerabilities introduced  
+✓ **Testing** - >= 80% coverage  
+✓ **Standards** - Follows project conventions  
+✓ **Documentation** - Code is self-documenting  
+
+## Review Checklist
+
+- [ ] Understand the purpose
+- [ ] Code compiles/runs
+- [ ] Tests pass
+- [ ] No obvious bugs
+- [ ] Security reviewed
+- [ ] Performance checked
+- [ ] Style consistent
+- [ ] Documentation clear
+- [ ] Ready to merge
+
+## Best Practices
+
+### Effective Code Reviews
+
+- Be constructive, not critical
+- Focus on important issues first
+- Separate style from substance
+- Suggest improvements
+- Ask clarifying questions
+- Acknowledge good work
+- Provide context
+- Be respectful
+
+### Review Priorities
+
+1. **Critical** - Security, correctness
+2. **High** - Performance, maintainability
+3. **Medium** - Style, consistency
+4. **Low** - Optimization, minor improvements
+
+## Related Documentation
+
+- See `../README.md` for overview
+- Check hooks/ for pre-commit checks
+- Review commands/ for test/validate commands

package/prompts/reviewer/code-review.md

@@ -0,0 +1,129 @@
+# Code Review Prompt
+
+**Role:** Reviewer  
+**Type:** Code Review  
+**Context Needed:** PR/diff, project standards, acceptance criteria, related PRs
+
+## Template
+
+```
+Review this code change for [PR title]:
+
+## Context
+- PR: [Link or description]
+- Files changed: [List]
+- Lines added/removed: [Stats]
+- Related to: [Related issues/PRs]
+
+## What to Check
+- ✓ Correctness - Does it work as intended?
+- ✓ Security - No vulnerabilities?
+- ✓ Performance - No regressions?
+- ✓ Maintainability - Easy to understand?
+- ✓ Testing - Adequate coverage?
+- ✓ Style - Follows conventions?
+
+## Project Standards
+[Reference to coding standards, patterns]
+
+## Acceptance Criteria
+1. [Criterion 1]
+2. [Criterion 2]
+3. [Criterion 3]
+
+## Expected Output
+- Issues found (severity: critical/high/medium/low)
+- Questions for author
+- Suggestions for improvement
+- Approval recommendation
+```
+
+## When to Use
+
+- Reviewing PRs before merge
+- Assessing code quality
+- Catching issues early
+- Knowledge sharing
+- Maintaining standards
+
+## Required Context
+
+- Full diff/PR
+- Acceptance criteria
+- Project coding standards
+- Related architecture
+- Security requirements
+
+## Expected Output
+
+- ✓ Bug identification
+- ✓ Security review
+- ✓ Performance check
+- ✓ Style/pattern review
+- ✓ Clear feedback
+- ✓ Approval/concerns
+
+## Quality Gates
+
+```
+Correctness:
+  ✓ Logic is sound
+  ✓ Edge cases handled
+  ✓ No obvious bugs
+
+Security:
+  ✓ No vulnerabilities
+  ✓ Input validated
+  ✓ Auth/perms correct
+
+Testing:
+  ✓ Adequate coverage
+  ✓ Tests meaningful
+  ✓ No test deletions
+
+Standards:
+  ✓ Follows patterns
+  ✓ Code readable
+  ✓ No tech debt
+```
+
+## Example Usage
+
+```
+Review PR: Add payment retry logic (#1234)
+
+## Context
+Files: src/services/payment.ts, tests/payment.test.ts
+Changes: +150 -30 lines
+Related: Issue #1200 (payment failures)
+
+## What to Check
+- Does retry logic work for timeouts?
+- Are there exponential backoffs?
+- Does it handle rate limits?
+- Test coverage adequate?
+- Any security issues?
+
+## Project Standards
+- Error handling pattern: Custom errors
+- Testing: Jest with 80% coverage
+- Async: Promises/async-await
+- Logging: Winston logger
+
+## Acceptance Criteria
+1. Retries up to 3 times
+2. Exponential backoff (1s, 2s, 4s)
+3. Respects rate limit headers
+4. Logs all attempts
+5. >= 85% test coverage
+```
+
+## Tips
+
+- Be specific with feedback
+- Separate issues by severity
+- Suggest fixes not just problems
+- Praise good work
+- Consider context
+- Avoid bikeshedding
+- Focus on important issues