What is true-skills test-plan.md?

A set of instructions for planning a testing cycle from quality goals, risks, requirements, and available scope. It represents the executable plan with a named folder and test suite linked to a sprint or release.

Finding coverage gaps, choosing and prioritizing test work, and building the folders and suites that make a cycle runnable.

It gives the team a concrete set of tests to run while making clear that some formal release and test-plan records must be created in Katalon's user interface.

How katalon-labs/true-skills configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to katalon-labs/true-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/katalon-labs/true-skills/main/.kiro/steering/test-plan.md

Clone the repo

git clone --depth 1 https://github.com/katalon-labs/true-skills

Made for: Kiro.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-plan/github.svg)](https://agentmods.dev/instructions/katalon-labs/true-skills/test-plan)

Your own site

<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/test-plan"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-plan/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/katalon-labs/true-skills/test-plan"><img src="https://agentmods.dev/badge/instructions/katalon-labs/true-skills/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,373 This file is loaded in full into every session.

When invoked 1,373 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.01373	$0.01373
Opus 5.5	$0.00549	$0.00549
Sonnet 5.5	$0.00275	$0.00275
Haiku 4.5	$0.00137	$0.00137

Measured 1mo ago against content hash ce2b981cb670, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

true-skills test-plan.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.kiro/steering/test-plan.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Katalon Test Plan

Use this skill for the planning stage of the Katalon lifecycle: turn quality goals into a scoped, risk-prioritized, executable plan. The output is a plan the team can act on plus the folder/suite/release structure that makes it runnable. Prefer Katalon MCP tools for platform data; use the human as a tool when scope, risk appetite, or release target cannot be resolved safely.

Availability Boundary

State the boundary before promising a plan:

Available via MCP: resolve scope (list_projects, list_repositories, find_iterations), read requirement coverage and gaps (fetch_requirement_data, find_requirements, find_test_cases_by_requirement), and build the executable plan structure (manage_test_folder, manage_test_suite, add cases to suites).
Not directly available: create a Release or Build entity, create a formal Test Plan entity, or author release gates through MCP. These live in the TestOps UI.
Workaround (the MCP-legal test plan): a named folder + test suite associated with a sprint/release is the executable plan. Create it, populate it, and report it as the plan of record.

Planning Workflow

+---------------+     +----------------------+     +----------------------+
| Resolve scope | --> | Read coverage + risk | --> | Prioritize what first|
+---------------+     +----------------------+     +----------------------+
        |                        |                             |
        v                        v                             v
+---------------+     +----------------------+     +----------------------+
| Propose plan  | --> | Build folder + suite | --> | Associate sprint/rel |
+---------------+     +----------------------+     +----------------------+

Steps and tool rules

Resolve scope. list_projects -> list_repositories. If exactly one matches the user's wording or context, use it. Use find_iterations to bind the plan to a sprint/release when named.
Read coverage and gaps. Use fetch_requirement_data for requirement coverage status and find_test_cases_by_requirement to see which requirements already have cases. find_requirements / read_requirement when requirement keys are supplied.
Prioritize by risk and evidence. Rank scope using: requirement coverage gaps first, then high-change/high-traffic areas, then areas with historically unstable tests (defer stability detail to test-review). State the risk basis; do not invent traffic numbers the MCP does not return.
Propose the plan in chat. Objectives, in-scope / out-of-scope, coverage matrix (requirement -> planned cases), risk ranking, target environments, and the suite/folder structure you will create.
Materialize the executable structure. manage_test_folder for the plan folder, manage_test_suite for the runnable suite, add the selected/known cases. Reuse an existing folder/suite when one already matches instead of creating a duplicate.
Verify and report. read_test_suite to confirm; report the plan of record with the suite as the executable artifact and the open gaps to fill next.

Read the full file on GitHub · 109 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 109 lines · 1,373 tokens per session scan A ce2b981cb670

Subscribe to this mod's changes

true-skills test-plan.md is an instructions file published in the GitHub repository katalon-labs/true-skills (10 stars, last pushed 4d ago), licensed MIT. It adds 1,373 tokens to every session, about $0.0055 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.

Claude Code Planning Testing agent-skills agentic-ai ai-testing cursor github-copilot

understudy qa-engineer.instructions.md

Instructions for erniker/understudy, covering qa engineer — quality assurance specialist instructions, 🎯 recommended model: {{modelqa}}, (use /model in cli or model picker in vs code), identity and expertise.

erniker/understudy · 1,600 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

true-skills: Instructions file for Kiro