project-orchestrator:test-lead

Orchestrate serial browser test execution and update living state documents.

Updated Feb 15, 2026

Search Tags:#automation #workflow #orchestration #browser-testing #design-doc #living-state #test-executor

Ready to run

npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-test-lead

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-orchestrator:test-lead
Source: https://github.com/GigaFyde/project-orchestrator/tree/main/skills/test-lead
Command: npx skills add https://github.com/GigaFyde/project-orchestrator --skill project-orchestrator-test-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates browser test execution from a design doc's Test Plan by serially spawning test-executor agents, collecting results, updating the living state doc, and presenting a summary.

Core Features & Use Cases

Serial execution: spawn a single test-executor at a time to ensure deterministic results and simpler debugging.
Living state updates: automatically append test results to the living state document for traceability.
Plan-driven workflow: integrate with design-doc driven plans to parse App Context, prerequisites, scenarios, and dependencies.

Quick Start

Initiate a design-doc plan run and let the system spawn a single test-executor to validate the workflow.

Frequently Asked Questions about project-orchestrator:test-lead

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

FAQPage Schema

How do I orchestrate browser tests sequentially from a design doc test plan?▼

Browser test orchestration from a design doc is handled by serially spawning test-executor agents, collecting results, and updating the living state document for traceability and post-run reporting.

What is serial browser test execution and when do I need it?▼

Serial browser test execution spawns a single test-executor at a time to ensure deterministic results and simpler debugging. You need it when test scenarios have dependencies requiring sequential validation.

Can I use a design doc to drive automated browser test workflows?▼

Yes, the plan-driven workflow integrates with design docs to parse App Context, prerequisites, scenarios, and dependencies, automatically applying them to orchestrate browser test execution.

How do I maintain living state and traceability during browser test runs?▼

Living state traceability is maintained by automatically appending test results to the living state document during orchestration, ensuring all test execution outcomes are recorded for post-run reporting.

Does browser test orchestration handle dependency management between test scenarios?▼

Yes, dependency handling is enforced during sequential test execution, ensuring scenarios are validated in order and that prerequisite conditions are met before spawning the next test-executor agent.

What are the limitations of serial test orchestration for browser automation?▼

Serial test orchestration limits parallel execution, meaning tests run one at a time. This ensures deterministic results and simpler debugging but may increase overall execution time for large test suites.