From 8366c09a27d4103314666346323153ca9a7cd6c3 Mon Sep 17 00:00:00 2001 From: Bryan Ramos Date: Wed, 1 Apr 2026 17:01:44 -0400 Subject: [PATCH] refactor: rename plan agent to architect --- README.md | 2 +- agents/{plan.md => architect.md} | 2 +- skills/orchestrate/SKILL.md | 10 +++++----- 3 files changed, 7 insertions(+), 7 deletions(-) rename agents/{plan.md => architect.md} (99%) diff --git a/README.md b/README.md index ef5f2fc..9e95eb5 100644 --- a/README.md +++ b/README.md @@ -25,7 +25,7 @@ The script symlinks `agents/`, `skills/`, `CLAUDE.md`, and `settings.json` into | `senior-worker` | opus | Escalation for architectural complexity or worker failures. | | `debugger` | sonnet | Diagnoses and fixes bugs with minimal targeted changes. | | `docs-writer` | sonnet | Writes and updates docs. Never modifies source code. | -| `plan` | opus | Research-first planning. Produces implementation plans for workers. Read-only. | +| `architect` | opus | Research-first planning. Produces implementation plans for workers. Read-only. | | `code-reviewer` | sonnet | Reviews diffs for quality, correctness, and coverage. Read-only. | | `security-auditor` | opus | Audits security-sensitive changes for vulnerabilities. Read-only. | | `karen` | opus | Independent fact-checker. Verifies worker output against source and web. Read-only, runs in background. | diff --git a/agents/plan.md b/agents/architect.md similarity index 99% rename from agents/plan.md rename to agents/architect.md index 561f7df..d42cb40 100644 --- a/agents/plan.md +++ b/agents/architect.md @@ -1,5 +1,5 @@ --- -name: Plan +name: architect description: Research-first planning agent. Use before any non-trivial implementation task. Verifies approaches against official documentation and community examples, analyzes the codebase, and produces a concrete implementation plan for workers to follow. model: opus effort: max diff --git a/skills/orchestrate/SKILL.md b/skills/orchestrate/SKILL.md index d311182..253327a 100644 --- a/skills/orchestrate/SKILL.md +++ b/skills/orchestrate/SKILL.md @@ -16,7 +16,7 @@ You (orchestrator) ├── docs-writer (sonnet, effort: high) — READMEs, API refs, architecture docs, changelogs; never touches source ├── requirements-analyst (sonnet, read-only) — first planning stage: tier classification, constraints, research questions ├── researcher (sonnet, read-only) — one per topic, parallel; verified facts from docs and community - ├── plan (opus, effort: max) — architect: receives requirements + research, produces implementation blueprint + ├── architect (opus, effort: max) — architect: receives requirements + research, produces implementation blueprint ├── decomposer (sonnet, read-only) — translates plan into parallelizable worker task specs ├── code-reviewer (sonnet, read-only) — quality gate: logic, naming, error handling, test coverage ├── security-auditor (opus, read-only) — vulnerability audit: injection, auth, secrets, crypto, OWASP @@ -46,7 +46,7 @@ Determine before starting. Default to the lowest applicable tier. **Cost-aware shortcuts:** - Tier 1 with obvious approach: skip the planning pipeline entirely — spawn worker directly -- Tier 1 with uncertain approach: spawn `plan` directly (skip requirements-analyst and researcher) +- Tier 1 with uncertain approach: spawn `architect` directly (skip requirements-analyst and researcher) - Tier 2+: run the full pipeline - When in doubt, err toward shipping — the review chain catches mistakes cheaper than the planning pipeline prevents them @@ -80,12 +80,12 @@ Each researcher receives: Collect all researcher outputs. Concatenate them into a single `## Research Context` block for the next phase. **Phase 3 — Architecture and planning** -Spawn `plan` with three inputs assembled as a single prompt: +Spawn `architect` with three inputs assembled as a single prompt: - Requirements analysis output (from Phase 1) - Research context block (from Phase 2, or "No research context — approach uses established codebase patterns." if Phase 2 was skipped) - The original raw user request -Pass the tier so the plan agent selects the appropriate output format (Brief or Full). +Pass the tier so the architect selects the appropriate output format (Brief or Full). ### Step 4 — Consume the plan @@ -193,7 +193,7 @@ When the plan includes risk tags, use this table to determine mandatory reviewer | `external-api` | `karen` | Verify API usage against documentation | | `data-mutation` | `verification` | Must validate writes to persistent storage at runtime | | `breaking-change` | `karen` | Verify downstream impact, check AC coverage | -| `new-library` | `karen` | Verify usage against docs; planner must do full research first | +| `new-library` | `karen` | Verify usage against docs; architect must do full research first | | `concurrent` | `verification` | Concurrency bugs are hard to catch in static review | When multiple risk tags are present, take the union of all mandatory reviewers.