Skip to content

/test-plan

Testing class

Writes test source into the repo and executes it — the only class that does both. Shared rules: CONVENTIONS-testing.md.

Ingests a requirement from a connected tracker (Linear/Jira/Notion/GitHub Issues) or pasted markdown, consumes /test-gap-finder's coverage output rather than reimplementing it, and emits structured case objects covering equivalence classes, boundaries, negative paths and authz. Advises only: it writes no spec and no file.

At a glance

Run it /test-plan
Class testing
Version 0.1.0
Author navjyotnishant
Needs a connected PM tracker (MCP) · /test-gap-finder · gitleaks or trufflehog or detect-secrets
Source skills/test-plan/SKILL.md

What it needs, and what happens without it

Every tool is detected at runtime — none is installed for you.

Tool Without it
a connected PM tracker (MCP) paste-ready fallback — the user pastes the requirement as markdown (§A5)
/test-gap-finder plan against the requirement alone, and say the plan may duplicate existing tests
gitleaks or trufflehog or detect-secrets BLOCK before publishing anything

Agents it spawns

This skill spawns no subagents — it runs inline.

The procedure

The executable steps live in the skill file itself and are deliberately not reproduced here: they are instructions to the model at runtime, not documentation.

Read test-plan/SKILL.md →