codingthefuturewithai/teamcraft-glgd:capture-conventions

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

• Google Drive is the only storage and retrieval mechanism. Never use local filesystem tools for any purpose.
• If a Drive file operation fails with a path error, read the error message to identify a valid accessible host path and retry with it.
• If a Drive tool call fails, report the exact error to the user and stop. Do not fall back, retry with different paths, or improvise alternative approaches.

Resolve Drive Account

Call mcp__google-drive__list_accounts before any other Drive operation:

• No accounts — Drive is not configured for this user. Tell them and skip Drive operations.
• One account — Use it. Pass account_email explicitly on every Drive tool call this session.
• Multiple accounts — Present the list, ask which account to use for this session. Pass that account_email on every Drive tool call.

If any Drive call returns a permission error, surface it: the active account may not have access to that file or folder. Offer to try another account if one is available.

Establish Intent First

Start by asking the user what they want to accomplish in this session. Do not search Drive 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 Drive — Scoped to Intent

Once you know what the user wants to accomplish, ask whether they can point you at an existing conventions document or conventions folder in Google Drive 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 doc, a project folder — tell them and ask for conventions docs instead. If they don't have anything to point at, search broadly for 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 Drive and what the user tells you.

Organise and Store

Help the user decide how to structure what was captured — a single comprehensive document, one document per tech stack, organised by area, or whatever fits how this team's knowledge base works. Ask where to save in Google Drive. Confirm 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.