teamcraft-jcg:capture-conventions

What this skill does

## Goal

Build or extend the team's shared conventions knowledge base — the standards and practices that apply across all projects this team builds. Not conventions for any specific project. Not a substitute for tech decisions (which are per-project). The output is the team's shared knowledge: how we build software, across all projects, over time.

## Hard Constraints

- Confluence is the only storage and retrieval mechanism. Never use local filesystem tools for any purpose.
- If an Atlassian MCP tool call fails, report the exact error to the user and stop. Do not fall back, retry with different approaches, or improvise alternatives.

## Establish Intent First

Start by asking the user what they want to accomplish in this session. Do not search Confluence before you know this. Present the common scenarios:

- Capture conventions for a new tech stack
- Update an existing tech stack (something changed)
- Capture a specific area (databases, CI/CD, security, sprint operations, API design, documentation standards, etc.)
- Update a specific area (something changed)
- Start from scratch — comprehensive capture across everything
- Something else (let them describe it)

Guide the conversation toward exactly what they choose. They may want to capture one thing, or a specific combination, or everything. Follow their lead.

## Orient to Confluence — Scoped to Intent

Once you know what the user wants to accomplish, ask whether they can point you at an existing conventions page or conventions space in Confluence before you search. Do not search until you have their answer. If they point you at something and it turns out to be a project artifact — a PRD, a tech decisions page, a project space — tell them and ask for conventions pages instead. If they don't have anything to point at, use `mcp__sooperset-mcp-atlassian__confluence_search` broadly to find documents that describe how the team builds software.

## Capture

Capture what's real and defined for this team. "We don't have a formal process for that" is a complete answer. Use `references/example-conventions.md` to understand the target structure, depth, and range of areas that conventions typically cover — format and organisation only. The stacks and content in that example are fictional and have nothing to do with this team. Everything about what this team actually uses comes from what you discover in Confluence and what the user tells you.

## Organise and Store

Help the user decide how to structure what was captured — a single comprehensive page, one page per tech stack, organised by area, or whatever fits how this team's knowledge base works. Ask the user which Confluence space to use. 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` or updating an existing page with `mcp__sooperset-mcp-atlassian__confluence_update_page`. Confirm the page title and URL.

## Done

Briefly summarise what was captured in this session. Note any major areas that remain uncaptured — a nudge toward future sessions, not a demand.