discovery
Research and discovery workflow for document deliverables — competitive analyses, architecture comparisons, ADR scaffolding, literature reviews, vendor evaluations. No TDD requirement. Phases: gathering → synthesizing → completed. Triggers: 'discover', 'research', 'explore topic', or /exarchos:discover.
What this skill does
# Discovery Workflow Skill
A workflow type for tasks whose deliverable is a **document, not code**. Explicitly
exempt from the Iron Law (no failing test requirement) because there is nothing to test.
## When to Use
- Competitive analyses and market research
- Architecture comparisons and ADR scaffolding
- Literature reviews and vendor evaluations
- Design research that does NOT feed into implementation planning
## When NOT to Use
- If the deliverable includes code changes → use `/exarchos:oneshot` or `/exarchos:ideate`
- If you need TDD enforcement → use any other workflow type
- If the research feeds directly into implementation → use `/exarchos:ideate` (which includes a design phase)
## Phases
### Phase 1: Gathering (initial)
Collect sources, references, and raw material for the deliverable.
1. Define the research question or deliverable scope
2. Identify and collect sources (URLs, documents, code references)
3. Record sources in workflow state:
```typescript
mcp__plugin_exarchos_exarchos__exarchos_workflow({
action: "update", featureId: "<id>",
updates: { "artifacts.sources": ["<source1>", "<source2>", "..."] }
})
```
4. Create an outline of the deliverable
**Transition:** When `artifacts.sources` is a non-empty array → `synthesizing`
### Phase 2: Synthesizing
Draft the deliverable document from gathered sources.
1. Write the document based on gathered sources and outline
2. Commit the document to the repo (typically under `docs/research/` or `docs/designs/`)
3. Record the report path:
```typescript
mcp__plugin_exarchos_exarchos__exarchos_workflow({
action: "update", featureId: "<id>",
updates: { "artifacts.report": "<path-to-document>" }
})
```
**Transition:** When `artifacts.report` is set → `completed`
### Optional: Escalation to Implementation
If discovery surfaces an implementation need:
1. Note the finding in the report
2. After completing the discovery workflow, start a new workflow:
```bash
/exarchos:ideate <implementation-topic>
```
Reference the discovery report as design input.
## Event Emissions
Optionally emit events at key moments for observability:
```typescript
mcp__plugin_exarchos_exarchos__exarchos_event({
action: "append", stream: "<featureId>",
event: { type: "discovery.sources_collected", data: { sourceCount: N } }
})
```
```typescript
mcp__plugin_exarchos_exarchos__exarchos_event({
action: "append", stream: "<featureId>",
event: { type: "discovery.report_committed", data: { path: "<report-path>" } }
})
```
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.