FIRST-TIME-SETUP.md 15 KB

OAC Plugin - First-Time Setup Guide

Version: 1.0.0
Date: 2026-02-16
Audience: First-time users
Time: 5-10 minutes


๐ŸŽฏ What You'll Accomplish

By the end of this guide, you'll have:

  • โœ… OAC plugin installed and verified
  • โœ… Context files downloaded
  • โœ… Working development workflow
  • โœ… Understanding of the 6-stage process

No prior experience needed โ€” just follow the steps in order.


๐Ÿ“‹ Prerequisites

Before starting, ensure you have:

  • Claude Code installed and working
  • Internet connection (for downloading context files)
  • A project directory to work in

๐Ÿš€ Step-by-Step Setup

Step 1: Install the Plugin

Choose ONE method:

Option A: From GitHub Marketplace (Recommended)

# Add the marketplace
/plugin marketplace add darrenhinde/OpenAgentsControl

# Install the plugin
/plugin install oac

Expected output:

โœ“ Marketplace added: darrenhinde/OpenAgentsControl
โœ“ Plugin installed: oac
โœ“ Location: ~/.claude/plugins/cache/oac/

Option B: Local Development

# Navigate to the repo
cd /path/to/OpenAgentsControl

# Start Claude with the plugin
claude --plugin-dir ./plugins/claude-code

Expected output:

โœ“ Loading plugin from: ./plugins/claude-code
โœ“ Plugin loaded: oac

Step 2: Verify Installation

Run the status command to check everything is working:

/oac:status

Expected output:

OAC Plugin Status
=================

Plugin Version: 1.0.0
Status: โœ… Installed

Components:
- Subagents: 6 available
  โœ“ task-manager
  โœ“ context-scout
  โœ“ external-scout
  โœ“ coder-agent
  โœ“ test-engineer
  โœ“ code-reviewer

- Skills: 9 available
  โœ“ using-oac
  โœ“ context-discovery
  โœ“ external-scout
  โœ“ task-breakdown
  โœ“ code-execution
  โœ“ test-generation
  โœ“ code-review
  โœ“ context-manager
  โœ“ parallel-execution

- Commands: 4 available
  โœ“ /oac:setup
  โœ“ /oac:help
  โœ“ /oac:status
  โœ“ /oac:cleanup

Context Files: โš ๏ธ Not installed yet

โœ… Success indicator: You should see "Plugin Version: 1.0.0" and all components listed.

โŒ If you see errors: See Troubleshooting section below.


Step 3: Download Context Files

Context files contain coding standards, security patterns, and workflow guides that OAC uses to ensure high-quality code.

Choose ONE option:

Option A: Core Context Only (Recommended for First-Time Users)

/oac:setup --core

What this downloads: ~50 essential files (standards, workflows, patterns)
Download time: 30-60 seconds
Disk space: ~2 MB

Expected output:

Downloading OAC Context Files
==============================

Category: core
Source: https://github.com/darrenhinde/OpenAgentsControl

Downloading files...
โœ“ .opencode/context/core/standards/code-quality.md
โœ“ .opencode/context/core/standards/security-patterns.md
โœ“ .opencode/context/core/standards/typescript.md
โœ“ .opencode/context/core/workflows/6-stage-workflow.md
... (46 more files)

Summary:
========
โœ“ Downloaded: 50 files
โœ“ Location: .opencode/context/
โœ“ Manifest: plugins/claude-code/.context-manifest.json

Next steps:
- Run /oac:status to verify
- Start coding with /using-oac

Option B: All Context (For Advanced Users)

/oac:setup --all

What this downloads: ~200 files (includes examples, guides, plugin docs)
Download time: 2-3 minutes
Disk space: ~8 MB


Step 4: Verify Context Installation

Check that context files were downloaded successfully:

/oac:status

Expected output:

OAC Plugin Status
=================

Plugin Version: 1.0.0
Status: โœ… Installed

Context Files: โœ… Installed
- Version: 1.0.0
- Location: .opencode/context/
- Files: 50 (core)
- Last updated: 2026-02-16

Components:
... (same as before)

โœ… Success indicator: "Context Files: โœ… Installed"

You can also verify manually:

# Check that context directory exists
ls .opencode/context/

# Should show:
# core/  openagents-repo/  navigation.md

Step 5: View Available Features

Get an overview of what OAC can do:

/oac:help

Expected output: A comprehensive guide showing:

  • 6-stage workflow overview
  • Available skills and when to use them
  • Available subagents and their purposes
  • Available commands
  • Quick start examples

Take 2 minutes to skim this output โ€” it's your reference guide.


Step 6: Test the Workflow

Let's test OAC with a simple task to ensure everything works.

Type this into Claude Code:

Add a hello world function to a new file called utils.ts

What should happen:

  1. Stage 1: Analyze & Discover ``` I'll help you add a hello world function. Let me discover relevant context first.

Invoking /context-discovery to find coding standards...


2. **Stage 2: Plan & Approve**

Plan:

  • Create src/utils.ts
  • Add helloWorld() function
  • Follow TypeScript standards from context

Files to create:

  • src/utils.ts

May I proceed with this plan? (yes/no)

   
   **Type**: `yes`

3. **Stage 3: LoadContext**

Loading context files... โœ“ Read .opencode/context/core/standards/typescript.md โœ“ Read .opencode/context/core/standards/code-quality.md


4. **Stage 4: Execute**

Creating src/utils.ts... โœ“ File created with helloWorld() function


5. **Stage 5: Validate**

Validating implementation... โœ“ TypeScript syntax valid โœ“ Follows coding standards โœ“ No anti-patterns detected


6. **Stage 6: Complete**

โœ… Task completed successfully!

Summary:

  • Created src/utils.ts
  • Added helloWorld() function
  • Follows TypeScript standards ```

โœ… Success indicator: You should see all 6 stages complete without errors.


๐ŸŽ“ Understanding the 6-Stage Workflow

Every task in OAC follows this workflow:

โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Stage 1: Analyze & Discover                                 โ”‚
โ”‚ - Understand what you're asking for                         โ”‚
โ”‚ - Find relevant context files (standards, patterns)         โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ†“
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Stage 2: Plan & Approve                                     โ”‚
โ”‚ - Present implementation plan                               โ”‚
โ”‚ - REQUEST APPROVAL before proceeding                        โ”‚
โ”‚ - Confirm approach with you                                 โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ†“
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Stage 3: LoadContext                                        โ”‚
โ”‚ - Read all discovered context files                         โ”‚
โ”‚ - Load coding standards, security patterns                  โ”‚
โ”‚ - Pre-load everything needed for execution                  โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ†“
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Stage 4: Execute                                            โ”‚
โ”‚ - Simple tasks (1-3 files): Direct implementation           โ”‚
โ”‚ - Complex tasks (4+ files): Break down into subtasks        โ”‚
โ”‚ - Follow loaded standards and patterns                      โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ†“
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Stage 5: Validate                                           โ”‚
โ”‚ - Run tests and validation                                  โ”‚
โ”‚ - STOP on failure โ€” fix before proceeding                   โ”‚
โ”‚ - Verify acceptance criteria met                            โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜
                            โ†“
โ”Œโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”
โ”‚ Stage 6: Complete                                           โ”‚
โ”‚ - Update documentation                                      โ”‚
โ”‚ - Summarize changes                                         โ”‚
โ”‚ - Return results                                            โ”‚
โ””โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”˜

Key points:

  • Approval gate at Stage 2 โ€” You control what gets implemented
  • Context loaded upfront โ€” Ensures consistent, high-quality code
  • Validation before completion โ€” Catches issues early
  • Automatic for every task โ€” You don't need to invoke it manually

๐ŸŽฏ What's Next?

Now that OAC is set up, you can:

1. Start Building Features

Just describe what you want to build:

Build a user authentication system with JWT tokens

OAC will:

  • Discover relevant security patterns
  • Break down into subtasks (if complex)
  • Implement following best practices
  • Generate tests
  • Review code quality

2. Explore Advanced Features

Context Manager โ€” Set up project-specific configuration:

/context-manager

Parallel Execution โ€” Speed up multi-component features:

# Automatically used when tasks are independent
# Example: Frontend + Backend + Tests run simultaneously

External Scout โ€” Fetch current library documentation:

/external-scout drizzle schemas
/external-scout react hooks

3. Learn the Skills

Each skill has a specific purpose:

Skill When to Use
/using-oac Auto-invoked for every task
/context-discovery Find relevant standards and patterns
/external-scout Get current library documentation
/task-breakdown Break down complex features
/code-execution Implement features
/test-generation Create comprehensive tests
/code-review Review code quality
/context-manager Set up projects and configuration
/parallel-execution Execute independent tasks simultaneously

4. Read the Documentation

  • Quick Start: QUICK-START.md โ€” Usage examples and workflows
  • Installation: INSTALL.md โ€” Detailed installation guide
  • Full README: README.md โ€” Complete system overview

๐Ÿ†˜ Troubleshooting

Issue: Plugin not found

Symptom: /oac:status returns "command not found"

Solution:

# Check plugin list
/plugin list

# Should show "oac" in the list
# If not, reinstall:
/plugin install oac

Issue: Context files not downloading

Symptom: /oac:setup --core fails or times out

Solution:

# Check internet connection
ping github.com

# Try again with verbose output
/oac:setup --core --verbose

# If still failing, check GitHub access
curl https://raw.githubusercontent.com/darrenhinde/OpenAgentsControl/main/README.md

Issue: Skills not working

Symptom: /context-discovery returns "skill not found"

Solution:

# Verify skill files exist
ls ~/.claude/plugins/cache/oac/skills/

# Should show 9 directories
# If missing, reinstall plugin
/plugin uninstall oac
/plugin install oac

Issue: Subagents not available

Symptom: Error when trying to invoke subagent

Solution:

# Check status
/oac:status

# Should show 6 subagents
# If missing, verify agent files
ls ~/.claude/plugins/cache/oac/agents/

# Should show 6 .md files
# If missing, reinstall plugin

Issue: Workflow not auto-starting

Symptom: Tasks don't automatically invoke /using-oac

Solution:

# Check hooks are installed
ls ~/.claude/plugins/cache/oac/hooks/

# Should show:
# - hooks.json
# - session-start.sh

# Restart Claude Code to reload hooks

Issue: Context files exist but not being used

Symptom: OAC says "context not found" but files exist

Solution:

# Verify context location
ls .opencode/context/core/standards/

# Should show multiple .md files

# Check manifest
cat plugins/claude-code/.context-manifest.json

# Should show version and file list

# If manifest missing, re-run setup
/oac:setup --core --force

โœ… Success Checklist

Before you finish, verify:

  • /oac:status shows "Plugin Version: 1.0.0"
  • /oac:status shows "Context Files: โœ… Installed"
  • /oac:status shows 6 subagents, 9 skills, 4 commands
  • .opencode/context/ directory exists with files
  • Test task completed successfully (hello world example)
  • You understand the 6-stage workflow
  • You know where to find help (/oac:help)

All checked? ๐ŸŽ‰ You're ready to build with OAC!


๐Ÿ“š Additional Resources

Quick Reference

Command Purpose
/oac:status Check installation status
/oac:help View comprehensive help
/oac:setup --core Download context files
/oac:cleanup Clean up old temporary files

Documentation

  • This guide: First-time setup (you are here)
  • QUICK-START.md: Usage examples and workflows
  • INSTALL.md: Detailed installation guide
  • README.md: Complete system overview

Support


๐ŸŽ‰ Welcome to OAC!

You're now ready to build high-quality, context-aware code with OpenAgents Control.

Remember:

  • OAC automatically guides you through the 6-stage workflow
  • Approval gates keep you in control
  • Context files ensure consistent, high-quality code
  • Skills and subagents handle the complexity

Happy coding! ๐Ÿš€


Version: 1.0.0
Last Updated: 2026-02-16
Status: Production Ready