---
name: ai-pair-programming-session-kickoff
description: "Writes the opening message for an AI coding session so the assistant starts with your stack, goal and ground rules instead of guessing. Use when a developer is about to open an AI coding session and wants a kickoff message that front-loads the goal, codebase context and ground rules. Do not use for writing a long-lived rules file for a repository or a formal task brief. Related topics: AI, Coding, Technical."
---

# AI Pair-Programming Session Kickoff

Writes the opening message for an AI coding session so the assistant starts with your stack, goal and ground rules instead of guessing.

## When to use

Use this skill when a developer is about to open an AI coding session and wants a kickoff message that front-loads the goal, codebase context and ground rules. Do not use it for writing a long-lived rules file for a repository or a formal task brief.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Pin the goal and working mode into one sentence the assistant cannot misread, and confirm it matches the chosen mode.
3. Condense the codebase context to what the task touches: stack and versions, the relevant modules, and the data flow between them.
4. Record what was already tried and why it failed, so the assistant does not repeat those attempts.
5. Turn the chosen ground rules into short bullets and add the challenge-my-approach instruction only if requested.
6. Close with one concrete first step and read the message once to confirm it stands alone.

## Inputs

- **Assistant in use** (choose one: Cursor, Copilot Chat, Terminal agent, Other)
- **Goal for today** (free text, e.g. "What we are building or fixing")
- **Working mode** (choose one: Explore ideas first, Plan then code, Just code it)
- **Language, framework and versions** (free text, e.g. "TypeScript 5 with Next 14")
- **How the relevant code works** (longer free text)
- **What has been tried already** (longer free text)
- **Rules to apply** (choose any: Ask before big refactors, Run tests after changes, Explain trade-offs, Flag anything suspicious, Keep changes minimal)
- **Challenge my approach if a better one exists** (choose one: Yes, No)

## Output

A single kickoff message in this order: context, goal, ground rules as bullets, then one named first step. It should read in about a minute.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Pair-Programming Session Kickoff

Write the opening message for an AI coding session. The assistant should have everything it needs before it touches a file.

#### Session
- Assistant in use: {{Assistant in use}}
- Goal for today: {{Goal for today}}
- Working mode: {{Working mode}}

#### Codebase context
- Language, framework and versions: {{Language, framework and versions}}
- How the relevant code works: {{How the relevant code works}}
- What has been tried already: {{What has been tried already}}

#### Ground rules
- Rules to apply: {{Rules to apply}}
- Challenge my approach if a better one exists: {{Challenge my approach if a better one exists}}

Order the message as context first, then the goal, then the ground rules as short bullets, and end with the first concrete step the assistant should take. Match the working mode: for explore, ask it for options before any code; for plan, ask for a numbered plan and wait for approval; for just code, ask for the smallest working change. Put failed attempts in explicitly so they are not repeated. Keep the whole message short enough to read in one minute.

## Pitfalls

- Pasting the whole codebase description instead of the slice the task touches, which buries the goal.
- Leaving out failed attempts, so the assistant proposes the same fix again.
- Choosing 'just code it' without stating constraints, which invites sprawling changes.
