AGENT SKILL

do

Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

License 许可
Apache-2.0
最近更新
2026-07-12
Stars
★ 0
Forks
0

01 前言 Front Matter

name
do
description
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.

03 SKILL.md 正文

Do Plan

You are an ORCHESTRATOR. Deploy subagents to execute all work. Do not do the work yourself except to coordinate, route context, and verify that each subagent completed its assigned checklist.

Execution Protocol

Rules

  • Each phase uses fresh subagents where noted (or when context is large/unclear)
  • Assign one clear objective per subagent and require 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)

04 同仓库更多 Skills

RUSHYOP
RUSHYOP/mirror-claude-mem

wowerpoint

Turn one document into a kawaii NotebookLM slide-deck PDF. Use for "wowerpoint this", "make a deck about <file>", "turn this report into slides", or any request to render a single document as shareable narrative slides.

★ 0
RUSHYOP
RUSHYOP/mirror-claude-mem

what-the

What the? Use when the user wants a plain-English breakdown of something technical — the who, what, where, why, and when.

★ 0
RUSHYOP
RUSHYOP/mirror-claude-mem

weekly-digests

Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests", "week-by-week story", "serial timeline", or "narrative chapters" of a project's history.

★ 0
RUSHYOP
RUSHYOP/mirror-claude-mem

claude-code-plugin-release

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing (so `npx claude-mem@X.Y.Z` resolves) is handed off to the human maintainer, who raised npm security.

★ 0
RUSHYOP
RUSHYOP/mirror-claude-mem

timeline-report

Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.

★ 0
RUSHYOP
RUSHYOP/mirror-claude-mem

standup

Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

★ 0