@fredcallagan/arn-spark 5.1.0

package/plugins/arn-spark/skills/arn-spark-init/references/jira-mcp-setup.md

@@ -0,0 +1,61 @@
+# Atlassian Remote MCP Server Setup
+
+The Atlassian Remote MCP Server is the official, cloud-hosted MCP server for Jira Cloud integration. It uses OAuth 2.1 for authentication and provides native Claude Code integration for issue operations.
+
+**Documentation:** https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
+
+## Prerequisites
+
+- A Jira Cloud instance with an active account
+- Claude Code installed and running
+- Project initialized with `/arn-spark-init` or `/arn-code-init` (or in the process of running it)
+
+## Setup Procedure
+
+### Step 1: Add the MCP Server
+
+Run the following command from your project directory:
+
+```bash
+claude mcp add atlassian --scope project --transport http --url https://mcp.atlassian.com/v1/mcp
+```
+
+This adds the Atlassian MCP server configuration to the **project's** `.mcp.json` file (not the Arness plugin's `.mcp.json`).
+
+### Step 2: Restart Claude Code
+
+MCP servers are loaded at session start. After adding the server, restart Claude Code for the new server to become available:
+
+1. Exit the current Claude Code session
+2. Start a new session in the same project directory
+
+### Step 3: Authenticate via OAuth 2.1
+
+On the first use of any Atlassian MCP tool, a browser window will open automatically for OAuth 2.1 authentication:
+
+1. Sign in with your Atlassian account
+2. Authorize the MCP server to access your Jira instance
+3. Return to Claude Code -- the session will continue with authenticated access
+
+### Step 4: Verify the Connection
+
+Run `/mcp` in Claude Code to confirm the Atlassian server is listed and connected:
+
+```
+/mcp
+```
+
+Look for `atlassian` in the server list with a `connected` status.
+
+## Known Limitations
+
+- **Re-authentication:** The OAuth 2.1 token may expire multiple times per day. When this happens, a browser window will open again for re-authentication. This is a known limitation of the Atlassian Remote MCP Server.
+- **Cloud only:** The remote MCP server works with Jira Cloud only. Jira Data Center and Jira Server are not supported.
+- **Scope:** The MCP server is configured per-project (`--scope project`). Each project that uses Jira integration needs its own MCP configuration.
+
+## Notes
+
+- The MCP server is added to the project's `.mcp.json`, not the Arness plugin's `.mcp.json`
+- Arness uses the MCP server's `list_projects` tool during `/arn-spark-init` (or `/arn-code-init`) to let the user pick their Jira project
+- Once configured, Arness skills (`/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr`) use the MCP server transparently for all Jira operations
+- No API keys or tokens need to be stored in project files -- OAuth 2.1 handles authentication at runtime

package/plugins/arn-spark/skills/arn-spark-init/references/platform-labels.md

@@ -0,0 +1,97 @@
+# Arness Platform Labels
+
+Arness uses labels for issue management and tracking across supported platforms. The label strategy varies by platform: GitHub uses repository labels with explicit creation, while Jira uses freeform labels with implicit creation plus native issue types and priorities.
+
+---
+
+## GitHub
+
+Labels created during `/arn-spark-init` (or `/arn-code-init`) when GitHub integration is detected. These labels are used by Arness skills for issue management and tracking.
+
+### Labels
+
+| Label | Color | Purpose | Used By |
+|-------|-------|---------|---------|
+| `arness-backlog` | `#d4c5f9` (lavender) | Deferred items from PRs or postponed features | `/arn-code-review-pr`, `/arn-code-create-issue`, `/arn-code-pick-issue` |
+| `arness-feature-issue` | `#0e8a16` (green) | Feature requests tracked via Arness | `/arn-code-create-issue`, `/arn-code-pick-issue` |
+| `arness-bug-issue` | `#d93f0b` (red) | Bug reports tracked via Arness | `/arn-code-create-issue`, `/arn-code-pick-issue` |
+| `arness-priority-high` | `#b60205` (dark red) | High priority | `/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr` |
+| `arness-priority-medium` | `#fbca04` (yellow) | Medium priority | `/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr` |
+| `arness-priority-low` | `#c5def5` (light blue) | Low priority | `/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr` |
+| `arness-rejected` | `#e4e669` (olive) | Issue reviewed and rejected as invalid or out of scope | `/arn-code-pick-issue` |
+
+### Plugin Repository Label
+
+The following label lives on the **Arness plugin repository** (not on user projects). It is pre-created by plugin maintainers and used by `/arn-code-report` to tag diagnostic issues.
+
+| Label | Color | Purpose | Used By |
+|-------|-------|---------|---------|
+| `arness-report` | `#1d76db` (blue) | Issue reported via /arn-code-report diagnostic | `/arn-code-report` (plugin repo only) |
+
+### Creation Command
+
+Labels are created using `gh label create` which is idempotent -- existing labels are skipped:
+
+```bash
+gh label create "arness-backlog" --color "d4c5f9" --description "Deferred items from PRs or postponed features" --force
+gh label create "arness-feature-issue" --color "0e8a16" --description "Feature requests tracked via Arness" --force
+gh label create "arness-bug-issue" --color "d93f0b" --description "Bug reports tracked via Arness" --force
+gh label create "arness-priority-high" --color "b60205" --description "High priority" --force
+gh label create "arness-priority-medium" --color "fbca04" --description "Medium priority" --force
+gh label create "arness-priority-low" --color "c5def5" --description "Low priority" --force
+gh label create "arness-rejected" --color "e4e669" --description "Issue reviewed and rejected as invalid or out of scope" --force
+```
+
+### Notes
+
+- Labels are only created when GitHub integration is detected during `/arn-spark-init` (or `/arn-code-init`)
+- The `--force` flag updates existing labels if the color or description has changed
+- Projects without GitHub integration skip label creation entirely
+- Skills that use labels check for their existence and create missing ones on demand
+
+---
+
+## Jira
+
+Jira labels are freeform -- they are created implicitly on first use and do not need to be pre-created during initialization. Arness combines Jira labels with native issue types and priority fields for a richer mapping.
+
+### Labels
+
+Arness uses the following label names when creating and filtering Jira issues:
+
+| Label | Purpose | Used By |
+|-------|---------|---------|
+| `arness-feature-issue` | Feature requests tracked via Arness | `/arn-code-create-issue`, `/arn-code-pick-issue` |
+| `arness-bug-issue` | Bug reports tracked via Arness | `/arn-code-create-issue`, `/arn-code-pick-issue` |
+| `arness-backlog` | Deferred items from PRs or postponed features | `/arn-code-review-pr`, `/arn-code-create-issue`, `/arn-code-pick-issue` |
+| `arness-rejected` | Issue reviewed and rejected as invalid or out of scope | `/arn-code-pick-issue` |
+| `arness-priority-high` | High priority | `/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr` |
+| `arness-priority-medium` | Medium priority | `/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr` |
+| `arness-priority-low` | Low priority | `/arn-code-create-issue`, `/arn-code-pick-issue`, `/arn-code-review-pr` |
+
+### Issue Type Mapping
+
+Arness maps its label categories to native Jira issue types:
+
+| Arness Label | Jira Issue Type |
+|------------|-----------------|
+| `arness-feature-issue` | Story |
+| `arness-bug-issue` | Bug |
+| `arness-backlog` | Task |
+
+### Priority Mapping
+
+Arness maps its priority labels to native Jira priority levels:
+
+| Arness Label | Jira Priority |
+|------------|---------------|
+| `arness-priority-high` | High |
+| `arness-priority-medium` | Medium |
+| `arness-priority-low` | Low |
+
+### Notes
+
+- Jira labels are applied in addition to native issue type and priority fields
+- Labels are created implicitly by Jira on first use -- no `create` command is needed
+- Arness uses both the label and the native Jira field so issues are filterable via JQL or the label sidebar
+- Bitbucket's built-in issue tracker is not supported by Arness

package/plugins/arn-spark/skills/arn-spark-naming/SKILL.md

@@ -0,0 +1,275 @@
+---
+name: arn-spark-naming
+description: >-
+  This skill should be used when the user says "naming", "brand name",
+  "name my product", "find a name", "product naming", "brand naming",
+  "what should I call it", "name ideas", "pick a name", "naming session",
+  "help me name this", "brainstorm names", "come up with a name",
+  "arn spark naming", "arn-spark-naming", or wants to find a brand
+  name for their product through strategic analysis, creative generation,
+  qualitative scoring, and due diligence including domain availability
+  and trademark screening.
+version: 1.0.0
+---
+
+# Arness Spark Naming
+
+Guide a product from nameless concept to validated brand name through a structured 4-step methodology, driven by the `arn-spark-brand-strategist` agent. Produces a **naming brief** (`naming-brief.md`) in the vision directory and a **naming report** (`naming-report.md`) in the reports directory.
+
+## Prerequisites
+
+1. Read the project's arness.md for the `## Arness` section.
+2. Extract **Vision directory** and **Reports directory** paths. If no `## Arness` section exists or Arness Spark fields are missing, inform the user: "Arness Spark is not configured for this project yet. Run `/arn-brainstorming` to get started — it will set everything up automatically." Do not proceed without it.
+3. Create directories if they do not exist.
+
+## Step 0: Context Gathering
+
+### Product context
+
+Check for `<vision-dir>/product-concept.md`:
+
+**If found:** Read and extract: vision statement, value proposition, target audience, product pillars, competitive landscape. Summarize the extracted context to the user: "Found your product concept. I'll use this as the foundation for naming."
+
+**If not found:**
+
+Ask the user:
+
+**"No product concept found. How should I learn about your product?"**
+1. **Describe your product** — Provide a description in the next message
+2. **Point me to a file** — Specify a file path containing product information
+3. **Explore current project** — I'll read README, package.json, and code to infer what the product does
+
+If option 3: invoke `arn-spark-brand-strategist` in `brand-dna` mode with instructions to explore the project and summarize the product context.
+
+### Target market
+
+Ask the user:
+
+**"What is the primary target market? This determines trademark databases and languages for linguistic screening."**
+1. **United States** — USPTO trademark search, English + Spanish linguistic check
+2. **European Union** — EUIPO trademark search, English + French + German + Spanish + Italian
+3. **United Kingdom** — IPO trademark search, English linguistic check
+4. **Global / Multiple regions** — WIPO + major national databases, all major languages
+
+### Existing naming brief
+
+Check for `<vision-dir>/naming-brief.md`:
+
+**If found:**
+
+Ask the user:
+
+**"A naming brief already exists. How would you like to proceed?"**
+1. **Resume from where I left off** — Continue from the first incomplete section
+2. **Start fresh** — Preserve existing as naming-brief-previous.md and begin new
+
+If resume: read the brief, detect which sections contain "-- Pending --" or are missing, and resume from the first incomplete step.
+
+---
+
+## Step 1: Strategic Foundation (Brand DNA)
+
+Invoke the `arn-spark-brand-strategist` agent in `brand-dna` mode via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spark/skills/arn-spark-ensure-config/references/ensure-config.md` "Dispatch convention" for fallback). Context:
+- Product context (from product-concept.md or user input)
+- Competitive landscape (from product concept, or agent will research via websearch)
+- Target market
+
+The agent returns: brand personality profile, audience vocabulary, competitor name landscape, 1-2 recommended naming categories with rationale.
+
+Present the Brand DNA analysis to the user.
+
+Ask the user:
+
+**"Proceed with the recommended naming categories?"**
+1. **Yes, proceed with [recommended categories]** (Recommended) — Use the strategist's recommendation (substitute actual category names from the Brand DNA analysis)
+2. **Choose different categories** — Select naming categories manually
+
+If option 2:
+
+Ask the user (multiSelect: true):
+
+**"Select naming categories to explore (select all that apply):"**
+1. **Descriptive** — Names that describe what the product does (PayPal, Dropbox)
+2. **Evocative** — Names that suggest a feeling or metaphor (Slack, Nike)
+3. **Invented / Abstract** — Completely new words (Spotify, Google)
+4. **Lexical** — Wordplay, puns, alliteration (Pinterest, Netflix)
+
+Then prompt (free-text): "Any existing name ideas, words you love, or words you hate? These will seed the creative sprint. Type 'none' or 'skip' to continue without seeds."
+
+Write initial `<vision-dir>/naming-brief.md` using the creative brief template:
+> Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/creative-brief-template.md`
+
+Populate: Context and Brand DNA sections. Mark remaining sections as "-- Pending --".
+
+---
+
+## Step 2: Creative Sprint (The Big List)
+
+Four generation rounds via `arn-spark-brand-strategist` in `generation` mode.
+
+**Round 1 — Seed harvest:** Invoke agent with user's existing ideas and preferences as seeds. If no seeds, skip to Round 2.
+
+**Round 2 — Category sprints:** Invoke agent once per selected category, requesting 50-80 candidates each. Pass the brand DNA context and dead directions. Present candidates to user after each category sprint for early feedback.
+
+**Round 3 — Mashup round:** Invoke agent with all Round 1-2 candidates. Cross-pollinate fragments across categories. Target: 30-50 mashup candidates.
+
+**Round 4 — User collaboration checkpoint:** Present the complete candidate list organized by category. This is a free-text conversation loop: the user marks favorites (star), flags directions to kill, and may suggest additional directions. Iterate until the user signals satisfaction.
+
+Target: 200+ total candidates across all rounds.
+
+Update `naming-brief.md` with Creative Sprint Results section (generation stats, candidates by category, starred favorites, dead directions).
+
+---
+
+## Step 3: Qualitative Filter (Six Senses)
+
+Load the scoring methodology:
+> Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/naming-methodology.md`
+
+Invoke the `arn-spark-brand-strategist` agent in `scoring` mode via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spark/skills/arn-spark-ensure-config/references/ensure-config.md` "Dispatch convention" for fallback). Context: full candidate list, user-starred favorites, dead directions.
+
+**Pass 1:** Agent filters 200+ candidates to 30-40 by removing obvious duds (unpronounceable, too long, too similar, offensive, dead directions). User-starred names always survive Pass 1.
+
+**Pass 2:** Agent scores each surviving candidate on the Six Senses (1-5 each):
+1. Appearance — visual punch, letter count
+2. Sound — euphony, Phone Test
+3. Meaning — associations, connotations
+4. Memorability — stickiness, alliteration
+5. Function — verbability, typability, handle-fit
+6. Scalability — expansion headroom
+
+Present the scored table sorted by total score (6-30).
+
+Prompt (free-text): "Select 5-8 finalists for due diligence. You can pick from the top of the table, or choose names you like regardless of score."
+
+Update `naming-brief.md` with Qualitative Filter Results section.
+
+---
+
+## Step 4: Cold Shower (Due Diligence)
+
+### 4a — Domain Availability
+
+Load the WHOIS/RDAP server reference:
+> Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/whois-server-map.md`
+
+**How it works:** Both scripts use RDAP (the modern IETF standard) as the primary lookup method, with port-43 WHOIS and system `whois` as built-in fallbacks. The fallback chain per domain is: RDAP → port-43 WHOIS → system whois → manual URL. The scripts handle this automatically — no manual fallback logic needed.
+
+**Environment detection** (priority order):
+
+1. Check Python: run `python3 --version`. If available, use `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/scripts/whois-check.py`.
+2. Check Node.js: run `node --version`. If available, use `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/scripts/whois-check.js`.
+3. Neither available: skip automated checking. Present manual fallback URLs (`https://www.whois.com/whois/[domain]`) for each domain.
+
+Note: System `whois` is NOT required — both scripts have it as a built-in last-resort fallback (gracefully skipped on Windows where `whois` is not available). Python and Node.js scripts work identically across Linux, macOS, Windows, and WSL2.
+
+**Rate limit discovery:** Before running queries, use websearch for `"[RDAP or WHOIS server name]" rate limit` for the primary TLD servers involved. Set `delay_seconds` to the most conservative discovered limit. Floor: 2 seconds. Default if unknown: 3 seconds.
+
+**Domain list construction:** Each finalist name × TLDs. Start with global TLDs: `.com` (essential), `.io`, `.co`, `.dev`, `.app`, `.ai`. Then add country-specific TLDs based on target market (see `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/whois-server-map.md` for the market-to-TLD mapping):
+- US: add `.us`
+- EU: add `.eu`, `.de`, `.fr`, `.it`, `.es`, `.nl`
+- UK: add `.co.uk`
+- Global: add relevant local TLDs based on user's primary markets
+
+The scripts handle compound ccTLDs (`.com.br`, `.co.uk`, `.com.au`, etc.) and RDAP-only TLDs (`.dev`, `.app`, `.land`) automatically. Ask user if additional TLDs should be checked.
+
+**Execution:**
+```bash
+echo '{"domains": ["name1.com", "name1.io", ...], "delay_seconds": N}' | python3 ${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/scripts/whois-check.py
+```
+
+Parse JSON output. Each result includes a `method` field ("rdap", "whois", "system-whois", or "none") and a `manual_url` for any domain that couldn't be determined. If exit code 1 (RDAP rate limit circuit breaker): read partial results, report what was checked, offer manual URLs for unchecked domains.
+
+### 4b — Trademark Screening
+
+Load trademark database reference:
+> Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/trademark-databases.md`
+
+**Tier 1 (automated):** Use websearch for `"[name]" trademark [industry]` and `"[name]" registered trademark` for each finalist.
+
+**Tier 2 (guided):** Based on the target market, generate direct search URLs from the trademark database reference. Present URLs as a clickable checklist for the user to verify manually.
+
+**Always include:** "This is a preliminary screening. Consult a trademark attorney before committing to a brand name."
+
+### 4c — Linguistic Screening
+
+Invoke the `arn-spark-brand-strategist` agent in `linguistic-screening` mode via the Task tool, passing the model from `.arness/agent-models/spark.md` as the `model` parameter (see `plugins/arn-spark/skills/arn-spark-ensure-config/references/ensure-config.md` "Dispatch convention" for fallback). Context: finalist names, target market, relevant languages (mapped from target market per the agent's language mapping).
+
+The agent checks each name for: negative meanings, phonetic conflicts, cultural associations, and slang issues. Uses websearch for verification of uncertain findings.
+
+### 4d — Social Media Handle Check
+
+Use websearch for each finalist: `"[name]" @[name] site:twitter.com OR site:x.com OR site:instagram.com OR site:github.com`
+
+Report availability: available, taken, or unknown for each platform.
+
+---
+
+## Final Output
+
+### Update naming brief
+
+Update `<vision-dir>/naming-brief.md` with:
+- Due Diligence section (domain matrix, trademark results, linguistic results, social handles)
+- Final Decision section (chosen name, rationale, runner-ups)
+
+### Write naming report
+
+Load the report template:
+> Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-spark-naming/references/naming-report-template.md`
+
+Write `<reports-dir>/naming-report.md` with all sections populated.
+
+### Update product concept (conditional)
+
+**Only if `<vision-dir>/product-concept.md` exists:**
+
+Present the proposed change: adding the brand name to the product concept's Vision section.
+
+Ask the user:
+
+**"Update the product concept with the chosen brand name?"**
+1. **Yes, update it** — Add brand name to the Vision section of product-concept.md
+2. **No, keep as-is** — Product concept remains unchanged
+
+If Yes: read product-concept.md, add `**Brand name:** [chosen name]` to the Vision section, update the document title if it contains a placeholder. Write back.
+
+### Summary
+
+Present to the user:
+- Chosen brand name
+- Naming brief location: `<vision-dir>/naming-brief.md`
+- Naming report location: `<reports-dir>/naming-report.md`
+- Product concept updated: yes / no
+- Any due diligence gaps to address (unchecked domains, trademark databases to verify manually)
+- Runner-up names for reference
+
+---
+
+## Agent Invocation Map
+
+| Step | Agent | Mode | Purpose |
+|------|-------|------|---------|
+| 1 | `arn-spark-brand-strategist` | brand-dna | Analyze brand personality, audience, competitors, recommend categories |
+| 2 (each round) | `arn-spark-brand-strategist` | generation | Generate 50-80 candidates per category per round |
+| 3 | `arn-spark-brand-strategist` | scoring | Filter and score candidates on Six Senses framework |
+| 4c | `arn-spark-brand-strategist` | linguistic-screening | Check finalists in target languages |
+| 4a | Direct (Bash) | scripts | Run WHOIS availability check |
+| 4b, 4d | Direct (websearch) | — | Trademark and social media screening |
+
+## Error Handling
+
+- **WHOIS script fails:** Read partial JSON results. Report checked vs. unchecked domains. Offer manual fallback: `https://www.whois.com/whois/[domain]`
+- **Neither Python nor Node.js available:** Skip automated WHOIS entirely. Present manual check URLs.
+- **websearch fails during trademark screening:** Note the gap. Present trademark database URLs for manual verification.
+- **User cancels mid-process:** Save current progress to naming-brief.md (incomplete sections marked "-- Pending --"). Resumable via Step 0.
+- **Product concept update fails:** Print the proposed change in conversation for manual application.
+- **Agent returns insufficient candidates:** Retry with adjusted prompt (broader techniques, relaxed constraints). If still insufficient, present what was generated and ask user whether to continue or adjust direction.
+
+## Constraints
+
+- Product-concept.md updates are NET-NEW information (brand name addition), not stress-test-driven modifications. This does not conflict with the concept-review exclusivity rule (from `arn-spark-concept-review`, which restricts stress-test-recommendation consolidation to that skill alone).
+- User approval gate is MANDATORY before writing to product-concept.md.
+- All reference/script paths use `${CLAUDE_PLUGIN_ROOT}`.
+- WHOIS queries use a circuit breaker — any error stops all remaining queries immediately to protect the user's IP.
+- The naming brief overwrites on re-run (git provides history). The user is warned and offered resume/start-fresh in Step 0.

package/plugins/arn-spark/skills/arn-spark-naming/references/creative-brief-template.md

@@ -0,0 +1,146 @@
+# [Product Name] — Naming Brief
+
+> **Instructions:** Every section below MUST appear in the final document. Replace all bracketed placeholders with actual content. Sections that have not yet been completed during a partial run should contain "-- Pending --" to indicate they are awaiting completion.
+
+## Context
+
+- **Product vision:** [1-2 sentence vision statement from product concept or user description]
+- **Value proposition:** [The one thing this product does better than anyone else]
+- **Target audience:** [Primary audience description — who they are, what they care about]
+- **Target market:** [Country/region for trademark and linguistic screening]
+- **Industry/domain:** [The product's industry category]
+
+## Brand DNA
+
+### Brand Personality Profile
+
+[2-3 sentences describing the brand archetype and personality traits. Examples: "The Reliable Expert — trustworthy, knowledgeable, no-nonsense" or "The Rebellious Newcomer — bold, unconventional, challenging the status quo."]
+
+### Target Audience Vocabulary
+
+[Key words and phrases the target audience uses in their domain. Communication style: formal/casual, technical/plain, aspirational/practical.]
+
+### Competitor Name Landscape
+
+| Competitor | Name Type | Observations |
+|-----------|-----------|--------------|
+| [Name 1] | [Descriptive/Evocative/Invented/Lexical] | [What the name communicates] |
+| [Name 2] | [Type] | [Observations] |
+| [Name 3] | [Type] | [Observations] |
+
+**Pattern analysis:** [Summary of naming patterns in the space. Are most names descriptive? Is there whitespace in evocative or invented names?]
+
+### Naming Categories Selected
+
+[Category 1] — [Rationale for selection]
+[Category 2 if applicable] — [Rationale for selection]
+
+### User Seeds
+
+- **Words loved:** [List of words the user likes]
+- **Words hated:** [List of words the user dislikes]
+- **Existing name ideas:** [Any names the user has already considered]
+- **Themes to explore:** [Specific themes or directions the user wants to pursue]
+- **Themes to avoid:** [Directions the user wants to avoid]
+
+---
+
+## Creative Sprint Results
+
+### Generation Statistics
+
+| Category | Round 1 (Seeds) | Round 2 (Sprint) | Round 3 (Mashup) | Total |
+|----------|----------------|-------------------|-------------------|-------|
+| [Category 1] | [N] | [N] | [N] | [N] |
+| [Category 2] | [N] | [N] | [N] | [N] |
+| **Total** | **[N]** | **[N]** | **[N]** | **[N]** |
+
+### Candidates by Category
+
+#### [Category 1]: [Category Name]
+
+[Numbered list of all candidates in this category]
+
+#### [Category 2]: [Category Name]
+
+[Numbered list of all candidates in this category]
+
+### User-Starred Favorites
+
+[List of names the user marked as favorites during the collaboration checkpoint]
+
+### Dead Directions
+
+[Directions or themes the user flagged as undesirable, with reason if provided]
+
+---
+
+## Qualitative Filter Results
+
+### Pass 1 Shortlist (30-40 candidates)
+
+[Numbered list of candidates that survived the initial filter, with brief reason each was kept]
+
+### Six Senses Scored Table
+
+| Rank | Name | Appearance | Sound | Meaning | Memorability | Function | Scalability | Total |
+|------|------|-----------|-------|---------|-------------|----------|-------------|-------|
+| 1 | [name] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [6-30] |
+| 2 | [name] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [1-5] | [6-30] |
+| ... | | | | | | | | |
+
+### Finalists Selected for Due Diligence
+
+[List of 5-8 names selected by the user, with any notes on why they were chosen]
+
+---
+
+## Due Diligence
+
+### Domain Availability
+
+| Name | .com | .io | .co | .dev | .app | .ai | Notes |
+|------|------|-----|-----|------|------|-----|-------|
+| [name] | [Available/Taken/Error] | ... | ... | ... | ... | ... | |
+
+**Check method:** [RDAP (primary) / WHOIS port-43 (fallback) / System whois / Manual]
+**Date checked:** [ISO 8601]
+
+### Trademark Screening
+
+| Name | websearch Result | Risk Level | Database URLs Provided | Notes |
+|------|-----------------|-----------|----------------------|-------|
+| [name] | [Summary of search findings] | [Clear/Caution/Conflict] | [Yes/No] | |
+
+**Databases checked:** [List of trademark databases]
+**Disclaimer:** This is a preliminary screening. Consult a trademark attorney before committing to a brand name.
+
+### Linguistic Screening
+
+| Name | Languages Checked | Issues Found | Notes |
+|------|------------------|-------------|-------|
+| [name] | [Language list] | [None / Issue description] | |
+
+### Social Media Handles
+
+| Name | X / Twitter | Instagram | GitHub | Notes |
+|------|-----------|-----------|--------|-------|
+| [name] | [Available/Taken] | [Available/Taken] | [Available/Taken] | |
+
+---
+
+## Final Decision
+
+### Chosen Name
+
+**[Name]**
+
+### Rationale
+
+[2-3 sentences explaining why this name was selected — reference Six Senses scores, due diligence results, and alignment with brand DNA.]
+
+### Runner-Ups (Ordered)
+
+1. **[Name]** — [Brief reason it was not chosen, but remains a strong alternative]
+2. **[Name]** — [Brief reason]
+3. **[Name]** — [Brief reason]