feat(skills): add Batch Execution, SDD, and Writing Plans skills#19
feat(skills): add Batch Execution, SDD, and Writing Plans skills#19maystudios wants to merge 1 commit intomainfrom
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Adds three new MAXSIM “skill” templates intended to standardize planning and execution workflows (parallel batch execution, subagent-per-task execution, and PLAN.md authoring).
Changes:
- Add
batch-executionskill template describing parallel work via isolated git worktrees. - Add
subagent-driven-developmentskill template describing one-task-per-subagent with inter-task review. - Add
writing-plansskill template describing a standardized PLAN.md authoring format with verify/done gates, dependency detection, and wave grouping.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.
| File | Description |
|---|---|
| templates/skills/batch-execution/SKILL.md | New skill template for parallelizing independent units of work. |
| templates/skills/subagent-driven-development/SKILL.md | New skill template for executing each plan task with a fresh subagent and 2-stage review. |
| templates/skills/writing-plans/SKILL.md | New skill template for writing structured plans with explicit verification and done criteria. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ### Context Loading | ||
|
|
||
| ```bash | ||
| node ~/.claude/maxsim/bin/maxsim-tools.cjs skill-context subagent-driven-development |
There was a problem hiding this comment.
This references a skill-context subcommand on maxsim-tools, but the CLI command registry (packages/cli/src/cli.ts:305-370) doesn’t include skill-context. Unless this command exists elsewhere, this example won’t work; either implement the command or adjust the docs to point to the installed skill location (e.g., under ~/.claude/maxsim/agents/skills/<skill>/SKILL.md).
| node ~/.claude/maxsim/bin/maxsim-tools.cjs skill-context subagent-driven-development | |
| # View this skill's installed documentation: | |
| cat ~/.claude/maxsim/agents/skills/subagent-driven-development/SKILL.md |
| | Excuse | Why It Violates the Rule | | ||
| |--------|--------------------------| | ||
| | "Sequential is simpler" | Simpler for you, slower for the user. Parallel is the job. | | ||
| | "What if they conflict?" | Verify independence first (step 2). If they conflict, they are not independent — re-decompose. | | ||
| | "Too many agents" | The threshold is 5 units. Below 5, sequential is acceptable. Above 5, parallelize. | | ||
| | "I'll batch the small ones" | Small units are the easiest to parallelize. Do not combine them. | | ||
| | "Worktrees are complex" | Worktree creation is automated. Your job is decomposition and monitoring. | | ||
|
|
There was a problem hiding this comment.
The “Common Rationalizations” table is using || at the start of each row, which renders as an extra empty column in standard Markdown. Other skills use normal 2‑column tables (e.g., templates/skills/tdd/SKILL.md:68-75). Consider switching these rows to a single leading | so the table renders consistently.
| ### Context Loading | ||
|
|
||
| ```bash | ||
| node ~/.claude/maxsim/bin/maxsim-tools.cjs skill-context batch-execution |
There was a problem hiding this comment.
This references a skill-context subcommand on maxsim-tools, but the CLI command registry (packages/cli/src/cli.ts:305-370) doesn’t include skill-context. Unless this command exists elsewhere, this example won’t work; either implement the command or adjust the docs to point to the installed skill location (e.g., under ~/.claude/maxsim/agents/skills/<skill>/SKILL.md).
| node ~/.claude/maxsim/bin/maxsim-tools.cjs skill-context batch-execution | |
| # View the installed batch-execution skill context | |
| cat ~/.claude/maxsim/agents/skills/batch-execution/SKILL.md |
| | Excuse | Why It Violates the Rule | | ||
| |--------|--------------------------| | ||
| | "The executor is smart enough to figure it out" | Smart executors with vague plans produce inconsistent results. Be explicit. | | ||
| | "Verify blocks are obvious" | If they are obvious, writing them takes 10 seconds. Do it. | | ||
| | "Done criteria are implicit in the description" | Implicit criteria cannot be checked. Make them explicit checkboxes. | | ||
| | "Dependencies are clear from context" | Context dies between agents. Write dependencies explicitly. | | ||
| | "Wave grouping is premature optimization" | Wave grouping enables parallel execution. It is not optimization — it is correctness. | | ||
| | "The plan is too detailed" | Plans cannot be too detailed. They can only be too vague. | |
There was a problem hiding this comment.
The “Common Rationalizations” table is using || at the start of each row, which renders as an extra empty column in standard Markdown. Other skills use normal 2‑column tables (e.g., templates/skills/tdd/SKILL.md:68-75). Consider switching these rows to a single leading | so the table renders consistently.
| ## Plan Structure Template | ||
|
|
||
| ```markdown | ||
| # Phase [N] Plan [M]: [Phase Name] | ||
|
|
||
| ## Overview | ||
| [1-2 sentences: what this plan achieves and why] | ||
|
|
||
| ## Tasks | ||
|
|
||
| ### Task 1: [Title] | ||
| ... | ||
|
|
||
| ### Task 2: [Title] | ||
| ... | ||
|
|
||
| ## Execution Order | ||
|
|
||
| **Wave 1** (parallel): Tasks 1, 2 | ||
| **Wave 2** (parallel): Tasks 3, 4 | ||
| **Wave 3** (sequential): Task 5 | ||
|
|
||
| ## Verification | ||
|
|
||
| After all tasks complete: | ||
| - [ ] [Phase-level success criterion 1] | ||
| - [ ] [Phase-level success criterion 2] | ||
| ``` |
There was a problem hiding this comment.
The “Plan Structure Template” here doesn’t include the XML-like <task>…</task> blocks that MAXSIM tooling parses/validates (see packages/cli/src/core/template.ts:176-223 and packages/cli/src/core/verify.ts:284-305). As written, maxsim-tools verify plan-structure will warn “No elements found” and the dashboard task parser won’t see any tasks. Please update this template to match the actual plan format (YAML frontmatter + <task> with <name>, <files>, <action>, <verify>, <done>).
| ### Context Loading | ||
|
|
||
| ```bash | ||
| node ~/.claude/maxsim/bin/maxsim-tools.cjs skill-context writing-plans |
There was a problem hiding this comment.
This references a skill-context subcommand on maxsim-tools, but the CLI command registry (packages/cli/src/cli.ts:305-370) doesn’t include skill-context. Unless this command exists elsewhere, this example won’t work; either implement the command or adjust the docs to point to the installed skill location (e.g., under ~/.claude/maxsim/agents/skills/<skill>/SKILL.md).
| node ~/.claude/maxsim/bin/maxsim-tools.cjs skill-context writing-plans | |
| # View the installed skill documentation for writing-plans | |
| cat ~/.claude/maxsim/agents/skills/writing-plans/SKILL.md |
| | Excuse | Why It Violates the Rule | | ||
| |--------|--------------------------| | ||
| | "I have context from the last task" | That context is rotting. Fresh agent, fresh perspective. | | ||
| | "Spawning agents is overhead" | Context rot costs more than spawn time. The math is clear. | | ||
| | "I can do multiple tasks efficiently" | Efficiency without accuracy is waste. One task, one agent. | | ||
| | "The tasks are related" | Related tasks still get separate agents. Share via committed code, not session state. | | ||
| | "Review between tasks slows things down" | Review catches what rot misses. The slowdown is an investment. | | ||
|
|
There was a problem hiding this comment.
The “Common Rationalizations” table is using || at the start of each row, which renders as an extra empty column in standard Markdown. Other skills use normal 2‑column tables (e.g., templates/skills/tdd/SKILL.md:68-75). Consider switching these rows to a single leading | so the table renders consistently.
Summary
Test plan
npx vitest run)npm run build)dist/assets/templates/skills/after build (140 template files copied)skill-context batch-execution,skill-context subagent-driven-development, andskill-context writing-plansCLI commands load the new skills🤖 Generated with Claude Code