user-test

Convert manual_test_script outputs into human checklists or agent prose.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sofer/.agents --skill user-test
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: user-test
Source: https://github.com/sofer/.agents/tree/main/skills/user-test
Command: npx skills add https://github.com/sofer/.agents --skill user-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reformat the manual code-review test script into an executable, human- or agent-friendly format to streamline testing and validation.

Core Features & Use Cases

  • Reformatting: convert structured manual_test_script outputs into markdown checklists for humans or prose instructions for agents.
  • Format selection: automatically determine or accept a preferred output format based on project config.
  • Results logging: store per-story test results in the .sdlc directory and gate progress to commit:pr.
  • Versatility: usable in CI pipelines or manual testing sessions for consistent QA communications.

Quick Start

Convert the code-review manual_test_script into the chosen format (human or agent) and save the formatted output to the project's .sdlc/stories location.

Frequently Asked Questions about user-test

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a manual test script into an executable format for CI pipelines?▼

You can convert a manual test script by reformatting the code-review manual_test_script output into either a human-readable markdown checklist or agent-ready prose, saving the structured instructions to the .sdlc/stories directory.

What is the best way to structure manual testing instructions for both humans and agents?▼

The best way to structure manual testing instructions is to reformat code-review outputs into portable test formats, automatically selecting between a human-checklist or agent-ready prose based on your project configuration.

Does this test formatting process store results and enforce gate transitions to commit pr?▼

Yes, the test formatting process stores per-story test results in the .sdlc/stories directory and enforces gate transitions to commit:pr, ensuring structured progress validation before code changes proceed.

Can I use the reformatted test script for automated QA workflows and manual testing sessions?▼

Yes, you can use the reformatted test script for automated QA workflows and manual testing sessions, as it generates portable, structured test instructions derived from code-review outputs suitable for both contexts.

When do I need to reformat a code-review manual test script into agent instructions?▼

You need to reformat a code-review manual test script into agent instructions when your CI pipelines or manual testing workflows require structured, portable test instructions that automate validation and enforce gate transitions.