agentleFS
Sign inStart free
ww-w-aiww-w-ai/bkit-gemini/skills/batch/SKILL.md

batch

Skill66 starsChanged 7 months agoApache-2.0View on GitHub

Process multiple features or tasks in parallel. Batch execution of PDCA commands across features.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use verify.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Validate: Check that each feature has prerequisites for the requested command

    line 45
  2. Distinctive:

    Fail-forward: If one feature fails, remaining features still execute

    line 58
  3. Very specific:

    Retry option: Use --retry-failed to re-run only the failed features

    line 60
  4. Distinctive:

    If no features are specified, batch will auto-discover features from:

    line 83

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Batch Skill

Process multiple features or tasks in parallel. Execute PDCA commands across multiple features in a single invocation.

Usage

/batch plan user-auth payment-system notification
/batch design user-auth payment-system
/batch analyze user-auth payment-system notification search
/batch report user-auth payment-system

Execution Model

  1. Parse: Extract the command and feature list from arguments
  2. Validate: Check that each feature has prerequisites for the requested command
  3. Execute: Process each feature sequentially, tracking progress via Task Tracker
  4. Report: Output a summary table showing status for each feature

Progress Tracking

Each feature creates a Task Tracker entry:

  • Task subject: [Batch {command}] {feature}
  • Status updates as each feature completes
  • Final summary shows pass/fail per feature

Error Handling

  • Fail-forward: If one feature fails, remaining features still execute
  • Error log: Failed features are collected and reported at the end
  • Retry option: Use --retry-failed to re-run only the failed features
/batch --retry-failed analyze user-auth payment-system

Output Format

Batch Execution Summary
----------------------------------------------
Command: plan
Features: 4 total | 3 success | 1 failed
----------------------------------------------
  user-auth        [OK]   docs/01-plan/features/user-auth.plan.md
  payment-system   [OK]   docs/01-plan/features/payment-system.plan.md
  notification     [OK]   docs/01-plan/features/notification.plan.md
  search           [FAIL] Missing prerequisite: project scope undefined
----------------------------------------------

Feature Discovery

If no features are specified, batch will auto-discover features from:

  1. .pdca-status.json primary and secondary features
  2. docs/01-plan/features/*.plan.md existing plan files
  3. docs/02-design/features/*.design.md existing design files
/batch analyze          # auto-discovers all features
/batch report --all     # explicitly process all known features

Combination with Other Skills

Batch works with any PDCA subcommand and can be combined with loop:

/loop 1h batch analyze user-auth payment-system

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free