requirement-analyzer
Analyzes ideas and extracts functional and non-functional requirements. Use when breaking down concepts into specific, measurable requirements. Identifies what needs to be built, constraints, and success criteria.
What this skill does
# Requirement Analyzer Skill ## Instructions 1. Analyze the provided idea or concept 2. Extract functional requirements (what the system should do) 3. Identify non-functional requirements (performance, security, scalability, etc.) 4. Determine constraints (technical, time, resource limitations) 5. Define acceptance criteria for each requirement 6. Prioritize requirements (must-have, should-have, nice-to-have) 7. Identify dependencies between requirements 8. Format requirements in a clear, structured format ## Examples **Input:** "I want a user authentication system" **Output:** ```markdown ## Functional Requirements ### Must-Have - FR1: Users can register with email and password - Acceptance: User can create account, receives confirmation email - FR2: Users can log in with email/password - Acceptance: Valid credentials grant access, invalid credentials show error - FR3: Users can reset forgotten passwords - Acceptance: Password reset link sent via email, user can set new password ### Should-Have - FR4: Users can log in with OAuth providers (Google, GitHub) - Acceptance: User can authenticate via OAuth, account linked to email ## Non-Functional Requirements - NFR1: Authentication must complete in < 2 seconds - NFR2: Passwords must be hashed using bcrypt (minimum 10 rounds) - NFR3: System must support 10,000 concurrent users - NFR4: All authentication endpoints must use HTTPS ## Constraints - Must use existing database infrastructure - Must comply with GDPR for user data - Must integrate with existing email service ## Dependencies - User database schema - Email service API - Session management system ``` **Input:** "Build a task management API" **Output:** ```markdown ## Functional Requirements ### Must-Have - FR1: Create, read, update, delete tasks - FR2: Assign tasks to users - FR3: Set task priorities and due dates - FR4: Filter and search tasks ### Should-Have - FR5: Task comments and attachments - FR6: Task status workflow (todo, in-progress, done) ## Non-Functional Requirements - NFR1: API response time < 200ms for 95% of requests - NFR2: Support pagination for large result sets - NFR3: RESTful API design following OpenAPI 3.0 ## Constraints - Must use PostgreSQL database - Must support authentication via JWT tokens ``` ## Format Guidelines - Use clear requirement IDs (FR1, NFR1, etc.) - Include acceptance criteria for each requirement - Prioritize requirements clearly - Identify technical and business constraints - Note dependencies and integration points
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.