Forge-Test-Execution

Executes planned test cycles and reports results with traceable evidence.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/Nealsch/ForgeOS --skill forge-test-execution-nealsch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Forge-Test-Execution
Source: https://github.com/Nealsch/ForgeOS/tree/main/Framework/05-Skills/04-Quality/Forge-Test-Execution
Command: npx skills add https://github.com/Nealsch/ForgeOS --skill forge-test-execution-nealsch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Test execution often happens ad hoc, with results recorded inconsistently and no traceable evidence linking outcomes to test cases, requirements, or builds. This Skill provides a structured procedure for running planned test cycles, recording outcomes, capturing evidence, and reporting quality status to stakeholders. ## Core Features & Use Cases - Structured Test Cycle Execution: Confirms entry criteria, prepares environments and test data, and executes test cases against an approved test plan. - Evidence-Based Result Recording: Captures outcomes, evidence, and observations for every test case so results are reviewable and traceable to requirements and builds. - Honest Status Reporting: Reports pass, fail, blocked, and skipped states accurately, summarizes cycle results against exit criteria, and hands confirmed failures to defect management. - Use Case: A QA lead running a regression cycle on a release candidate uses this Skill to execute the planned suites, record evidence per test case, track progress against the plan, and publish a test summary report for the release readiness assessment. ## Quick Start Use the Forge-Test-Execution skill to run the current test cycle against the approved test plan and produce a test execution report with evidence for each test case.

Frequently Asked Questions about Forge-Test-Execution

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

FAQPage Schema
How do I run a structured test execution cycle against a test plan?▼

Confirm entry criteria and build readiness, prepare the environment and test data, then execute test cases as defined in the approved plan. Record outcomes and evidence for each case, track progress, and summarize results against exit criteria.

How should test results and evidence be recorded during execution?▼

Record the outcome, evidence, and observations for every test case so each result traces back to the test case, requirement, and build under test. Use the Test-Plan template as the baseline for capturing cycles, results, and status.

What inputs are needed before starting test execution?▼

You need an approved test plan, test strategy and quality objectives, test cases and scenarios, environment access and configuration, test data, the build under test, entry criteria confirmation, and known defects or open issues.

When should I not use a test execution skill?▼

Do not use it for defining test strategy, planning cycles, designing test cases, triaging or resolving defects, root-cause analysis, release readiness decisions, or debugging. Those activities belong to their respective separate skills.

How are failed tests handled after execution?▼

Failed and blocked tests are reported with supporting evidence and handed to defect management for triage and resolution. Test execution itself does not resolve defects or decide release readiness.