Prompt file imported from PauloHYBEX/Nexus-TCMS (.windsurf/workflows/templates/research-project/STACK.md). Copyright stays with the author.

Stack Research Template

Name: STACK
Author: PauloHYBEX

Template for .planning/research/STACK.md — recommended technologies for the project domain.

# Stack Research

**Domain:** [domain type]
**Researched:** [date]
**Confidence:** [HIGH/MEDIUM/LOW]

## Recommended Stack

### Core Technologies

| Technology | Version | Purpose | Why Recommended |
|------------|---------|---------|-----------------|
| [name] | [version] | [what it does] | [why experts use it for this domain] |
| [name] | [version] | [what it does] | [why experts use it for this domain] |
| [name] | [version] | [what it does] | [why experts use it for this domain] |

### Supporting Libraries

| Library | Version | Purpose | When to Use |
|---------|---------|---------|-------------|
| [name] | [version] | [what it does] | [specific use case] |
| [name] | [version] | [what it does] | [specific use case] |

### Development Tools

| Tool | Purpose | Notes |
|------|---------|-------|
| [name] | [what it does] | [configuration tips] |
| [name] | [what it does] | [configuration tips] |

## Alternatives Considered

| Recommended | Alternative | When to Use Alternative |
|-------------|-------------|-------------------------|
| [our choice] | [other option] | [conditions where alternative is better] |
| [our choice] | [other option] | [conditions where alternative is better] |

## What NOT to Use

| Avoid | Why | Use Instead |
|-------|-----|-------------|
| [technology] | [specific problem] | [recommended alternative] |
| [technology] | [specific problem] | [recommended alternative] |

## Versions

### Version Compatibility

| Package A | Compatible With | Notes |
|-----------|-----------------|-------|
| [package@version] | [package@version] | [compatibility notes] |

### Installation

```bash
# Core
[package manager] install [packages]

# Supporting
[package manager] install [packages]

# Dev dependencies
[package manager] install -D [packages]

Stack research for: [domain] Researched: [date]


</template>

<guidelines>

**Core Technologies:**
- Include specific version numbers — not just "React" but "React 19.x"
- Explain why this is the standard choice, not just what it does
- Focus on technologies that affect architecture decisions

**Supporting Libraries:**
- Include libraries commonly needed for this domain
- Note when each is needed (not all projects need all libraries)

**Alternatives:**
- Don't just dismiss alternatives — explain when they make sense
- Helps the user make informed decisions if they disagree with recommendations

**What NOT to Use:**
- Actively warn against outdated or problematic choices
- Explain the specific problem, not just "it's old"
- Always provide the recommended alternative

**Versions:**
- Note any known compatibility issues between packages
- Critical for avoiding debugging time later
- Include installation commands so the planner can reference them

</guidelines>

# Stack Research Template Template for `.planning/research/STACK.md` — recommended technologies for the project domain. <template> ```markdown # Stack Research **Domain:** [domain type] **Researched:** [date] **Confidence:** [HIGH/MEDIUM/LOW] ## Recommended Stack ### Core Technologies | Technology | Version | Purpose | Why Recommended | |------------|---------|---------|-----------------| | [name] | [version] | [what it does] | [why experts use it for this domain] | | [name] | [version] | [what it does] | [why experts use it for this domain] | | [name] | [version] | [what it does] | [why experts use it for this domain] | ### Supporting Libraries | Library | Version | Purpose | When to Use | |---------|---------|---------|-------------| | [name] | [version] | [what it does] | [specific use case] | | [name] | [version] | [what it does] | [specific use case] | ### Development Tools | Tool | Purpose | Notes | |------|---------|-------| | [name] | [what it does] | [configuration tips] | | [name] | [what it does] | [configuration tips] | ## Alternatives Considered | Recommended | Alternative | When to Use Alternative | |-------------|-------------|-------------------------| | [our choice] | [other option] | [conditions where alternative is better] | | [our choice] | [other option] | [conditions where alternative is better] | ## What NOT to Use | Avoid | Why | Use Instead | |-------|-----|-------------| | [technology] | [specific problem] | [recommended alternative] | | [technology] | [specific problem] | [recommended alternative] | ## Versions ### Version Compatibility | Package A | Compatible With | Notes | |-----------|-----------------|-------| | [package@version] | [package@version] | [compatibility notes] | ### Installation ```bash # Core [package manager] install [packages] # Supporting [package manager] install [packages] # Dev dependencies [package manager] install -D [packages] ``` --- *Stack research for: [domain]* *Researched: [date]* ``` </template> <guidelines> **Core Technologies:** - Include specific version numbers — not just "React" but "React 19.x" - Explain why this is the standard choice, not just what it does - Focus on technologies that affect architecture decisions **Supporting Libraries:** - Include libraries commonly needed for this domain - Note when each is needed (not all projects need all libraries) **Alternatives:** - Don't just dismiss alternatives — explain when they make sense - Helps the user make informed decisions if they disagree with recommendations **What NOT to Use:** - Actively warn against outdated or problematic choices - Explain the specific problem, not just "it's old" - Always provide the recommended alternative **Versions:** - Note any known compatibility issues between packages - Critical for avoiding debugging time later - Include installation commands so the planner can reference them </guidelines>

{ "prompt": "# Stack Research Template\n\nTemplate for `.planning/research/STACK.md` — recommended technologies for the project domain.\n\n<template>\n\n```markdown\n# Stack Research\n\n**Domain:** [domain type]\n**Researched:** [date]\n**Confidence:** [HIGH/MEDIUM/LOW]\n\n## Recommended Stack\n\n### Core Technologies\n\n| Technology | Version | Purpose | Why Recommended |\n|------------|---------|---------|-----------------|\n| [name] | [version] | [what it does] | [why experts use it for this domain] |\n| [name] | [version] | [what it does] | [why experts use it for this domain] |\n| [name] | [version] | [what it does] | [why experts use it for this domain] |\n\n### Supporting Libraries\n\n| Library | Version | Purpose | When to Use |\n|---------|---------|---------|-------------|\n| [name] | [version] | [what it does] | [specific use case] |\n| [name] | [version] | [what it does] | [specific use case] |\n\n### Development Tools\n\n| Tool | Purpose | Notes |\n|------|---------|-------|\n| [name] | [what it does] | [configuration tips] |\n| [name] | [what it does] | [configuration tips] |\n\n## Alternatives Considered\n\n| Recommended | Alternative | When to Use Alternative |\n|-------------|-------------|-------------------------|\n| [our choice] | [other option] | [conditions where alternative is better] |\n| [our choice] | [other option] | [conditions where alternative is better] |\n\n## What NOT to Use\n\n| Avoid | Why | Use Instead |\n|-------|-----|-------------|\n| [technology] | [specific problem] | [recommended alternative] |\n| [technology] | [specific problem] | [recommended alternative] |\n\n## Versions\n\n### Version Compatibility\n\n| Package A | Compatible With | Notes |\n|-----------|-----------------|-------|\n| [package@version] | [package@version] | [compatibility notes] |\n\n### Installation\n\n```bash\n# Core\n[package manager] install [packages]\n\n# Supporting\n[package manager] install [packages]\n\n# Dev dependencies\n[package manager] install -D [packages]\n```\n\n---\n*Stack research for: [domain]*\n*Researched: [date]*\n```\n\n</template>\n\n<guidelines>\n\n**Core Technologies:**\n- Include specific version numbers — not just \"React\" but \"React 19.x\"\n- Explain why this is the standard choice, not just what it does\n- Focus on technologies that affect architecture decisions\n\n**Supporting Libraries:**\n- Include libraries commonly needed for this domain\n- Note when each is needed (not all projects need all libraries)\n\n**Alternatives:**\n- Don't just dismiss alternatives — explain when they make sense\n- Helps the user make informed decisions if they disagree with recommendations\n\n**What NOT to Use:**\n- Actively warn against outdated or problematic choices\n- Explain the specific problem, not just \"it's old\"\n- Always provide the recommended alternative\n\n**Versions:**\n- Note any known compatibility issues between packages\n- Critical for avoiding debugging time later\n- Include installation commands so the planner can reference them\n\n</guidelines>", "variables": [], "notes": "Template for `.planning/research/STACK.md` — recommended technologies for the project domain.", "metadata": { "source": { "provider": "github-windsurf-workflows", "repository": "https://github.com/PauloHYBEX/Nexus-TCMS", "path": ".windsurf/workflows/templates/research-project/STACK.md", "ref": "af66d4e66d7443d045e74bafc302cd998ceb5b99", "url": "https://github.com/PauloHYBEX/Nexus-TCMS/blob/af66d4e66d7443d045e74bafc302cd998ceb5b99/.windsurf/workflows/templates/research-project/STACK.md", "key": "PauloHYBEX/Nexus-TCMS/.windsurf/workflows/templates/research-project/STACK.md" } } }

STACK

About

Stack Research Template

Use it

Manifest

Reviews