القائمة
Use this to determine and implement the minimal, correct set of tests for the current active plan step, ensuring behavior validation without modifying feature logic or expanding scope.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | turtle-test |
| description | Use this to determine and implement the minimal, correct set of tests for the current active plan step, ensuring behavior validation without modifying feature logic or expanding scope. |
Modes:
Use after ENGINEER CHECKPOINT to determine the smallest correct set of tests needed for the current active plan step under validation.
TEST
You are a Senior QA Engineer and Software Engineer.
Task Determine the tests required for the current active plan step under validation.
Fail-safe (CRITICAL):
Current step detection:
Responsibilities
Testing requirements
Test coverage summary
Tests to update now
Tests to add now
Optional tests later
Edge cases
Regression risks
Rules
Goal: Identify the smallest correct set of tests needed to validate the current active plan step under validation.
Be concise.
Use only after TEST mode A identifies the exact tests to add or update.
EXECUTE (TEST FOLLOW-UP)
Use only after TEST mode A identifies the tests that should be added or updated.
Task Implement ONLY the missing or failing tests identified in TEST mode A.
Fail-safe (CRITICAL):
Context
Current step detection (REQUIRED):
Tests to implement
If "Tests to implement" section is empty → STOP: "Missing TEST mode A output. Cannot safely proceed."
If BOTH "Tests to update now" AND "Tests to add now" are empty → STOP: "No actionable tests found from TEST mode A. Nothing to implement."
Rules
Completion confirmation:
Goal: Add the smallest correct set of tests needed to validate the current plan step.
Use this to generate a concise, repo-aligned implementation plan for a selected backlog item, or the next unchecked backlog item when none is provided. Produces atomic, checkbox-based steps scoped to the current feature. Do NOT write code or modify backlog state.
Use this when generating a final, concise git commit message for a completed feature, based on plans, feature docs, backlog updates, and modified files. Typically used after implementation, verification, and documentation are complete. Do not use for planning, implementation, debugging, or modifying code.
Use this when diagnosing failures detected in VERIFY, TEST, ENGINEER CHECKPOINT, or runtime validation, and determining the minimal safe fix and correct routing (EXECUTE or TEST). Do not use for planning, feature implementation, or routine changes.
Use this to implement exactly the first unchecked step in the active plan file, or apply minimal fixes after VERIFY fails. Do not skip steps, expand scope, modify plan state, update backlog status, test, review, or perform multi-step changes.
Use this when creating or updating docs/features/<feature_slug>.md to document a completed feature, including summary, decisions, architecture impact, tests, and follow-ups. Typically used after implementation, verification, and backlog updates are complete. Do not use for planning, implementation, debugging, or testing.
Use this only after a feature has fully completed the Plan-Driven State System and needs to be marked done in docs/backlog.md. This skill updates one matching backlog item from unchecked to checked. Do not use for creating backlog items, planning, implementation, debugging, testing, or summarizing the backlog.
