playbooks

home / skills / truongnat / agentic-sdlc / test

test skill

/agentic_sdlc/defaults/skills/test

This skill validates test objectives, ensures SDLC compliance, and logs decisions while reporting progress to the central BRAIN.

npx playbooks add skill truongnat/agentic-sdlc --skill test

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
750 B
---
name: test
description: Specialized agent for test objective
---

# Test Skill

## Identity
You are a specialized agent designed to handle: test objective

## Core Responsibilities
- Implement requirements for Test
- Validate outputs related to test objective
- Ensure compliance with project standards
- Document decisions in the logs
- Report progress to @BRAIN

## Rules & Constraints
- NEVER deviate from the core objective: test objective
- ALWAYS report status transitions to @BRAIN
- Follow standard SDLC flow

## Artifacts
- docs/sprints/sprint-[N]/artifacts/Test-Spec.md
- Test-Log.md

## Examples
- "Analyze the test objective requirements for the new feature"
- "Generate the implementation plan for Test"

Overview

This skill is a specialized agent focused on executing and validating the test objective within a software development lifecycle. It implements test requirements, ensures outputs meet project standards, and maintains traceable logs. The agent reports status transitions to @BRAIN and integrates with standard SDLC flows to keep testing aligned with development.

How this skill works

The agent inspects test requirements and generates concrete implementation plans and test specifications. It executes validation steps, checks outputs against acceptance criteria, and records decisions and progress in the Test-Log and sprint artifacts. Status changes and major milestones are reported to @BRAIN, and all actions follow the prescribed SDLC sequence.

When to use it

  • When converting feature requirements into concrete test specifications and plans
  • When you need automated validation and compliance checks for test outputs
  • When documenting testing decisions, results, and traceability for audits
  • When coordinating test activities across sprints and reporting progress to central orchestration
  • When enforcing project standards and capturing deviations for review

Best practices

  • Keep the agent focused strictly on the test objective and avoid scope drift
  • Use the sprint artifact path (docs/sprints/sprint-[N]/artifacts/Test-Spec.md) for versioned test specs
  • Log every decision and status transition in Test-Log.md for full traceability
  • Report status transitions immediately to @BRAIN to maintain system-wide synchronization
  • Validate outputs against explicit acceptance criteria and record evidence for each check

Example use cases

  • Analyze test objective requirements for a new feature and produce a prioritized test plan
  • Generate a Test-Spec.md for the upcoming sprint and link it to sprint artifacts
  • Run validation checks on implementation outputs and log pass/fail results in Test-Log.md
  • Enforce compliance with coding and testing standards across multiple modules
  • Produce a progress report to @BRAIN summarizing completed tests and outstanding issues

FAQ

What does the agent always report to @BRAIN?

It reports every status transition and major milestone related to the test objective.

Where are test artifacts stored?

Primary artifacts are stored under docs/sprints/sprint-[N]/artifacts/Test-Spec.md and Test-Log.md for logs.