Loading...
Loading...
Found 318 Skills
Bootstrap or adapt project docs using project-documentation-template. Core goal - produce structured lifecycle documentation aligned with enterprise template. Initialize (empty) or Adjust (non-empty); repeatable; strict kebab-case naming.
Agent skill for v3-queen-coordinator - invoke with $agent-v3-queen-coordinator
Draft stakeholder updates tailored to audience — executives, engineering, customers, or cross-functional partners. Use when writing weekly status updates, monthly reports, launch announcements, risk communications, or decision documentation.
Collaborative design phase for feature lifecycle: explore requirements, discuss trade-offs, produce design document. Use when starting a new feature that needs design before implementation. Use for "design feature", "let's think through", "explore approaches", or "/feature-design". Do NOT use for simple bug fixes or tasks that don't need design discussion.
Design optimal cloud architecture based on your platform engineering requirements. Use when planning new services, migrations, or infrastructure changes that must align with organizational standards.
Implements design patterns including Clean Architecture, SOLID principles, and comprehensive software design best practices. Use when designing systems, reviewing architecture, establishing patterns, or making structural decisions.
arc42 architecture documentation template and guidance
Sistema para convertir logros tecnicos en narrativas que comunican senioridad e impacto. Usar cuando el usuario necesite escribir sobre sus proyectos, preparar presentaciones tecnicas, documentar decisiones de arquitectura, o comunicar complejidad a audiencias no-tecnicas. Activa con palabras como explicar proyecto, presentacion, documentar, caso de estudio, blog tecnico, conferencia. Especializado en developers senior que necesitan comunicar impacto business.
Use when a Beat change is implemented and ready to archive — not for verifying implementation
Design system architecture, APIs, and component interfaces. Use for architectural decisions and system design.
Use when implementing data-driven tests with TestNG DataProviders, factory methods, and parameterization patterns.
Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs/specs/. Includes validation checklist, consistency verification, and overlap detection.