cc-power-user

Use this agent when: 1. **After implementing a new feature or module**: Review the technical design and implementation patterns to ensure consistency and maintainability. - Example: User says "I've just finished implementing the user authentication flow" → Launch this agent to review the architectural patterns, identify potential flaws, and suggest improvements. 2. **When reviewing code changes**: Proactively assess design patterns and architectural decisions in recent commits. - Example: User commits changes to backend service → Assistant: "Let me use the architecture-guardian agent to review the design patterns and architectural consistency of your recent changes." 3. **During feature planning**: Evaluate proposed technical approaches before implementation. - Example: User asks "What's the best way to implement real-time notifications?" → Assistant: "I'll engage the architecture-guardian agent to analyze this requirement against our current architecture and recommend an MVP-appropriate solution." 4. **When technical debt is suspected**: Identify areas where maintenance complexity is growing. - Example: User mentions "The payment module is getting harder to work with" → Launch this agent to analyze the module's architecture and identify refactoring opportunities. 5. **For architectural consistency checks**: Ensure new components align with established patterns across backend service, frontend, and website services. - Example: User implements a new API endpoint → Assistant: "I'm going to use the architecture-guardian agent to verify this follows our established API design patterns and identify any inconsistencies." 6. **When onboarding new patterns**: Evaluate if introducing a new technical pattern is justified for an MVP. - Example: User suggests "Should we use event sourcing for this?" → Launch this agent to assess the complexity-to-benefit ratio for the current MVP stage.

Analyzes the backend service (Golang/PostgreSQL) and creates surgical, precise developer guidelines documentation. Only captures essential context that AI agents need to work effectively on this service.

Autonomous Golang backend developer for the backend service. Works on features, bug fixes, refactoring, and maintenance following established patterns and guidelines. Can delegate to specialized agents and handle context limits via handoff.

Use this agent when you need to analyze, research, or understand the your project's golang backend service located at $HOME/Projects/your-project/backend service. This includes investigating code architecture, understanding implementation patterns, analyzing dependencies, reviewing API endpoints, examining database schemas, or researching specific features and functionalities within the backend service. Examples: - <example> user: "I need to understand how authentication works in the backend service" assistant: "I'll use the backend agent to analyze the authentication implementation in the backend service." <Task tool call to backend agent> </example> - <example> user: "Can you explain the database schema used in the your project backend?" assistant: "Let me launch the backend agent to investigate the database schema and models in the backend service." <Task tool call to backend agent> </example> - <example> user: "What API endpoints are available in the backend service?" assistant: "I'll use the backend agent to research and document all available API endpoints in the backend service." <Task tool call to backend agent> </example> - <example> user: "How is error handling implemented in the golang backend?" assistant: "I'm going to use the backend agent to analyze the error handling patterns and practices in the backend service codebase." <Task tool call to backend agent> </example>

---

Shared quality gates all phases must pass before proceeding. Single source of truth for pre-commit, tests, code quality, security, performance, documentation, CI, and acceptance criteria.

Refine GitHub issues by creating WHAT/WHY/HOW sections and preparing them for implementation. Adds issues to GitHub Projects V2, sets status to "Ready", and assigns the current iteration.

Transform a GitHub issue into a production-ready pull request with automated PR review. Executes full workflow including refinement check, code generation, RL loop, testing, PR creation, automated review, feedback application, and re-verification before marking ready for human review.

Shared skill for GitHub Projects V2 API operations. Includes GraphQL mutations for adding issues, updating status, and managing iterations.

Transform ambiguous GitHub issues into refined specifications with WHAT, WHY, and HOW sections. Use before implementing features or fixes when issue lacks clear requirements.