Generate AI IDE Configuration
DSP-5 Order: #5 Elaboration Has Dependencies
Updated 4 weeks, 2 days ago
Guidance
Generate AI IDE Configuration
Objective
Assemble a comprehensive configuration file for the chosen AI IDE target, pulling from SAO.md, ESM artifacts, available workflows, skills, artifact templates, and coding conventions. The output file gives the AI agent everything it needs to understand the project and start building features.
Process
1. Gather Inputs
Collect all source material identified in DSP-01 through DSP-03:
| Source | What to Extract | Config Section |
|---|---|---|
docs/architecture/SAO.md |
Executive summary, architecture, design principles, tech stack, directory layout | Sections 1-3 |
docs/features/user_journey.md |
Acts, user journey overview | Section 4 (Docs Map) |
docs/features/act-*/ |
Feature file inventory | Section 4 (Docs Map) |
docs/ux/IA_guidelines.md |
UI patterns, design system | Section 4 (Docs Map) |
.windsurf/workflows/*/ |
Workflow names, descriptions, activity counts | Section 5 (Workflows) |
.windsurf/workflows/*/skills/ |
Skill titles, capability domains, tech stacks | Section 6 (Skills) |
.windsurf/workflows/*/artifacts/ |
Template file names and descriptions | Section 7 (Artifact Templates) |
.windsurf/rules/*.md |
Coding conventions, testing discipline, commit format | Section 9 (Conventions) |
2. Assemble Config File
Use the appropriate template from DSP/artifacts/ based on the target chosen in DSP-04.
The config file MUST contain these sections (section numbers vary by template):
Section: What Is {ProjectName}
Extract from SAO.md Executive Summary. One paragraph explaining what the project does and its key innovation.
Section: Architecture
Extract from SAO.md:
- High-level component diagram (ASCII or Mermaid)
- Directory layout (from Project Structure section)
- Data model hierarchy
- Key design decisions (top 3-5)
Section: Documentation Map
Point to all key docs with brief descriptions:
| What | Where | When to Read |
|------|-------|--------------|
| System architecture | `docs/architecture/SAO.md` | Before big changes |
| User journey / all Acts | `docs/features/user_journey.md` | Feature planning |
| Feature specs (BDD) | `docs/features/act-*/` | Before implementing any feature |
| UI patterns & IA | `docs/ux/IA_guidelines.md` | Before building UI |
| Development rules | `.windsurf/rules/*.md` | Always active |
| Process workflows | `.windsurf/workflows/*/` | When running a workflow |
| Agent reference architecture | Playbook artifact 56 | When SAO §17 applies |
| Test architecture (TFK-01) | `docs/architecture/test-architecture.md` | Agent test lanes, CI gates |
When SAO §17 applies, add agent-lane rows to the docs map:
| Agent integration proofs (PRF-*) | skill *Agent Integration Proof Patterns* | Before agent slices |
| Agent task eval (TASK-*) | skill *Agent Task Eval* | Promotion / nightly only |
| assert_agent_story helper | `tests/support/agent_story.py` | TFK-02 bootstrap |
Section: Available Workflows
List each workflow with its purpose, activity count, and when to use it:
| Workflow | Purpose | Activities | When to Use |
|----------|---------|------------|-------------|
| ESM | Envision the System | 7 | Defining what to build |
| DTA | Define Architecture | 18 | Making architectural decisions |
| DSP | Deploy Software Process | 6 | Setting up AI IDE |
| BSP | Bootstrap Project | 8 | Scaffolding new project |
| BPE | Build Feature | N | **Primary workflow for feature delivery** |
| EST | Estimate the Project | 8 | Estimation and planning |
Section: Available Skills
List skills found in workflow skills/ directories:
| Skill | Capability Domain | Tech Stack | Location |
|-------|-------------------|------------|----------|
| {SkillTitle} | {Domain} | {Stack} | `.windsurf/workflows/{WF}/skills/{file}` |
When SAO §17 applies, ensure these agent-test skills appear in the inventory (link from playbook, do not duplicate bodies):
| Agent Integration Proof Patterns | TEST_INTEGRATION | pytest, CAP-004, artifact-56 | playbook skill |
| Agent Task Eval | TEST_INTEGRATION | golden-tasks, live LLM | playbook skill |
| Pytest Log Story Assertions | LOG_STORY_TESTING | pytest caplog | playbook skill |
| Test Trophy Architecture | TEST_STRATEGY | pytest+behave | playbook skill |
| pytest Runner Configuration | TEST_FRAMEWORK | pytest markers | playbook skill |
If no skills exist yet, note: "No skills defined yet. Skills provide technology-specific implementation guidance for workflow activities."
Section: Artifact Templates
List templates found in workflow artifacts/ directories:
| Template | Workflow | Purpose | Location |
|----------|----------|---------|----------|
| User Journey Template | ESM | Structure for user journey doc | `ESM/artifacts/user_journey_template.md` |
| IA Guidelines Template | ESM | Design system & UI patterns spec | `ESM/artifacts/ia_guidelines_template.md` |
| Feature File Template | ESM | BDD scenario format | `ESM/artifacts/feature_file_template.feature` |
| SAO Template | DTA | Architecture document structure | `DTA/artifacts/sao_document_template.md` |
| CLAUDE.md Template | DSP | AI config for Claude Code | `DSP/artifacts/claude_md_template.md` |
| Copilot Instructions Template | DSP | AI config for GitHub Copilot | `DSP/artifacts/copilot_instructions_template.md` |
| Windsurf/Cursor Rules Template | DSP | AI config for Windsurf/Cursor | `DSP/artifacts/windsurf_cursor_rules_template.md` |
| Makefile Template | BSP | Project orchestration Makefile | `BSP/artifacts/makefile_template.mk` |
| Helm Chart Template | DCD | K8s Helm chart structure | `DCD/artifacts/` (reference structure) |
| Infra Repo Scaffold | DCI | CDK infra repo structure | `DCI/artifacts/` (reference structure) |
| Implementation Plan Template | BPE | Feature implementation plan | `BPE/artifacts/implementation_plan_template.md` |
| Definition of Done Checklist Template | BPE | DoD checklist for feature sign-off | `BPE/artifacts/definition_of_done_checklist_template.md` |
| AI Agent Reference Architecture | DTA | CAP-*, PRF-*, TASK-* catalogs | `DTA/artifacts/` artifact 56 |
Section: AI/Human Collaboration Patterns
Absorbed from the former DSP-05 content. Include:
AI Agent Responsibilities:
- Code generation following established patterns
- Test implementation (unit, integration, e2e)
- Documentation generation (docstrings, README updates)
- Refactoring within architectural boundaries
Human Developer Responsibilities:
- Architectural decisions and boundary setting
- Code review and quality validation
- Security-sensitive implementations
- Production deployment decisions
Quality Gates for AI-Generated Code:
1. All tests pass (unit, integration, linting)
2. Code coverage meets project threshold
3. Documentation generated for public APIs
4. Code follows established patterns from SAO.md
5. Human review and approval before merge
Escalation Rules:
- Ambiguous requirements → ask human
- Architectural decisions outside patterns → ask human
- Security-sensitive code → flag for human review
Section: Coding Conventions
Extract from .windsurf/rules/ or document directly:
- Commit format (Angular convention)
- Method size limits (20-30 lines max for public methods)
- Import organization (module-level only)
- Logging standards (INFO level, what/why/where/when)
- Testing discipline (test-first, pytest, no mocks in integration tests except CAP-004 ScriptedLLM in @agent_proof tests)
When SAO §17 applies, append agent test lane conventions:
### Agent test lanes (SAO §17)
| Lane | Gate | Command | Rule / skill |
|------|------|---------|--------------|
| 1 Control-plane proofs | PR when AGENTS_ENABLED | `make test-agent-proof` | `do-assert-agent-story`, *Agent Integration Proof Patterns* |
| 2 Deterministic shell | PR integration | normal `make test` | no LLM mock |
| 3 Live contract eval | Nightly / CD optional | `agent-eval.yml` | temp=0 contracts |
| 4 Task performance | Promotion | `make test-agent-quality` | *Agent Task Eval*, not PR merge |
- Behave AT proves user-visible behavior; `@pytest.mark.agent_proof` proves PRF orchestration — do not merge them.
- Ban FakeLLM and silent queue exhaustion — CAP-004 ScriptedLLM only (`do-not-mock-in-integration-tests`).
- Plan slices declare Agent Proof Table (BPE-01 Section G); MIN manifest may set `checkpoint.agent_proof_command`.
Section: Development Workflow (How to Build Features)
Reference the BPE workflow with a condensed summary:
1. Read the feature spec in docs/features/act-*/
2. Read SAO.md for architectural context
3. Backend: models → services → views
4. Frontend: templates + interactions
5. Tests: write before implementation, 100% pass rate required
6. When SAO §17: behavior + log story + agent proof green in same slice
7. PR with all changes
Section: Running Locally
Extract from SAO.md or document:
- Setup commands (venv, install, migrate)
- Start dev server
- Run tests
- Load demo data
When SAO §17 applies, append agent test commands:
make test-agent-proof # lane 1 PRF proofs (no-op when AGENTS_ENABLED unset)
make test-agent-quality # lane 4 TASK-* eval (nightly / manual)
pytest -m agent_proof tests/integration/agent/ -x
3. Customize for Target Format
Claude Code (CLAUDE.md):
- Single file, flat Markdown sections with --- separators
- Use ## for main sections
- Keep under ~500 lines (Claude Code reads this on every conversation)
GitHub Copilot (.github/copilot-instructions.md):
- Single file, similar to CLAUDE.md but may use different heading conventions
- Focus on coding patterns and conventions (Copilot is code-completion oriented)
Windsurf (.windsurf/rules/_ai-context.md):
- Create a summary context rule that points to existing rules and workflows
- Do NOT duplicate content already in .windsurf/rules/*.md
- Focus on the docs map, workflow inventory, and skills inventory
- Add conditional trigger: "When starting a new conversation or task"
Cursor (.cursor/rules/_ai-context.mdc):
- Similar to Windsurf but uses MDC format with YAML frontmatter
- Mirror the Windsurf content adapted to Cursor conventions
4. Present to User
Show the generated config file to the user before writing it:
- Highlight any sections that are thin or missing source material
- Ask if any project-specific conventions should be added
- Confirm file location is correct
Deliverables
- ✅ AI IDE config file generated for chosen target(s)
- ✅ All 10 sections populated from source material
- ✅ Agent test lanes + skills inventoried when SAO §17 applies
- ✅ User reviewed the generated content
- ✅ Ready to proceed to DSP-06 (Review & Commit)
Artifacts Produced
None
Artifacts Consumed
ESM Templates (inventoried for Section 7 — Artifact Templates):
- User Journey Template (ESM/artifacts/user_journey_template.md)
- IA Guidelines Template (ESM/artifacts/ia_guidelines_template.md)
- Feature File Template (ESM/artifacts/feature_file_template.feature)
DTA Templates:
- System Architecture Overview Template (DTA/artifacts/sao_document_template.md)
DSP Templates (used to generate the output config file in step 2):
- CLAUDE.md Template (DSP/artifacts/claude_md_template.md)
- Copilot Instructions Template (DSP/artifacts/copilot_instructions_template.md)
- Windsurf/Cursor Rules Template (DSP/artifacts/windsurf_cursor_rules_template.md)
BSP Templates (inventoried for Section 7):
- Makefile Template (BSP/artifacts/makefile_template.mk)
DCD Templates (inventoried for Section 7):
- Helm Chart Template (DCD/artifacts/ — reference structure)
BPE Templates (inventoried for Section 7):
- Implementation Plan Template (BPE/artifacts/implementation_plan_template.md)
- Definition of Done Checklist Template (BPE/artifacts/definition_of_done_checklist_template.md)
DCI Templates (inventoried for Section 7):
- Infra Repo Scaffold (DCI/artifacts/ — reference structure)
Notes
No additional notes.
Details
- Order:
- #5
- Phase:
- Predecessor:
- DSP-4 Choose Target AI IDE
- Created:
- Apr 12, 2026
- Last Updated:
- Aug 21, 2026
Workflow
Deploy Software Process
Check prerequisite artifacts (ESM, DTA), choose target AI IDE, and generate configuration (CLAUDE.md / copilot-instructions.md / Windsurf/Cursor rules) so AI …
View WorkflowAssigned Agent
No agent assigned
Required Skills
No skills linked
Rules
No rules linked.
Input Artifacts 8
-
Feature File Template (Gherkin)
Template
Required
Produced by: Write Feature Files -
Helm Chart Template
Template
Required
Produced by: Create Helm Chart & Values -
IA Guidelines Template
Template
Required
Produced by: Define Information Architecture -
Implementation Plan Template
Document
Required
Produced by: Plan Feature -
Infra Repo Scaffold
Template
Required
Produced by: Scaffold Infra Repo & CDK Project -
Makefile Template
Document
Required
Produced by: Create Makefile -
System Architecture Overview Template
Document
Required
Produced by: Write SAO.md -
User Journey Template
Template
Required
Produced by: Define User Journey
Output Artifacts 4
- CLAUDE.md Template Template Required
- Copilot Instructions Template Template
- Definition of Done Checklist Template Document
- Windsurf/Cursor Rules Template Template