ideation-intake

Included with Lifetime

$97 forever

Start a new ideation run by creating a run folder and intake template, then validate the filled template and produce a structured problem_space.md. Use when the user says "start ideation", "new ideation run", "define problem space", or invokes /ideation:intake.

General

What this skill does


# Ideation Intake

This skill operates in two phases:

## Phase 1: Create Template

When the user invokes this skill for the first time (no filled intake.md exists):

1. **Read configuration** from `.claude/ideation.local.md` if it exists. Parse YAML frontmatter for `default_run_prefix` and `output_root`. Use defaults (`ideation-run`, `.`) if missing.

2. **Determine run folder name**:
   - If the user provides a run name argument, use it directly (e.g. `my-project-ideas`)
   - Otherwise, auto-number: scan `output_root` for existing folders matching `{default_run_prefix}-NN` and use the next number (zero-padded to 2 digits)

3. **Create the run folder** at `{output_root}/{run-name}/`

4. **Write `intake.md`** into the run folder using the template from [references/intake-template.md](../ideation/references/intake-template.md). Copy it verbatim.

5. **Tell the user**: "I've created `{run-folder}/intake.md`. Fill in the template with your problem areas, capabilities, and constraints, then run `/ideation:intake {run-folder}` again to validate and generate the problem space."

**Stop here.** Do not proceed to Phase 2 until the user has filled in the template.

## Phase 2: Validate and Generate

When the user invokes this skill on a run folder that already has a filled `intake.md`:

1. **Read `intake.md`** from the run folder.

2. **Validate completeness**:
   - At least 1 problem area with all fields filled (Who, What happens, What should happen, Severity)
   - At least 1 existing capability with all fields filled
   - Solution constraints section has at least one "Must" and one "Must not"
   - Target users is not empty
   - If validation fails, report what's missing and stop

3. **Assign IDs** sequentially:
   - Problems: `prob_01`, `prob_02`, ...
   - Existing capabilities: `cap_01`, `cap_02`, ...
   - Aspirational capabilities: `asp_01`, `asp_02`, ...

4. **Write `problem_space.md`** with YAML frontmatter following the data contract:

```yaml
---
run_id: {run-folder-name}
created_at: {ISO8601 timestamp}
version: "1.0"
problem_count: {count}
capability_count: {count}
aspirational_count: {count}
timeline: {from constraints}
---
```

The body transforms the user's input into the structured format with assigned IDs. Preserve the user's language — do not rewrite their descriptions. Only clean up formatting and add IDs.

**Severity mapping**: The user's "How bad is it (1-5)" becomes `**Severity**: X/5`.

5. **Report**: Show the user a summary of what was parsed — problem count, capability count, aspirational count, and the assigned IDs.

## Reference

- Template: [intake-template.md](../ideation/references/intake-template.md)
- Output schema: [data-contracts.md](../ideation/references/data-contracts.md) (Stage 1 section)

Files: 1

Size: 3.1 KB

Complexity: 13/100

Category: General

Source: https://github.com/kjgarza/marketplace-claude/tree/main/plugins/ideation/skills/ideation-intake

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce 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).

Generalscripts

relationship-science-coach

Included

Use 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.

Generalscripts

building-sf-integrations

Included

Salesforce 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).

Generalscripts

venue-templates

Included

Access 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.

Generalscripts

let-fate-decide

Included

Draws 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.

Generalscripts

net-ops

Included

Cross-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.

Generalscripts