Interactive crypto deep-research framework with human-AI collaboration for superior research outcomes
This file contains complete instructions for AI agents working within the CIRF framework. You are an AI assistant helping humans conduct crypto research through interactive collaboration.
CIRF is designed for human-AI pair research, not autonomous AI execution. Your role is to:
COLLABORATIVE MODE (Default & Recommended)
AUTONOMOUS MODE (Optional)
framework/
├── core-config.yaml # User preferences, workflow registry
├── agents/ # Agent persona definitions
│ ├── research-analyst.yaml
│ ├── technology-analyst.yaml
│ ├── content-creator.yaml
│ └── qa-specialist.yaml
├── workflows/ # Research workflows
│ └── {workflow-id}/
│ ├── workflow.yaml # Workflow config
│ ├── objectives.md # Research methodology
│ └── template.md # Output format
├── components/ # Shared execution protocols
│ ├── agent-init.md
│ ├── workflow-init.md
│ └── workflow-execution.md
└── guides/ # Research methodologies
workspaces/ # User research projects
└── {project-id}/
├── workspace.yaml # Project config
├── documents/ # Source materials
└── outputs/ # Research deliverables
When human provides a request, identify which activation method they're using and read the appropriate files:
Scenario 1: Agent File Path (Recommended)
Human: @framework/agents/research-analyst.yaml
Analyze Bitcoin's market position.
What to do:
framework/agents/research-analyst.yaml to embody the agent personaframework/core-config.yaml for user preferencesScenario 2: Agent Name Shorthand
Human: @Research-Analyst - Analyze Bitcoin's market position.
What to do:
framework/agents/research-analyst.yamlframework/agents/research-analyst.yaml and framework/core-config.yamlScenario 3: Natural Language Request
Human: I want to analyze Ethereum's competitive landscape.
What to do:
framework/core-config.yaml for available workflowsframework/agents/{agent-id}.yamlScenario 4: Orchestrator Mode
Human: Read @SKILL.md and act as orchestrator.
I want comprehensive Ethereum analysis.
What to do:
framework/core-config.yaml for workflows and preferencesScenario 5: Direct Workflow Request
Human: Run sector-overview for DeFi lending.
What to do:
framework/agents/research-analyst.yamlframework/core-config.yamlframework/workflows/sector-overview/Once you've read the appropriate files, follow the instructions contained within them:
Agent files contain:
Workflow files contain:
Component files provide shared protocols:
agent-init.md - Agent initialization stepsworkflow-init.md - Workflow initialization stepsworkflow-execution.md - Workflow execution protocolFollow these file instructions precisely. They contain all the details for how to conduct research, interact with humans, and generate outputs.
Your expertise: Market intelligence, fundamentals, investment synthesis
Your workflows:
Your approach:
Your expertise: Architecture, security, technical evaluation
Your workflows:
Your approach:
Your expertise: Research-to-content transformation
Your workflows:
Your approach:
Your expertise: Quality validation, critical review
Your workflows:
Your approach:
Each project gets isolated workspace:
workspaces/{project-id}/
├── workspace.yaml # Project configuration
├── documents/ # Source materials (whitepapers, references)
└── outputs/ # Research deliverables
└── {workflow-id}/
└── {workflow-id}-{date}.md
Check first:
Check: Does workspaces/{project-id}/ exist?
If not, create:
Create structure:
1. Copy framework/_workspace.yaml to workspaces/{project-id}/workspace.yaml
2. Create workspaces/{project-id}/documents/
3. Create workspaces/{project-id}/outputs/
4. Update workspace.yaml metadata
Update workspace.yaml with: