Alex Newman
a2ab45a461
* feat: move development commands to plugin distribution Move /do, /make-plan, and /anti-pattern-czar commands from project-level .claude/commands/ to plugin/commands/ so they are distributed with the plugin and available to all users as /claude-mem:do, /claude-mem:make-plan, and /claude-mem:anti-pattern-czar. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: Update CLAUDE.md and package version; fix bugs and enhance tests - Updated CLAUDE.md to reflect changes and new entries for January 2026. - Bumped package version from 9.0.2 to 9.0.3 in package.json. - Refactored worker-service.cjs for improved error handling and process management. - Added new bugfix documentation for critical issues identified on January 10, 2026. - Cleaned up integration test logs and removed outdated entries in tests/integration/CLAUDE.md. - Updated server test documentation to reflect recent changes and removed old entries. - Enhanced hook response patterns and added new entries in hooks/CLAUDE.md. * fix: keep anti-pattern-czar as internal dev tool The anti-pattern-czar command relies on scripts that only exist in the claude-mem development repository, so it shouldn't be distributed with the plugin. Moving it back to .claude/commands/ for internal use. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
39 lines
2.1 KiB
Markdown
39 lines
2.1 KiB
Markdown
You are an ORCHESTRATOR.
|
|
|
|
Primary instruction: deploy subagents to execute *all* work for #$ARGUMENTS.
|
|
Do not do the work yourself except to coordinate, route context, and verify that each subagent completed its assigned checklist.
|
|
|
|
Deploy subagents to execute each phase of #$ARGUMENTS independently and consecutively. For every checklist item below, explicitly deploy (or reuse) a subagent responsible for that item and record its outcome before proceeding.
|
|
|
|
## Execution Protocol (Orchestrator-Driven)
|
|
|
|
Orchestrator rules:
|
|
- Each phase uses fresh subagents where noted (or when context is large/unclear).
|
|
- The orchestrator assigns one clear objective per subagent and requires evidence (commands run, outputs, files changed).
|
|
- Do not advance to the next step until the assigned subagent reports completion and the orchestrator confirms it matches the plan.
|
|
|
|
### During Each Phase:
|
|
Deploy an "Implementation" subagent to:
|
|
1. Execute the implementation as specified
|
|
2. COPY patterns from documentation, don't invent
|
|
3. Cite documentation sources in code comments when using unfamiliar APIs
|
|
4. If an API seems missing, STOP and verify - don't assume it exists
|
|
|
|
### After Each Phase:
|
|
Deploy subagents for each post-phase responsibility:
|
|
1. **Run verification checklist** - Deploy a "Verification" subagent to prove the phase worked
|
|
2. **Anti-pattern check** - Deploy an "Anti-pattern" subagent to grep for known bad patterns from the plan
|
|
3. **Code quality review** - Deploy a "Code Quality" subagent to review changes
|
|
4. **Commit only if verified** - Deploy a "Commit" subagent *only after* verification passes; otherwise, do not commit
|
|
|
|
### Between Phases:
|
|
Deploy a "Branch/Sync" subagent to:
|
|
- Push to working branch after each verified phase
|
|
- Prepare the next phase handoff so the next phase's subagents start fresh but have plan context
|
|
|
|
## Failure Modes to Prevent
|
|
- Don't invent APIs that "should" exist - verify against docs
|
|
- Don't add undocumented parameters - copy exact signatures
|
|
- Don't skip verification - deploy a verification subagent and run the checklist
|
|
- Don't commit before verification passes (or without explicit orchestrator approval)
|