teamcraft-jcg:tech-decisions

---
name: teamcraft-jcg:tech-decisions
description: Capture the technology stack and key decisions for this project. Reads the PRD from Confluence, surfaces matching team conventions as context, and records what the team has decided to use and why. Simple format — what was decided and why, not a full ADR ceremony. Stores in Confluence.
argument-hint: "[Confluence PRD page URL or ID — optional]"
disable-model-invocation: true
user-invocable: true
allowed-tools:
  - mcp__sooperset-mcp-atlassian__confluence_search
  - mcp__sooperset-mcp-atlassian__confluence_get_page
  - mcp__sooperset-mcp-atlassian__confluence_get_page_children
  - mcp__sooperset-mcp-atlassian__confluence_create_page
  - mcp__sooperset-mcp-atlassian__confluence_update_page
---

## Hard Constraints

- Confluence is the only storage and retrieval mechanism for project documents. Never use local filesystem tools for document storage.

## Goal

Produce a clear record of what technologies this project uses and the key decisions that shaped its technical direction. Format: what was decided, why, and any caveats. This becomes the single source of truth that sprint planning and issue creation reference throughout the project.

## The Decisions Boundary

This skill captures what the team chose and why — not requirements (that is capture-requirements' domain) and not how to implement with the chosen stack (that belongs in code, comments, or the conventions knowledge base). If a conversation drifts into feature requirements or implementation how-tos, note it and redirect.

## Load Context

Load the PRD — it provides the requirements and constraints that technology decisions must satisfy. If a Confluence page URL or ID was passed as an argument, load it with `mcp__sooperset-mcp-atlassian__confluence_get_page` directly. If the page ID is in `.teamcraft/project.md`, use it directly. Otherwise, ask the user if they can point at the PRD in Confluence before searching. Only use `mcp__sooperset-mcp-atlassian__confluence_search` if they cannot point at it directly.

Also ask the user if they can point at any team convention documents in Confluence — documents that describe how this team builds software. If they can, load them with `mcp__sooperset-mcp-atlassian__confluence_get_page` using the page ID or URL. If they cannot, use `mcp__sooperset-mcp-atlassian__confluence_search` to find them — search results include the page ID, which you then pass to `mcp__sooperset-mcp-atlassian__confluence_get_page`. Convention documents might be named by team, client, technology, or practice area.

Conventions are context, not constraints — the user decides whether this project follows them. If a convention clearly answers a technology question, skip asking it, but capture any deviations and the reasons for them.

## Capture Decisions

Have a focused conversation about the key technical decisions for this project. Focus on decisions that shape implementation — things an engineer picking up an issue needs to know. Cover what's genuinely relevant; not every area applies to every project.

Areas to consider: language and versions, frameworks, data persistence, caching and queues, infrastructure and deployment, architectural approach, key dependencies, authentication — and anything else that materially shapes the codebase.

See `references/example-tech-decisions.md` for what a well-formed decisions document looks like.

## Review and Store

Show the complete document for review. Do not store until the user confirms. Ask the user which Confluence space to use — if they have a PRD already, suggest the same space as a natural default but let them decide. Use `mcp__sooperset-mcp-atlassian__confluence_search` to surface available spaces if needed. Once the space is confirmed, use `mcp__sooperset-mcp-atlassian__confluence_get_page_children` to browse its structure and recommend a specific parent page location based on what already exists — if no suitable parent exists, recommend creating one. Confirm the location before creating with `mcp__sooperset-mcp-atlassian__confluence_create_page`. If the document already exists, update it with `mcp__sooperset-mcp-atlassian__confluence_update_page` using the existing page ID. Record the Confluence page ID and URL.

## Done

Share the Confluence page URL and page ID. Pass this URL to your developer — they will record it in the project manifest alongside the PRD URL and Jira project details. With requirements and technology decisions settled, the natural next step is sprint planning — taking the PRD and tech decisions into Jira and creating the first set of backlog issues ready for sprint assignment.