spawn-task
Create comprehensive, self-contained task prompts for implementing features or fixing bugs.
Create comprehensive, self-contained task prompts for implementing features or fixing bugs.
AID Phase 4 - Development phase. Use for implementing features, TDD practices, code reviews, transitioning from planning to QA.
Framework for writing concise 3P (Progress, Plans, Problems) team updates for executives and stakeholders
Generate a comprehensive daily briefing combining calendar events, email inbox status, and reminders. Use when the user asks to plan their day, get a morning briefing, or wants an overview of their schedule and tasks. This orchestrates multiple skills together.
Use when adding logging, debugging production issues, checking service health, or performing routine operations (adding personalities, database queries). Covers structured logging, correlation IDs, Railway log analysis, and common operations.
Rapid ideation skill adapted from obra/superpowers to kick off cortex sessions. Use when defining scope, aligning on goals, or exploring solution space before coding.
Reviews implemented ADRs by comparing them against actual implementation and updating feedback sections. Use this when the user wants to review an ADR implementation, validate architectural decisions, or update ADR feedback logs.
Automate the workflow from creating a branch to opening a GitHub pull request. Use when the user says "create a PR", "commit and push", "push changes and create PR", or "open a pull request".
Salesforce Agentforce AI agents and autonomous automation (2025)
Review specifications to find gaps and generate clarifying questions. Use when reviewing spec.md, finding missing requirements, identifying ambiguities, or when you see "review spec", "find gaps", "what's missing", or "clarify requirements". Focuses on product decisions, not implementation details.
Complete Git expertise system for ALL git operations. PROACTIVELY activate for: (1) ANY Git task (basic/advanced/dangerous), (2) Repository management, (3) Branch strategies and workflows, (4) Conflict resolution, (5) History rewriting/recovery, (6) Platform-specific operations (GitHub/Azure DevOps/Bitbucket), (7) Advanced commands (rebase/cherry-pick/filter-repo). Provides: complete Git command reference, safety guardrails for destructive operations, platform best practices, workflow strategies, reflog recovery techniques, and expert guidance for even the most risky operations. Always asks user preference for automatic commits vs manual control.
Emergency release workflow for critical bug fixes and security patches. Use when production issues require fast-track deployment.
PM role in AID methodology. Use for requirements, user stories, acceptance criteria, stakeholder management, scope definition.
AID Phase 3 - Implementation Planning with consolidation-first approach. Resolves contradictions between PRD and Tech Spec, creates consolidated master document, then breaks down into actionable tasks and populates Jira. Includes sprint planning and risk assessment.
Developer role in AID methodology. Use for implementation, debugging, technical design, TDD workflow, code review.
Create GitHub issues with AI labeling and content type detection. TRIGGERS - create issue, file bug, feature request, report issue, gh issue create, new issue.
Expand seeds and escape convergent ideation. Use when you have the start of an idea and want to grow it, when brainstorming produces the same ideas every time, or when you need to explore possibility space.
Use when activating visual showcase modes (supersaiyan, kamehameha, over9000) for UI or interaction design - provides mode-specific enhancement checklists.
Generate Mermaid diagrams for educational content. Use when visualizing concepts, architectures, or workflows.
Manages MPEP index lifecycle including downloads, building, maintenance, and optimization.