Prime: Load Project Context

Objective

Process

Step 0: Load External Context

[jira-issue-keys] [confluence-page-ids]

• Jira keys may be a single key (

  ACC-2

  ) or comma-separated (

  ACC-2,ACC-3

  ).
• Confluence page ids are numeric page ids.

1. Call

   mcp__atlassian__getAccessibleAtlassianResources

   to obtain the

   cloudId

   .
2. For each Jira key, call

   mcp__atlassian__getJiraIssue

   with that

   cloudId

   , the issue key, and

   responseContentFormat: "markdown"

   .
3. Treat the returned issue summary, description, and acceptance criteria as the task context for everything that follows.

1. Call

   mcp__atlassian__getConfluencePage

   for each page id with

   contentFormat: "markdown"

   (use the

   cloudId

   from above, fetching it via

   mcp__atlassian__getAccessibleAtlassianResources

   if it was not already retrieved).
2. Treat the returned page content as supporting context (specs, design docs, requirements).

1. Analyze Project Structure

git ls-files

tree -L 3 -I 'node_modules|__pycache__|.git|dist|build'

2. Read Core Documentation

• Read CLAUDE.md or similar global rules file
• Read README files at project root and major directories
• Read any architecture documentation

3. Identify Key Files

• Main entry points (main.py, index.ts, app.py, etc.)
• Core configuration files (pyproject.toml, package.json, tsconfig.json)
• Key model/schema definitions
• Important service or controller files

4. Understand Current State

git log -10 --oneline

git status

Output Report

External Task Context (if loaded)

• Jira issue(s): key, title, one-line goal, acceptance criteria
• Confluence page(s): title and what they specify

Project Overview

• Purpose and type of application
• Primary technologies and frameworks
• Current version/state

Architecture

• Overall structure and organization
• Key architectural patterns identified
• Important directories and their purposes

Tech Stack

• Languages and versions
• Frameworks and major libraries
• Build tools and package managers
• Testing frameworks

Core Principles

• Code style and conventions observed
• Documentation standards
• Testing approach

Current State

• Active branch
• Recent changes or development focus
• Any immediate observations or concerns