claude-autopm 2.8.1 → 2.8.3

package/packages/plugin-core/rules/context7-enforcement.md

@@ -0,0 +1,327 @@
+# Context7 Documentation Enforcement
+
+> **CRITICAL**: This rule has HIGHEST PRIORITY. ALL commands and agents MUST query Context7 before execution.
+
+---
+
+## 🔴 VISUAL REMINDER FOR EVERY COMMAND/AGENT
+
+**WHEN YOU SEE:** User writes `/pm:epic-decompose` or `@aws-cloud-architect`
+
+**YOU MUST IMMEDIATELY:**
+
+1. 📖 **ANNOUNCE**: "I will now query Context7 for required documentation..."
+2. 🔍 **READ** the command/agent file to extract Documentation Queries
+3. 🌐 **QUERY** Context7 MCP for EACH listed topic using mcp__context7__get-library-docs
+4. 📝 **SUMMARIZE** key findings from Context7 results
+5. ✅ **CONFIRM**: "Context7 verification complete. Proceeding with [command/agent]..."
+
+**VISUAL OUTPUT FOR USER:**
+
+```
+🔒 Context7 Enforcement Active
+
+📋 Command: /pm:epic-decompose
+📚 Querying Context7 for required documentation...
+
+   ➜ mcp://context7/agile/epic-decomposition
+   ➜ mcp://context7/agile/task-sizing
+   ➜ mcp://context7/agile/user-stories
+   ➜ mcp://context7/project-management/task-breakdown
+
+✅ Context7 queries complete
+📖 Key findings: [summarize what you learned]
+
+Proceeding with epic decomposition using Context7 best practices...
+```
+
+---
+
+## Core Context7 Philosophy
+
+**Prime Directive**: Query live documentation from Context7 MCP BEFORE implementing any solution.
+**Zero Tolerance**: No implementation without Context7 query. No reliance on training data. No shortcuts.
+
+## Why This is Critical
+
+### Problems We Solve
+
+- **Hallucinations**: AI training data becomes stale, leading to outdated patterns
+- **API Changes**: Frameworks evolve - training data doesn't reflect latest versions
+- **Best Practices Drift**: Industry standards change faster than model retraining
+- **Version Conflicts**: Code suggestions may target wrong framework versions
+
+### Context7 Benefits
+
+- **Always Current**: Live documentation reflects latest releases
+- **Verified Patterns**: Real code examples from official sources
+- **API Accuracy**: Current function signatures, parameters, return types
+- **Breaking Changes**: Immediate awareness of deprecated patterns
+
+## The Context7 Cycle
+
+### 1. QUERY Phase (Before Implementation)
+
+**MANDATORY Steps:**
+1. Read command/agent file to extract `**Documentation Queries:**` section
+2. Query EACH Context7 MCP link listed
+3. Analyze results for relevant patterns, APIs, and best practices
+4. Summarize key findings before proceeding
+
+**Required Information:**
+- Current API signatures and parameters
+- Recommended patterns and anti-patterns
+- Breaking changes from recent versions
+- Official code examples
+
+### 2. IMPLEMENT Phase (Using Context7 Knowledge)
+
+**Requirements:**
+- Apply patterns EXACTLY as documented in Context7 results
+- Use API signatures from Context7 (not from training data)
+- Follow architectural recommendations from live docs
+- Reference Context7 findings in code comments where applicable
+
+**Verification:**
+- Cross-check implementation against Context7 examples
+- Validate parameters match current API documentation
+- Ensure no deprecated patterns are used
+
+### 3. VALIDATE Phase (Post-Implementation)
+
+**Mandatory Checks:**
+- Implementation matches Context7 best practices
+- No training data hallucinations introduced
+- Code follows latest framework conventions
+- All deprecation warnings addressed
+
+## Enforcement Rules
+
+### ABSOLUTE REQUIREMENTS
+
+**For ALL Commands:**
+- MUST read `## Required Documentation Access` section
+- MUST query EVERY `mcp://context7/...` link before execution
+- MUST summarize Context7 findings before proceeding
+- MUST apply Context7 guidance in implementation
+
+**For ALL Agents:**
+- MUST read `**Documentation Queries:**` section
+- MUST query Context7 before making technical decisions
+- MUST verify API signatures against live documentation
+- MUST flag conflicts between training data and Context7
+
+**For ALL Implementations:**
+- NO code based solely on training data for technical specifics
+- NO assumptions about API signatures without Context7 verification
+- NO "I think this is how it works" - VERIFY with Context7
+- NO skipping Context7 "because it's a small change"
+
+### PROHIBITED PRACTICES
+
+- ❌ Implementing without querying Context7 first
+- ❌ "I remember how this works" - training data is stale
+- ❌ Skipping Context7 for "simple" or "obvious" tasks
+- ❌ Using cached knowledge instead of live documentation
+- ❌ Proceeding when Context7 query fails (STOP and report)
+- ❌ Ignoring Context7 guidance because training data "seems better"
+
+## Query Quality Standards
+
+### Effective Context7 Queries
+
+**DO:**
+- ✅ Query ALL links in Documentation Queries section
+- ✅ Request specific topics relevant to the task
+- ✅ Ask for code examples and patterns
+- ✅ Verify API signatures and parameters
+- ✅ Check for breaking changes and migrations
+
+**DON'T:**
+- ❌ Skip queries assuming training data is sufficient
+- ❌ Query only one link when multiple are listed
+- ❌ Accept generic results - request specifics
+- ❌ Ignore version mismatches in results
+
+### Coverage Requirements
+
+- **100% Query Rate**: Every command/agent execution queries Context7
+- **Complete Coverage**: ALL listed Context7 links must be queried
+- **Result Validation**: Verify Context7 returned relevant information
+- **Fallback Protocol**: If Context7 fails, STOP and report (don't proceed with stale data)
+
+## Integration with Workflow
+
+### Command Execution Flow
+
+```
+User executes command: /pm:epic-decompose feature-name
+
+BEFORE execution:
+1. Read .claude/commands/pm/epic-decompose.md
+2. Extract Documentation Queries section:
+   - mcp://context7/agile/epic-decomposition
+   - mcp://context7/agile/task-sizing
+   - mcp://context7/agile/user-stories
+   - mcp://context7/project-management/task-breakdown
+3. Query Context7 for EACH link
+4. Summarize findings: "Context7 confirms INVEST criteria for user stories..."
+5. PROCEED with command execution using Context7 guidance
+
+DURING execution:
+- Apply Context7 patterns
+- Reference Context7 examples
+- Follow Context7 best practices
+
+AFTER execution:
+- Validate against Context7 standards
+- Flag any deviations from documentation
+```
+
+### Agent Invocation Flow
+
+```
+User invokes agent: @aws-cloud-architect design VPC
+
+BEFORE invocation:
+1. Read .claude/agents/cloud/aws-cloud-architect.md
+2. Extract Documentation Queries section:
+   - mcp://context7/aws/compute
+   - mcp://context7/aws/networking
+   - mcp://context7/terraform/aws
+3. Query Context7 for EACH link
+4. Summarize: "Context7 shows VPC best practices: /16 for staging, /20 for prod..."
+5. PROCEED with agent work using Context7 knowledge
+
+DURING agent work:
+- Use current AWS API patterns from Context7
+- Apply Terraform AWS provider patterns from Context7
+- Follow networking best practices from Context7
+
+AFTER agent work:
+- Cross-check VPC design against Context7 recommendations
+- Ensure no deprecated patterns used
+```
+
+## Violation Consequences
+
+**If Context7 enforcement is violated:**
+
+### Immediate Actions
+
+1. **STOP** execution immediately
+2. **IDENTIFY** what was implemented without Context7 verification
+3. **DELETE** code based on potentially stale training data
+4. **QUERY** Context7 for the relevant documentation
+5. **REIMPLEMENT** using Context7 guidance
+6. **DOCUMENT** violation and correction
+
+### Severity Levels
+
+**Level 1 - Minor (Warning):**
+- Partial Context7 queries (some links skipped)
+- Action: Complete missing queries, validate implementation
+
+**Level 2 - Moderate (Correction Required):**
+- No Context7 queries performed
+- Action: Stop, query Context7, review implementation
+
+**Level 3 - Critical (Revert and Redo):**
+- Implementation contradicts Context7 documentation
+- Action: Delete code, start over with Context7 guidance
+
+### No Exceptions Policy
+
+- NO "small changes" exceptions
+- NO "I'm confident this is right" exceptions
+- NO "Context7 is slow" exceptions
+- NO "training data matches Context7" assumptions
+
+## Success Metrics
+
+### Compliance Indicators
+
+- ✅ 100% of commands query Context7 before execution
+- ✅ 100% of agents query Context7 before implementation
+- ✅ Zero implementations based solely on training data
+- ✅ All API signatures verified against live documentation
+- ✅ No deprecated patterns in codebase
+- ✅ Context7 findings documented in comments/commits
+
+### Quality Indicators
+
+- ✅ Implementation matches Context7 examples
+- ✅ No "unexpected behavior" due to API changes
+- ✅ Code follows latest framework conventions
+- ✅ Breaking changes identified and addressed proactively
+
+## Automation and Enforcement
+
+### Pre-Command Hook
+
+File: `.claude/hooks/pre-command-context7.js`
+
+**Purpose**: Automatically extract and query Context7 before command execution
+
+**Behavior**:
+1. Intercept command execution
+2. Read command file from `.claude/commands/{category}/{command}.md`
+3. Extract `**Documentation Queries:**` section
+4. Query Context7 MCP for each link
+5. Inject results into command context
+6. Proceed with execution
+
+### Pre-Agent Hook
+
+File: `.claude/hooks/pre-agent-context7.js`
+
+**Purpose**: Automatically extract and query Context7 before agent invocation
+
+**Behavior**:
+1. Intercept agent invocation
+2. Read agent file from `.claude/agents/{category}/{agent}.md`
+3. Extract `**Documentation Queries:**` section
+4. Query Context7 MCP for each link
+5. Inject results into agent context
+6. Proceed with agent work
+
+### Validation Rule
+
+File: `.claude/rules/context7-enforcement.md` (this file)
+
+**Purpose**: Remind Claude to ALWAYS query Context7
+
+**Enforcement**:
+- Read by Claude on every session start
+- Highest priority in rule hierarchy
+- Zero tolerance for violations
+
+## Emergency Fallback
+
+**If Context7 MCP is unavailable:**
+
+1. **ALERT** user immediately: "⚠️ Context7 MCP unavailable - cannot verify documentation"
+2. **REQUEST** user decision:
+   - WAIT for Context7 to become available (RECOMMENDED)
+   - PROCEED with explicit user acknowledgment and risk acceptance
+3. **DOCUMENT** in code: `// WARNING: Implemented without Context7 verification - Context7 MCP was unavailable`
+4. **FLAG** for review: Add TODO to re-verify with Context7 when available
+
+**DO NOT:**
+- ❌ Silently proceed without Context7
+- ❌ Assume training data is sufficient
+- ❌ Skip documentation queries
+
+## Related Rules
+
+- **TDD Enforcement** (`.claude/rules/tdd.enforcement.md`) - Tests first, always
+- **Agent Usage** (`.claude/rules/agent-usage.md`) - When to use specialized agents
+- **Code Quality** (`.claude/rules/code-quality.md`) - Standards and anti-patterns
+
+## Final Reminder
+
+> **Context7 is NOT optional. It is MANDATORY for EVERY command and agent execution.**
+>
+> Training data becomes stale. APIs change. Best practices evolve.
+>
+> Context7 keeps us current. Query it. Every. Single. Time.

package/packages/plugin-core/rules/datetime.md

@@ -0,0 +1,122 @@
+# DateTime Rule
+
+## Getting Current Date and Time
+
+When any command requires the current date/time (for frontmatter, timestamps, or logs), you MUST obtain the REAL current date/time from the system rather than estimating or using placeholder values.
+
+### How to Get Current DateTime
+
+Use the `date` command to get the current ISO 8601 formatted datetime:
+
+```bash
+# Get current datetime in ISO 8601 format (works on Linux/Mac)
+date -u +"%Y-%m-%dT%H:%M:%SZ"
+
+# Alternative for systems that support it
+date --iso-8601=seconds
+
+# For Windows (if using PowerShell)
+Get-Date -Format "yyyy-MM-ddTHH:mm:ssZ"
+```
+
+### Required Format
+
+All dates in frontmatter MUST use ISO 8601 format with UTC timezone:
+
+- Format: `YYYY-MM-DDTHH:MM:SSZ`
+- Example: `2024-01-15T14:30:45Z`
+
+### Usage in Frontmatter
+
+When creating or updating frontmatter in any file (PRD, Epic, Task, Progress), always use the real current datetime:
+
+```yaml
+---
+name: feature-name
+created: 2024-01-15T14:30:45Z  # Use actual output from date command
+updated: 2024-01-15T14:30:45Z  # Use actual output from date command
+---
+```
+
+### Implementation Instructions
+
+1. **Before writing any file with frontmatter:**
+   - Run: `date -u +"%Y-%m-%dT%H:%M:%SZ"`
+   - Store the output
+   - Use this exact value in the frontmatter
+
+2. **For commands that create files:**
+   - PRD creation: Use real date for `created` field
+   - Epic creation: Use real date for `created` field
+   - Task creation: Use real date for both `created` and `updated` fields
+   - Progress tracking: Use real date for `started` and `last_sync` fields
+
+3. **For commands that update files:**
+   - Always update the `updated` field with current real datetime
+   - Preserve the original `created` field
+   - For sync operations, update `last_sync` with real datetime
+
+### Examples
+
+**Creating a new PRD:**
+
+```bash
+# First, get current datetime
+CURRENT_DATE=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
+# Output: 2024-01-15T14:30:45Z
+
+# Then use in frontmatter:
+---
+name: user-authentication
+description: User authentication and authorization system
+status: backlog
+created: 2024-01-15T14:30:45Z  # Use the actual $CURRENT_DATE value
+---
+```
+
+**Updating an existing task:**
+
+```bash
+# Get current datetime for update
+UPDATE_DATE=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
+
+# Update only the 'updated' field:
+---
+name: implement-login-api
+status: in-progress
+created: 2024-01-10T09:15:30Z  # Keep original
+updated: 2024-01-15T14:30:45Z  # Use new $UPDATE_DATE value
+---
+```
+
+### Important Notes
+
+- **Never use placeholder dates** like `[Current ISO date/time]` or `YYYY-MM-DD`
+- **Never estimate dates** - always get the actual system time
+- **Always use UTC** (the `Z` suffix) for consistency across timezones
+- **Preserve timezone consistency** - all dates in the system use UTC
+
+### Cross-Platform Compatibility
+
+If you need to ensure compatibility across different systems:
+
+```bash
+# Try primary method first
+date -u +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || \
+# Fallback for systems without -u flag
+date +"%Y-%m-%dT%H:%M:%SZ" 2>/dev/null || \
+# Last resort: use Python if available
+python3 -c "from datetime import datetime; print(datetime.utcnow().strftime('%Y-%m-%dT%H:%M:%SZ'))" 2>/dev/null || \
+python -c "from datetime import datetime; print(datetime.utcnow().strftime('%Y-%m-%dT%H:%M:%SZ'))" 2>/dev/null
+```
+
+## Rule Priority
+
+This rule has **HIGHEST PRIORITY** and must be followed by all commands that:
+
+- Create new files with frontmatter
+- Update existing files with frontmatter
+- Track timestamps or progress
+- Log any time-based information
+
+Commands affected: prd-new, prd-parse, epic-decompose, epic-sync, issue-start, issue-sync, and any other command that writes timestamps.

package/packages/plugin-core/rules/definition-of-done.md

@@ -0,0 +1,272 @@
+# 🎯 Definition of Done (DoD)
+
+> **A feature is not DONE until ALL criteria are met. No exceptions.**
+
+## Universal DoD Checklist
+
+A feature/task is **DONE** when:
+
+### ✅ Code Quality
+
+- [ ] Code complete and follows all coding standards
+- [ ] No commented-out code or debug statements
+- [ ] No hardcoded values (use config/env variables)
+- [ ] DRY principle applied (no duplication)
+- [ ] SOLID principles followed
+- [ ] Error handling implemented
+- [ ] Logging added for debugging
+
+### 🧪 Testing
+
+- [ ] Unit tests written and passing (>80% coverage)
+- [ ] Integration tests written and passing
+- [ ] E2E tests for critical paths
+- [ ] Visual regression tests passing (UI changes)
+- [ ] Performance tests passing
+- [ ] Security tests passing
+- [ ] All tests run in CI/CD
+
+### 🎨 UI/UX (if applicable)
+
+- [ ] Responsive design verified (mobile, tablet, desktop)
+- [ ] Cross-browser testing completed
+- [ ] Dark mode supported (if applicable)
+- [ ] Loading states implemented
+- [ ] Error states handled
+- [ ] Empty states designed
+- [ ] Animations smooth (<60fps)
+- [ ] Screenshots captured for documentation
+
+### ♿ Accessibility
+
+- [ ] WCAG 2.1 AA compliance verified
+- [ ] Keyboard navigation functional
+- [ ] Screen reader tested
+- [ ] Color contrast ratios met
+- [ ] ARIA labels appropriate
+- [ ] Focus indicators visible
+- [ ] Alt text for images
+
+### 🔒 Security
+
+- [ ] Security scan completed (no critical/high vulnerabilities)
+- [ ] Input validation implemented
+- [ ] SQL injection prevention verified
+- [ ] XSS protection in place
+- [ ] Authentication/authorization correct
+- [ ] Sensitive data encrypted
+- [ ] No secrets in code
+
+### ⚡ Performance
+
+- [ ] Performance requirements met
+- [ ] Database queries optimized
+- [ ] Caching implemented where appropriate
+- [ ] Bundle size within limits
+- [ ] Memory leaks checked
+- [ ] Load testing passed (if applicable)
+
+### 📝 Documentation
+
+- [ ] Code comments added where necessary
+- [ ] README updated (if needed)
+- [ ] API documentation updated
+- [ ] CHANGELOG updated
+- [ ] Architecture docs updated (if applicable)
+- [ ] User documentation created (if needed)
+- [ ] Inline JSDoc/docstrings complete
+
+### 👥 Review & Collaboration
+
+- [ ] Code reviewed and approved by peer
+- [ ] Design reviewed (for UI changes)
+- [ ] Product owner acceptance (if applicable)
+- [ ] No unresolved comments in PR
+- [ ] Branch conflicts resolved
+- [ ] Commit messages follow convention
+
+### 🚀 Deployment Readiness
+
+- [ ] CI/CD pipeline passing (all checks green)
+- [ ] Feature flags configured (if applicable)
+- [ ] Database migrations ready and tested
+- [ ] Rollback plan documented
+- [ ] Monitoring/alerts configured
+- [ ] Deployment notes written
+
+### 🛠️ Technical Debt
+
+- [ ] No new technical debt introduced
+- [ ] Existing debt not increased
+- [ ] Refactoring opportunities documented
+- [ ] TODO comments have associated tickets
+
+## DoD by Feature Type
+
+### API Endpoint
+
+```markdown
+- [ ] OpenAPI/Swagger spec updated
+- [ ] Request validation implemented
+- [ ] Response format consistent
+- [ ] Rate limiting configured
+- [ ] Authentication required (if needed)
+- [ ] Integration tests for all methods
+- [ ] Error responses documented
+- [ ] Performance < 200ms
+```
+
+### Database Change
+
+```markdown
+- [ ] Migration script created
+- [ ] Rollback script created
+- [ ] Migration tested on staging
+- [ ] Indexes optimized
+- [ ] Constraints defined
+- [ ] Backup plan documented
+- [ ] Data integrity verified
+```
+
+### UI Component
+
+```markdown
+- [ ] Storybook story created
+- [ ] Props documented with types
+- [ ] Default props defined
+- [ ] Error boundaries implemented
+- [ ] Accessibility audit passed
+- [ ] Visual regression tests
+- [ ] Theme variables used
+- [ ] RTL support (if required)
+```
+
+### Bug Fix
+
+```markdown
+- [ ] Root cause identified
+- [ ] Regression test written
+- [ ] Fix verified in multiple scenarios
+- [ ] Related code reviewed
+- [ ] No side effects introduced
+- [ ] Performance not degraded
+```
+
+### Infrastructure Change
+
+```markdown
+- [ ] Terraform/IaC updated
+- [ ] Change tested in staging
+- [ ] Rollback procedure documented
+- [ ] Cost impact assessed
+- [ ] Security review completed
+- [ ] Monitoring updated
+- [ ] Runbook updated
+```
+
+## DoD Verification Process
+
+### Self-Check (Developer)
+
+1. Review entire DoD checklist
+2. Mark completed items
+3. Document any exceptions with justification
+4. Attach evidence (screenshots, test results)
+
+### Peer Review
+
+1. Verify developer's checklist
+2. Spot-check critical items
+3. Run tests locally
+4. Review documentation updates
+
+### Automated Verification
+
+```yaml
+# CI/CD Pipeline Checks
+- Linting and formatting
+- Unit test coverage
+- Integration tests
+- Security scanning
+- Performance benchmarks
+- Build success
+- Docker image scan
+```
+
+### Final Verification (Team Lead/PO)
+
+1. Acceptance criteria met
+2. Business value delivered
+3. No blockers for deployment
+4. Stakeholder sign-off (if needed)
+
+## Exceptions Process
+
+### When Exceptions Are Allowed
+
+- Emergency hotfixes (document debt)
+- Proof of concepts (marked clearly)
+- Experimental features (behind flags)
+
+### Exception Requirements
+
+1. Document reason for exception
+2. Create follow-up ticket for completion
+3. Get approval from team lead
+4. Set deadline for resolution
+5. Track in technical debt log
+
+## DoD Evolution
+
+### Quarterly Review
+
+- Review DoD effectiveness
+- Add new criteria based on incidents
+- Remove outdated criteria
+- Adjust based on team feedback
+
+### Continuous Improvement
+
+- Track DoD violations and patterns
+- Automate more checks
+- Simplify where possible
+- Share learnings across teams
+
+## Quick Reference Card
+
+```bash
+# Minimum DoD (cannot skip)
+✓ Tests written and passing
+✓ Code reviewed
+✓ Documentation updated
+✓ Security scan clean
+✓ CI/CD passing
+
+# Additional for UI
++ Responsive design
++ Accessibility verified
++ Visual tests passing
+
+# Additional for API
++ API docs updated
++ Integration tests
++ Performance verified
+
+# Additional for Database
++ Migration tested
++ Rollback ready
++ Backup verified
+```
+
+## Remember
+
+**"Done" means DONE—not "mostly done" or "done except for..."**
+
+The Definition of Done protects:
+
+- **Users** from broken features
+- **Team** from technical debt
+- **Product** from quality issues
+- **Company** from reputation damage
+
+**Quality is not negotiable. Done is not debatable.**