Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1 +1,2 @@
Auto\ Run\ Docs/
*.DS_Store
74 changes: 74 additions & 0 deletions Setup/Claude-Cognitive-Infrastructure/0_INITIALIZE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
# Phase 0: Initialize

## Objective

Validate prerequisites and prepare for Claude Cognitive Infrastructure deployment.

## Prerequisites Checklist

### 1. Target Directory

Verify the target agent directory:

- [ ] Agent directory exists and is writable
- [ ] Directory has a clear name indicating agent purpose
- [ ] No critical files will be overwritten (or backup is acceptable)

### 2. Existing Infrastructure Check

Check for existing `.claude/` directory:

- [ ] If `.claude/` exists, determine upgrade vs fresh install
- [ ] If upgrading, backup existing memory files
- [ ] Note any custom configurations to preserve

### 3. Agent Context

Gather information about the agent:

- [ ] Agent name (from directory name)
- [ ] Organization (from parent directory, if applicable)
- [ ] Agent type/role (inferred from name or existing files)

## Agent Type Detection

Based on directory name, detect agent type for customization:

| Keywords in Name | Agent Type | Persona Suggestion |
|------------------|------------|-------------------|
| Sales, Lead, Pipeline | Sales | Scout |
| Engineer, Architect, Developer | Technical | Archon |
| Research, Analysis | Research | Sage |
| Marketing, Content | Marketing | Maven |
| Fundraising, Investor | Finance | Catalyst |
| Operations, Admin | Operations | Atlas |
| People, Recruiting, HR | People | Harbor |
| Executive, Chief | Executive | Aria |
| Brand, Communications | Communications | Echo |
| Strategy, Planning | Strategy | Compass |
| Customer, Success | Customer | Bridge |
| UX, Design | Design | Pixel |

## Validation Steps

1. Confirm agent directory path
2. Check write permissions
3. Detect agent type from name
4. Check for existing infrastructure
5. Determine installation mode (fresh/upgrade)

## Installation Modes

### Fresh Install
- Create complete `.claude/` structure
- Generate new CLAUDE.md identity
- Initialize empty memory files

### Upgrade Install
- Preserve existing memory files
- Update structure to latest version
- Add new capabilities (hooks, skills)

## Next Phase

Once prerequisites are validated, proceed to **1_ANALYZE.md** to analyze the agent context.
106 changes: 106 additions & 0 deletions Setup/Claude-Cognitive-Infrastructure/1_ANALYZE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,106 @@
# Phase 1: Analyze Agent Context

## Objective

Analyze the target agent's context to determine appropriate identity, skills, and configuration.

## Analysis Tasks

### 1. Directory Analysis

Examine the agent directory:

- [ ] Read directory name for agent purpose
- [ ] Check parent directory for organization context
- [ ] Look for existing ROLE.md or similar documentation
- [ ] Identify any existing configuration files

### 2. Agent Identity Derivation

From the directory name, derive:

| Component | Source | Example |
|-----------|--------|---------|
| Agent Name | Directory name | "Sales Lead Agent" |
| Organization | Parent directory | "Wayward Guardian" |
| Persona Name | Generated from type | "Scout" |
| Agent Type | Keywords in name | "Sales" |

### 3. Role Detection

If ROLE.md exists, extract:

- Role description (first paragraph after title)
- Key responsibilities (bulleted lists)
- Domain expertise areas
- Integration points with other agents

### 4. Existing Files Inventory

Check for files that inform configuration:

| File | Purpose | Action |
|------|---------|--------|
| ROLE.md | Role definition | Extract responsibilities |
| README.md | Documentation | Extract context |
| .claude/ | Existing infrastructure | Plan upgrade |
| auto-run/ | Playbooks | Note for integration |

## Agent Profile Template

Based on analysis, build agent profile:

```yaml
agent:
name: "<Agent Name>"
persona: "<Short Persona Name>"
organization: "<Organization Name>"
type: "<Agent Type>"

identity:
mission: "<One sentence mission>"
role: "<2-3 sentence role description>"

capabilities:
primary: [] # Core responsibilities
secondary: [] # Supporting tasks

integrations:
collaborates_with: [] # Other agents
tools: [] # External tools
```

## Analysis Outputs

Document the following for use in later phases:

1. **Agent Profile** - Complete identity information
2. **Installation Mode** - Fresh or upgrade
3. **Customizations Needed** - Based on agent type
4. **Preservation List** - Files to keep if upgrading

## Type-Specific Considerations

### Technical Agents
- Include architecture context directories
- Add development and testing contexts
- Consider code-related hooks

### Business Agents
- Include projects context
- Add working context for active tasks
- Consider CRM/pipeline integrations

### Research Agents
- Emphasize knowledge context
- Add research methodology
- Consider web search capabilities

### Operations Agents
- Include process documentation
- Add tracking and reporting
- Consider scheduling integrations

## Next Phase

Proceed to **2_PLAN_STRUCTURE.md** to plan the infrastructure structure.
200 changes: 200 additions & 0 deletions Setup/Claude-Cognitive-Infrastructure/2_PLAN_STRUCTURE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,200 @@
# Phase 2: Plan Structure

## Objective

Plan the complete Claude Cognitive Infrastructure directory structure for the agent.

## Core Directory Structure

```
<Agent Directory>/
├── CLAUDE.md # Agent identity file
└── .claude/
├── VERSION # Infrastructure version (1.1.0)
├── settings.json # Hook and behavior settings
├── config/
│ └── config.yaml # Runtime configuration
├── skills/
│ └── CORE/
│ └── SKILL.md # Core agent skill
├── context/
│ ├── CLAUDE.md # Context system documentation
│ ├── memory/
│ │ ├── learnings.md # Accumulated knowledge
│ │ ├── user_preferences.md # User working style
│ │ └── work_status.md # Current task tracking
│ ├── architecture/
│ │ └── CLAUDE.md # Architecture context
│ ├── design/
│ │ └── CLAUDE.md # Design principles
│ ├── development/
│ │ └── CLAUDE.md # Development context
│ ├── projects/
│ │ └── CLAUDE.md # Project configs
│ ├── testing/
│ │ └── CLAUDE.md # Testing guidelines
│ ├── tools/
│ │ └── CLAUDE.md # Tool documentation
│ └── working/
│ └── CLAUDE.md # Working context
├── hooks/
│ └── CLAUDE.md # Hooks documentation
├── agents/
│ └── CLAUDE.md # Agent definitions
├── scripts/
│ └── CLAUDE.md # Utility scripts
└── examples/
└── CLAUDE.md # Reference examples
```

## File Contents Plan

### CLAUDE.md (Root Identity)

```markdown
# <Agent Name>: <Agent Type>

## Your Name
Your name is **<Persona>**. You are the <Agent Type> for <Organization>.

## Your Mission
<Mission statement>

## Your Role
<Role description>

## Core Responsibilities
<Grouped responsibilities>

## Memory Management
**CRITICAL:** Update work_status.md after EVERY conversation turn.

## Organization Context
<Organization details>
```

### settings.json

```json
{
"hooks": {
"preToolCall": [],
"postToolCall": [],
"notification": []
},
"permissions": {
"tools": ["Read", "Write", "Edit", "Bash", "Glob", "Grep"]
}
}
```

### VERSION

```
1.1.0
```

### config/config.yaml

```yaml
version: "1.1.0"
agent:
name: "<Agent Name>"
persona: "<Persona>"
type: "<Agent Type>"
settings:
memory_update_frequency: "every_turn"
context_loading: "progressive"
```

### CORE/SKILL.md

```markdown
---
name: CORE
version: 1.0.0
priority: 100
triggers:
- identity
- who are you
- what do you do
context_budget: 5000
---

# <Persona>: Core Identity

## Overview
<Agent description and capabilities>

## Primary Functions
<Key responsibilities>

## Working Style
<How the agent operates>
```

### Memory Files

**learnings.md:**
```markdown
# Learnings

Facts and knowledge accumulated about users, organization, and domain.

## Users

## Organization

## Domain Knowledge
```

**user_preferences.md:**
```markdown
# User Preferences

Working style and preferences for interactions.

## Communication Style

## Working Hours

## Preferences
```

**work_status.md:**
```markdown
# Work Status

Current tasks and progress tracking.

## Active Tasks

## Pending Items

## Recently Completed

---
*Last updated: <date>*
```

## Context Placeholder Files

Each context subdirectory gets a CLAUDE.md placeholder:

```markdown
# <Context Name> Context

This directory contains <context type> information.

## Contents

<Description of what goes here>

## Usage

<How the agent should use this context>
```

## Next Phase

Proceed to **3_EVALUATE.md** to evaluate the planned structure.
Loading