HQ

HQ is a personal productivity vault built on Obsidian and powered by a multi-agent orchestration system running on Claude Code. It uses the PARA method (Projects, Areas, Resources, Archive) for organizing notes and a team of specialist AI agents -- coordinated by a dispatcher named Pam -- to handle everything from quick captures to full project execution through PRD-driven workflows.

Prerequisites

• Claude Code (CLI) installed and authenticated
• Obsidian installed
• Obsidian community plugins: data-files-editor, obsidian-html-plugin
• Claude Code plugin: javascript-typescript from the claude-code-workflows marketplace (required by the Wallace agent for TypeScript/Node.js skills). Install with: claude plugin install javascript-typescript@claude-code-workflows

Setup

1. Clone the repo and enter the vault:

   git clone <repo-url>
   cd hq

2. Run the setup script:

   ./setup.sh

   This creates your personal context file, installs the required Claude Code plugin, creates your personal branch, and suggests a shell alias.

3. Edit 2-areas/hq/assistant/personal-context.md with your real details. This file is gitignored.

4. Open the hq folder as a vault in Obsidian. Install and enable the community plugins listed above when prompted.

5. Add a shell alias for quick access (add to ~/.zshrc or ~/.bashrc):

   alias pam='claude --dangerously-skip-permissions --agent pam'

   Restart your shell or run source ~/.zshrc, then run pam from inside your vault directory.

How to Use

Talk to Pam. She is the front door to the entire system. Open a terminal in your vault directory and run pam (or claude --agent pam).

Pam classifies every request into one of three tiers:

Tier	What it is	Example
Capture	Quick note, idea, or brainstorm	"jot down this meeting summary"
Quick task	Single-agent job, no project needed	"draft a cold email to X"
Initiative	Multi-step project with PRDs	"build a landing page for my SaaS"

For captures, Pam routes to Scribe who saves a clean note in the vault. For quick tasks, Pam dispatches the right specialist directly. For initiatives, Pam creates a project folder, writes a plan, breaks it into PRDs, and dispatches agents to execute each one. PRDs are the canonical state artifact -- they carry the spec, status, execution log, and result in one file.

Agents

Agent	Role
Pam	Front-door assistant, planner, project manager, and dispatch orchestrator
Wallace	Backend developer -- Node.js services, API routes, server-side logic
Frank	Frontend developer -- Next.js, Tailwind CSS, client-side code
Faye	UX/UI designer -- visual interfaces, HTML mockups, design guides
Isaac	Trend researcher -- market intelligence, niches, business opportunities
Maya	Product marketing and GTM strategist -- positioning, pricing, funnels
Sam	Content writer -- marketing copy, emails, social content
Scribe	Note capture -- cleans up rough input into structured vault notes
Manny	Agent manager -- creates and maintains agent definitions

Agent definitions live in .claude/agents/. Each .md file defines one specialist's role, scope, skills, and workflow.

Folder Structure

~/hq/
  0-inbox/              Unprocessed captures, ideas, notes
  1-projects/           Active projects (PRD-driven execution)
  2-areas/
    hq/                 System area (templates, assistant config)
      assistant/        Personal context for Claude
      templates/        PRD, plan, and project templates
  3-resources/          Reference material, guides, research
  4-archive/            Completed or inactive items
  .claude/
    agents/             Agent definitions (one .md per agent)
    skills/
      hq-*/             HQ-specific skills
    settings.local.json Vault-level Claude Code permissions
  .agents/
    skills/             Third-party vendored skills (clone-and-go)
  .obsidian/            Vault config (three files tracked, rest gitignored)
  skills-lock.json      Vendored skill integrity hashes
  tasks.base            Obsidian Bases view for PRD tracking

Updating

To pull system updates from main into your personal branch:

git checkout <your-name>
git merge main

Conflicts will only arise if you edited system files (agents, skills, templates). Personal content in the PARA folders is gitignored and unaffected.