Name: DSP-04-Choose_Target_AI_IDE
Author: FeatureFactory-io

Prompt file imported from FeatureFactory-io/mimir (.windsurf/workflows/Edda/DSP/DSP-04-Choose_Target_AI_IDE.md). Copyright stays with the author.

Activity: Choose Target AI IDE

Activity ID: 63 Order: 4 Phase: Elaboration Dependencies: Predecessor: Activity 62 (Verify Architecture & Code Organization)

Description

Choose Target AI IDE

Guidance

Choose Target AI IDE

Objective

Ask the user which AI-assisted IDE they will use for development, then record the choice to determine the output format for DSP-05 (Generate AI IDE Configuration).

Process

1. Present Options

Ask the user to choose their primary AI IDE:

Target	Output File(s)	Format
Claude Code	`CLAUDE.md` at project root	Single Markdown file with all context
GitHub Copilot	`.github/copilot-instructions.md`	Single Markdown file in `.github/`
Windsurf	`.windsurf/rules/*.md` files	Multiple rule files + workflow references
Cursor	`.cursor/rules/*.mdc` files	Multiple rule files in MDC format

2. Clarify Multi-IDE Usage

If the user works with multiple IDEs (e.g., Windsurf for daily work + Claude Code for complex tasks):

Generate configs for all selected targets
Ensure consistency across configs (same conventions, same references)
Note: Windsurf and Cursor share the same workflow/rule structure but use different directories

3. Record Choice

Document the selected target(s) for DSP-05:

Target AI IDE Selection:
  Primary:   Windsurf
  Secondary: Claude Code
  
  Output files to generate:
    1. .windsurf/rules/ (multiple .md files)
    2. CLAUDE.md (single file)

4. Confirm Output Structure

Explain to the user what will be generated:

For Claude Code / GitHub Copilot (single file):

One comprehensive Markdown file covering:
- Project overview and architecture
- Directory layout and docs map
- Available workflows, skills, and artifact templates
- AI/human collaboration patterns and quality gates
- Coding conventions and testing discipline
- How to build features (BPE workflow reference)
- How to run locally

For Windsurf / Cursor (multiple files):

The project already uses .windsurf/rules/ and .windsurf/workflows/ — these ARE the config
DSP-05 will audit and supplement existing rules to ensure completeness
A summary _ai-context.md rule file will be generated pointing to all docs, workflows, skills, and templates
Existing rules will NOT be overwritten

Deliverables

✅ Target AI IDE selected (one or more)
✅ Output format understood by user
✅ Ready to proceed to DSP-05 (Generate AI IDE Configuration)

Agent

None

Skill

None

Rules

None

Artifacts Produced

None

Artifacts Consumed

None

Notes

No additional notes.

Install DSP-04-Choose_Target_AI_IDE and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

# Activity: Choose Target AI IDE **Activity ID**: 63 **Order**: 4 **Phase**: Elaboration **Dependencies**: Predecessor: Activity 62 (Verify Architecture & Code Organization) ## Description Choose Target AI IDE ## Guidance # Choose Target AI IDE ## Objective Ask the user which AI-assisted IDE they will use for development, then record the choice to determine the output format for DSP-05 (Generate AI IDE Configuration). --- ## Process ### 1. Present Options Ask the user to choose their primary AI IDE: | Target | Output File(s) | Format | |--------|----------------|--------| | **Claude Code** | `CLAUDE.md` at project root | Single Markdown file with all context | | **GitHub Copilot** | `.github/copilot-instructions.md` | Single Markdown file in `.github/` | | **Windsurf** | `.windsurf/rules/*.md` files | Multiple rule files + workflow references | | **Cursor** | `.cursor/rules/*.mdc` files | Multiple rule files in MDC format | ### 2. Clarify Multi-IDE Usage If the user works with multiple IDEs (e.g., Windsurf for daily work + Claude Code for complex tasks): - Generate configs for **all selected targets** - Ensure consistency across configs (same conventions, same references) - Note: Windsurf and Cursor share the same workflow/rule structure but use different directories ### 3. Record Choice Document the selected target(s) for DSP-05: ``` Target AI IDE Selection: Primary: Windsurf Secondary: Claude Code Output files to generate: 1. .windsurf/rules/ (multiple .md files) 2. CLAUDE.md (single file) ``` ### 4. Confirm Output Structure Explain to the user what will be generated: **For Claude Code / GitHub Copilot** (single file): - One comprehensive Markdown file covering: - Project overview and architecture - Directory layout and docs map - Available workflows, skills, and artifact templates - AI/human collaboration patterns and quality gates - Coding conventions and testing discipline - How to build features (BPE workflow reference) - How to run locally **For Windsurf / Cursor** (multiple files): - The project already uses `.windsurf/rules/` and `.windsurf/workflows/` — these ARE the config - DSP-05 will audit and supplement existing rules to ensure completeness - A summary `_ai-context.md` rule file will be generated pointing to all docs, workflows, skills, and templates - Existing rules will NOT be overwritten --- ## Deliverables - ✅ **Target AI IDE** selected (one or more) - ✅ **Output format** understood by user - ✅ **Ready to proceed** to DSP-05 (Generate AI IDE Configuration) ## Agent None ## Skill None ## Rules None ## Artifacts Produced None ## Artifacts Consumed None ## Notes No additional notes.

{ "prompt": "# Activity: Choose Target AI IDE\n\n**Activity ID**: 63\n**Order**: 4\n**Phase**: Elaboration\n**Dependencies**: Predecessor: Activity 62 (Verify Architecture & Code Organization)\n\n## Description\n\nChoose Target AI IDE\n\n## Guidance\n\n# Choose Target AI IDE\n\n## Objective\n\nAsk the user which AI-assisted IDE they will use for development, then record the choice to determine the output format for DSP-05 (Generate AI IDE Configuration).\n\n---\n\n## Process\n\n### 1. Present Options\n\nAsk the user to choose their primary AI IDE:\n\n| Target | Output File(s) | Format |\n|--------|----------------|--------|\n| **Claude Code** | `CLAUDE.md` at project root | Single Markdown file with all context |\n| **GitHub Copilot** | `.github/copilot-instructions.md` | Single Markdown file in `.github/` |\n| **Windsurf** | `.windsurf/rules/*.md` files | Multiple rule files + workflow references |\n| **Cursor** | `.cursor/rules/*.mdc` files | Multiple rule files in MDC format |\n\n### 2. Clarify Multi-IDE Usage\n\nIf the user works with multiple IDEs (e.g., Windsurf for daily work + Claude Code for complex tasks):\n\n- Generate configs for **all selected targets**\n- Ensure consistency across configs (same conventions, same references)\n- Note: Windsurf and Cursor share the same workflow/rule structure but use different directories\n\n### 3. Record Choice\n\nDocument the selected target(s) for DSP-05:\n\n```\nTarget AI IDE Selection:\n Primary: Windsurf\n Secondary: Claude Code\n \n Output files to generate:\n 1. .windsurf/rules/ (multiple .md files)\n 2. CLAUDE.md (single file)\n```\n\n### 4. Confirm Output Structure\n\nExplain to the user what will be generated:\n\n**For Claude Code / GitHub Copilot** (single file):\n- One comprehensive Markdown file covering:\n - Project overview and architecture\n - Directory layout and docs map\n - Available workflows, skills, and artifact templates\n - AI/human collaboration patterns and quality gates\n - Coding conventions and testing discipline\n - How to build features (BPE workflow reference)\n - How to run locally\n\n**For Windsurf / Cursor** (multiple files):\n- The project already uses `.windsurf/rules/` and `.windsurf/workflows/` — these ARE the config\n- DSP-05 will audit and supplement existing rules to ensure completeness\n- A summary `_ai-context.md` rule file will be generated pointing to all docs, workflows, skills, and templates\n- Existing rules will NOT be overwritten\n\n---\n\n## Deliverables\n\n- ✅ **Target AI IDE** selected (one or more)\n- ✅ **Output format** understood by user\n- ✅ **Ready to proceed** to DSP-05 (Generate AI IDE Configuration)\n\n## Agent\n\nNone\n\n## Skill\n\nNone\n\n## Rules\n\nNone\n\n## Artifacts Produced\n\nNone\n\n## Artifacts Consumed\n\nNone\n\n## Notes\n\nNo additional notes.", "variables": [], "notes": "Choose Target AI IDE", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/FeatureFactory-io/mimir", "path": ".windsurf/workflows/Edda/DSP/DSP-04-Choose_Target_AI_IDE.md", "ref": "850a123927f83a3ed209f39a5a3590bfe21aeb92", "url": "https://github.com/FeatureFactory-io/mimir/blob/850a123927f83a3ed209f39a5a3590bfe21aeb92/.windsurf/workflows/Edda/DSP/DSP-04-Choose_Target_AI_IDE.md", "key": "FeatureFactory-io/mimir/.windsurf/workflows/Edda/DSP/DSP-04-Choose_Target_AI_IDE.md" } } }

DSP-04-Choose_Target_AI_IDE

About

Activity: Choose Target AI IDE

Description

Guidance

Choose Target AI IDE

Objective

Process

1. Present Options

2. Clarify Multi-IDE Usage

3. Record Choice

4. Confirm Output Structure

Deliverables

Agent

Skill

Rules

Artifacts Produced

Artifacts Consumed

Notes

Install DSP-04-Choose_Target_AI_IDE and it becomes one more candidate the router can pick - when it fits.

Use it

Manifest

Reviews