spec
Write a product specification (PRD) from a validated idea or feature request. Use when the user needs to define requirements, user stories, acceptance criteria, or technical specifications before building.
What this skill does
# Product Specification: $ARGUMENTS
You are writing a PRD (Product Requirement Document) for the CEO. If `$ARGUMENTS` is a file path, read that file for context. Otherwise, treat it as the idea description.
## Process
1. If context is insufficient, ask the CEO what they want to build and for whom.
2. Draft a structured PRD with these sections:
- **Overview**: One-paragraph summary of what we're building and why
- **User Stories**: 3-7 stories in format: "As a [role], I want [feature], so that [benefit]"
- **Acceptance Criteria**: For each user story, define Given/When/Then scenarios
- **Release Phases**: Categorize user stories into phases:
- **MVP**: Core features needed for the product to be usable at all
- **P1**: Important features for the next release after MVP
- **P2**: Nice-to-have features that can wait
Ask the CEO to confirm the phasing before finalizing.
- **Technical Requirements**: Stack, integrations, data model, API endpoints
- **Non-Functional Requirements**: Performance targets, security, scalability
- **Out of Scope**: Explicitly list what we're NOT building (prevents scope creep)
- **Open Questions**: Anything that needs CEO input before building
3. Validate with subagents in parallel:
- Delegate to `@engineer` with the draft PRD. Task: validate technical feasibility of each requirement. For each: rate as feasible / needs-design-decision / risky. Flag anything overly complex, suggest simpler alternatives where possible.
- Delegate to `@designer` with the user stories section. Task: identify what screens and user flows are needed. For each user story, note which screens it touches and any UX concerns.
4. Incorporate subagent feedback into the final PRD.
5. Save to `.solopreneur/specs/{date}-{slug}.md` (create the directory if needed).
6. End with the next step prompt. If the spec has 5+ user stories, suggest breaking it into tickets first:
```
-> Next: Break this into implementable tickets:
/solopreneur:backlog .solopreneur/specs/{filename}
Or for smaller specs, go straight to design:
/solopreneur:design .solopreneur/specs/{filename}
```
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.