realjeffreyau/selectskills-for-codex/agentic-os

project-root/
├── CLAUDE.md          # Kernel: identity, routing rules, agent registry
├── agents/            # Specialist agent definitions (markdown prompts)
├── .claude/commands/  # Slash commands: user-facing CLI
├── scripts/           # Daemon scripts: scheduled or event-driven tasks
└── data/              # State: JSON/markdown filesystem, no external DB

# CLAUDE.md - Agentic OS Kernel
 
## Identity
You are the COO of [project-name]. You route tasks to specialist agents.
You never write code directly. You delegate to the right agent and synthesize results.
 
## Agent Registry
 
| Agent | Role | Trigger |
|---|---|---|
| @dev | Code, architecture, debugging | User says "build", "fix", "refactor" |
| @writer | Documentation, content, emails | User says "write", "draft", "blog" |
| @researcher | Research, analysis, fact-checking | User says "research", "analyze", "compare" |
| @ops | DevOps, deployment, infrastructure | User says "deploy", "CI", "server" |
 
## Routing Rules
1.Parse the user request for intent keywords
2.Match to the Agent Registry trigger column
3.Load the corresponding agent file from `agents/<name>.md`
4.Hand off execution with full context
5.Synthesize and present the result back to the user
 
## Model Policies
-Default model: use the repository or harness default.
-@dev tasks: prefer a higher-reasoning model for complex architecture.
-@researcher tasks: use the configured research-capable model and approved search tools.
-Cost ceiling: warn before exceeding the project's configured spend threshold.

# @dev - Software Engineer
 
## Identity
You are a senior software engineer. You write clean, tested, production-grade code.
You prefer simple solutions. You ask clarifying questions when requirements are ambiguous.
 
## Memory Scope
-Read `data/projects/<current-project>.md` for context
-Read `data/decisions/` for architectural decisions
-Append execution logs to `data/logs/<date>-@dev.md`
 
## Tool Access
-Full filesystem access within project root
-Git operations (status, diff, commit, branch)
-Test runner access
-MCP servers as configured in `.claude/mcp.json`
 
## Constraints
-Always write tests for new features
-Never commit directly to `main`; use feature branches
-Prefer editing existing files over creating new ones
-Keep functions under 50 lines when possible

User: "Build a landing page and write the launch blog post"
 
Kernel routing:
1. @dev - "Build a landing page with [requirements]"
2. @writer - "Write a launch blog post for [product] using the landing page copy"
3. Kernel synthesizes both outputs into a unified response

# /daily-sync
 
Run the morning briefing:
 
1.Read `data/logs/last-sync.md` for context
2.Check project status: `git status`, pending PRs, CI health
3.Review `data/inbox/` for new tasks or decisions needed
4.Generate a summary of blockers, priorities, and next actions
5.Append the briefing to `data/logs/daily/<date>.md`

data/
├── daily-logs/         # Append-only daily activity logs
├── projects/           # Per-project context files
├── decisions/          # Architectural and business decisions (ADR format)
├── inbox/              # New tasks or ideas awaiting triage
├── contacts/           # People, companies, relationship notes
└── templates/          # Reusable prompts and formats

# 2026-04-22 - Daily Log
 
## Sessions
-09:00 - Session 1: Refactored auth module (@dev)
-11:30 - Session 2: Drafted investor update (@writer)
 
## Decisions
-Switched from JWT to session cookies (see `data/decisions/2026-04-22-auth.md`)
 
## Blockers
-Waiting on API key from vendor (follow up 2026-04-24)
 
## Next Actions
-[ ] Merge auth refactor PR
-[ ] Send investor update for review

## Reflection - Session 3
-What worked: Parallel agent execution saved 20 minutes
-What didn't: @researcher hit a paywalled source, need better source ranking
-What to change: Add `source-tier` field to research notes (A/B/C credibility)

<!-- ~/Library/LaunchAgents/com.agentic.daily-sync.plist -->
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" ...>
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>com.agentic.daily-sync</string>
    <key>ProgramArguments</key>
    <array>
        <string>/claude</string>
        <string>--cwd</string>
        <string>/path/to/project</string>
        <string>--command</string>
        <string>/daily-sync</string>
    </array>
    <key>StartCalendarInterval</key>
    <dict>
        <key>Hour</key>
        <integer>8</integer>
        <key>Minute</key>
        <integer>0</integer>
    </dict>
    <key>StandardOutPath</key>
    <string>/tmp/agentic-daily-sync.log</string>
</dict>
</plist>

# ~/.config/systemd/user/agentic-daily-sync.service
[Unit]
Description=Agentic OS Daily Sync
 
[Service]
Type=oneshot
ExecStart=/usr/local/bin/claude --cwd /path/to/project --command /daily-sync

# ~/.config/systemd/user/agentic-daily-sync.timer
[Unit]
Description=Run daily sync every morning
 
[Timer]
OnCalendar=*-*-* 8:00:00
Persistent=true
 
[Install]
WantedBy=timers.target

# ecosystem.config.js
module.exports = {
  apps: [{
    name: 'agentic-daily-sync',
    script: 'claude',
    args: '--cwd /path/to/project --command /daily-sync',
    cron_restart: '0 8 * * *',
    autorestart: false
  }]
};

// data/projects/website-v2.json
{
  "name": "Website v2",
  "status": "in-progress",
  "milestone": "beta-launch",
  "agents_involved": ["@dev", "@writer"],
  "files": {
    "spec": "docs/website-v2-spec.md",
    "design": "designs/website-v2.fig"
  },
  "metrics": {
    "commits": 47,
    "last_session": "2026-04-22T11:30:00Z"
  }
}

{
  "name": "Website v2",
  "status": "in-progress",
  "milestone": "beta-launch",
  "_deprecated_priority": "high",
  "priority_v2": { "level": "high", "rationale": "Blocks investor demo" }
}

# BAD - One agent does everything
You are a full-stack developer, writer, researcher, and DevOps engineer.

# BAD - No memory between sessions
Starting fresh every time Claude Code opens.

# BAD - API keys in agent files or CLAUDE.md
Your OpenAI API key is sk-xxxxxxxx

# BAD - PostgreSQL for a solo user's agentic OS

# BAD - Routing logic in code instead of markdown tables
if (intent.includes('deploy')) { agent = opsAgent; }