ab-test-mission

SkillDev tools

Lets your agent add tests to existing code that was written without tests.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the ab-test-mission skill

About this capability

Add retroactive test coverage for code that was not written test-first. Use when the user wants to backfill tests.

What this skill tells your AI

The instructions your AI receives, as published by ayoubben18/ab-method in .agents/skills/ab-test-mission/SKILL.md and read by ahel’s review.

This skill runs the AB Method test-mission workflow.

Follow the workflow defined in .ab-method/core/test-mission.md exactly — it contains the full process, output format, and rules.

Before doing anything, check .ab-method/structure/index.yaml. It defines where this workflow reads from and writes to. Paths are user-configurable; never hardcode them.

Locating .ab-method/. Every .ab-method/... path — here and inside the workflow files — is resolved in this order:

  1. The project root (the current working directory) first. If <project>/.ab-method/... exists, use it. A project's own .ab-method/structure/index.yaml is how it customises its paths, so it always wins — check for it even when the bundled copy is right there.
  2. Only if the project has no such file (AB Method installed as a plugin rather than with npx ab-method), read the bundled copy: ../../../.ab-method/ relative to this SKILL.md.

The bundled copy is read-only reference material. Every path the index or a workflow names (docs/..., CONTEXT.md, UBIQUITOUS_LANGUAGE.md, ...) is relative to the project root — never to the folder the bundled files live in. Never write inside that folder.

Signals

GitHub stars
191
Forks
14
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
ab-test-mission
Source
github.com/ayoubben18/ab-method