implement-batch — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited implement-batch (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 3 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 3 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Orchestrates a batch of tickets as a cohesive unit. Creates a project branch, implements each ticket sequentially using the /implement workflow in autonomous mode, runs cross-cutting quality passes, and presents results for final human review.
Maximize autonomy, minimize accumulated error. The goal is to complete an entire batch of tickets without user intervention — but not at the cost of letting problems compound. When something goes wrong, pull the andon cord immediately rather than pressing forward and hoping later steps will compensate.
The project branch is the integration point. Each ticket gets its own topic branch. Work flows from topic branches into the project branch, never directly into main. This keeps main clean and gives the user a single decision point at the end: merge the project branch or don't.
This skill is a for-loop, not an orchestrator. Tickets are the work definition. Commander's intent does not apply here — the tickets carry the intent, and cross-cutting constraints (if any) inherit from the caller (/implement-project or /lead-project). The skill applies the autonomy discipline documented in references/autonomy.md at the points where it does apply: the shared handoff template for andon-cord pulls, the cascade rule for /implement escalations.
Cascade rule. Escalations from /implement cascade up to this skill, not directly to the operator. When /implement would otherwise pull its own cord (e.g., 3-strike acceptance failure, unresolvable critical security finding), the batch skill catches that signal and pulls its cord with batch-level context (which ticket, which step, what's already merged). The caller has more context than the worker; the worker does not go around its caller.
┌──────────────────────────────────────────────────────┐
│ BATCH WORKFLOW │
├──────────────────────────────────────────────────────┤
│ 1. Receive ticket specification │
│ 2. Detect issue tracker & fetch tickets │
│ 3. Batch planning (present to user) │
│ 4. Create project branch │
│ 5. Per-ticket loop: │
│ ├─ 5a. Create topic branch │
│ ├─ 5b. Run /implement (autonomous mode) │
│ ├─ 5c. Merge topic branch → project branch │
│ ├─ 5d. Post-merge verification gate │
│ └─ 5e. Delete topic branch │
│ 6. Cross-cutting quality passes │
│ ├─ 6a. /refactor (SAFE aggression) │
│ └─ 6b. /tidy-docs │
│ 7. Final review (present to user) │
└──────────────────────────────────────────────────────┘This protocol applies throughout the entire workflow. When the andon cord is pulled:
references/autonomy.md. The escalation must include pre-loaded options (2–3 named choices), an explicit recommendation, the one tradeoff that would flip the recommendation, and a pre-rebutted counterargument. Include the skill-specific state: which ticket and step failed, current branch state (what's merged into the project branch, what's in-progress on a topic branch), and tracker links if relevant.Andon cord triggers (skill-specific):
/implement step 4)/implement step 5a)Accept tickets from the user in any of these forms:
#12, #15, #18)v2.0")Detect the issue tracker and fetch ticket data per references/trackers.md (Detection Procedure + "Fetch (read)" operation). Fetch each ticket's title, description, acceptance criteria, labels, and dependencies.
Andon cord if tracker is unavailable or tickets can't be fetched.
Analyze all fetched tickets and produce an execution plan:
Dependency analysis:
Execution ordering:
Present the plan to user:
Wait for user approval before proceeding. This is the one planned user interaction point.
main or master)feat/batch-<descriptive-name>For each ticket in the planned order:
#### 5a. Create Topic Branch
feat/issue-<number>-<brief-slug>#### 5b. Run /implement Workflow (Autonomous Mode)
Follow the /implement workflow with these overrides for autonomous operation:
/implement Step | Autonomous Override |
|---|---|
| Step 1 (requirements) | Pre-loaded from ticket body. Do not prompt user for requirements. If the ticket lacks explicit acceptance criteria, derive them from the description. If the description is empty or incoherent, andon cord. |
| Step 2 (planning) | Follow normal conditional logic — invoke swe-planner for complex tasks, skip for simple ones. |
| Steps 3-4 (implementation + acceptance) | Follow normal logic. If acceptance verification fails 3 times, andon cord (do not escalate to user within /implement — escalate here at the batch level). |
| Step 5a (security review) | Follow normal logic. If critical/high findings cannot be resolved by the implementation agent, andon cord. |
| Steps 5b-5c (refactoring/perf review) | Follow normal logic — these are advisory. |
| Step 6 (implement review feedback) | Follow normal logic. |
| Step 7 (peer review) | Follow normal logic. Handle deep issues autonomously — trust agents. If peer review breaks tests, revert peer review changes per standard /implement logic. |
| Step 8 (coverage/quality verification) | Follow normal logic. Handle autonomously — if tests pass, proceed. Do not prompt user for approval of minor issues. |
| Step 9 (documentation) | Follow normal logic. |
| Step 10 (final verification) | Follow normal logic. |
| Step 11a (commit) | Auto-commit with ticket reference. Use Fixes #<number> in the commit message. |
| Step 11b (ticket update/close) | Post a comment on the ticket summarizing changes made. Do not close the ticket — leave that for the user after final review. |
| Step 11c (rebase on main) | Skip entirely. We're on topic branches off the project branch, not main. |
#### 5c. Merge Topic Branch into Project Branch
git merge --no-ff feat/issue-<number>-<brief-slug>--no-ff preserves topic branch history for clarity#### 5d. Post-Merge Verification Gate
#### 5e. Clean Up Topic Branch
git branch -d feat/issue-<number>-<brief-slug>After all tickets are implemented and merged into the project branch:
#### 6a. Refactoring
Run the /refactor workflow with these parameters:
/refactor workflow handles its own iteration loop, commits, and QA verification#### 6b. Documentation Review
Run the /tidy-docs workflow:
Present comprehensive summary to user:
## Batch Complete
### Tickets Implemented
- #12: <title> — <brief outcome>
- #15: <title> — <brief outcome>
- #18: <title> — <brief outcome>
### Statistics
- Total commits: N
- Net lines changed: +/-N
- Tests added/modified: N
- Documentation files updated: N
### Quality Passes
- Refactoring: N improvements, net -N lines
- Documentation: N updates
### Branch Status
- Project branch: feat/batch-<name>
- Base branch: <main branch>
- Ready to mergeUser decides next steps: merge to main, further work, or discard.
The orchestrator maintains:
Sequential execution:
Context management:
/implement workflow within each ticket manages its own agent lifecycleFresh state per ticket:
/implement workflow starts from scratch for each ticketRelationship to `/implement`:
/implement-batch is a higher-level orchestrator that runs /implement for each ticket/implement handles the full development cycle for a single ticket/implement-batch adds: batching, ordering, branching strategy, cross-cutting quality passesRelationship to `/scope`:
/scope creates tickets; /implement-batch consumes them/scope to plan and create tickets, then /implement-batch to implement the batchRelationship to `/refactor`, `/tidy-docs`:
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.