email-drafting
ๅฟซ้ๆ้ฝๅไผใ็ฎ็ใ่ฏญๆฐๅ CTA ็้ฎไปถๅไฝ SOP๏ผ่ฆ็ๆฐๅปบ้ฎไปถไธๅๅค็บฟ็จไธค็งๅธธ่งๅบๆฏใ
ๅฟซ้ๆ้ฝๅไผใ็ฎ็ใ่ฏญๆฐๅ CTA ็้ฎไปถๅไฝ SOP๏ผ่ฆ็ๆฐๅปบ้ฎไปถไธๅๅค็บฟ็จไธค็งๅธธ่งๅบๆฏใ
UIใใๆ ๅ ฑ่จญ่จ๏ผๅชๅ ๅบฆ/ๆง้ ๏ผ๏ผใคใณใฟใฉใฏใทใงใณ๏ผ็ถๆ ้ท็งป๏ผ๏ผใใธใฅใขใซ๏ผใใผใณ๏ผใใจใใฆ่จญ่จใใๅฎ่ฃ ๅฏ่ฝใชไปๆงใธ่ฝใจใใ่ฆใ็ฎใ ใใงใชใใใซใผใซๅ๏ผใณใณใใผใใณใ/ใใผใฏใณ๏ผใซๅฏใใใ
็ซฏๅฐ็ซฏ่ง้ขๅถไฝ playbook๏ผ็ญๅโ็ด ๆ่ง่โๅช่พโๅญๅนโๅฏผๅบโๅๅธโ้ชๆถ๏ผ๏ผๅผบ่ฐๅฏๅค็ฐ็ไบคไปๆต็จใ
Rules persuade. Structure IS argument. Design consciously.
Facilitate effective sprint retrospectives for continuous team improvement. Use when conducting team retrospectives, identifying improvements, or fostering team collaboration. Handles retrospective formats, action items, and facilitation techniques.
Router skill - analyze requirements and direct to appropriate tactics
Framework for writing concise 3P (Progress, Plans, Problems) team updates for executives and stakeholders
Comprehensive guide for choosing the right MAP workflow based on task type and requirements
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.
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.
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.
Code quality metrics and continuous improvement. Use when quality standards guidance is required.
Use when turning PRDs or feature specs into actionable implementation workflows - provides structured task decomposition, dependency mapping, and validation gates.
Use when implementing a feature or multi-file code change - provides structured implementation flow with persona selection, validation, and testing guidance.
Critical-thinking brainstorming partner that acts as a requirements analyst. Use when users present ideas, feature requests, or problems they want to solve. Triggers include "I want to build", "help me validate", "users need", "I'm thinking of creating", or any request involving problem/solution validation. This skill aggressively challenges assumptions, questions perceived problems, demands evidence, and ensures solutions address genuine needs before exploring implementation.
QA Engineer role in AID methodology. Use for test strategy, BDD scenarios, bug reporting, acceptance testing, flaky test prevention.
Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
Interactive idea refinement using Socratic method to develop fully-formed designs
Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.
Guides through adding new features, MCP tools, analyzers, and extending the patent creator system.
Write functional requirements using FR-XXX format with RFC 2119 keywords (MUST, SHOULD, MAY), success criteria (SC-XXX), and edge case identification. Use when writing requirements, specifications, success criteria, or when you see "functional requirements", "FR-", "SC-", "RFC 2119", "MUST SHOULD MAY", or "edge cases".
AID Phase 0 - Research & discovery. Use for validating problem spaces, identifying stakeholders, defining success metrics, deciding whether to proceed.