Test Manager

Version: 0.1.0 Repository: https://github.com/yysun/project-manager Source: https://github.com/yysun/project-manager/tree/main/skills/test-manager

Manage testing as durable workspace state through strategy → design → readiness → execution → triage → reporting → closure.

The default test root is <cwd>/.tests. Its direct child directories are test suites. Do not search upward, use a repository as implicit test state, or create a parallel test root when the user has not selected one.

Operating boundary

• Own test strategy, risk coverage, suite and case design, readiness, execution records, evidence, defect linkage, traceability, quality gates, and reporting.
• Own .tests state, not product-delivery coordination, task dependencies, or .projects state. When both kinds of state exist, keep their authority separate and report QA evidence across that boundary only when the user's workflow requires it.
• Test the requested system through the appropriate surface. For visible UI business testing, operate the UI and use API/database access only as read-only secondary evidence unless the user authorizes another method.
• For an authorized visible-UI execution, complete the entry gate and then open and operate the requested browser, preferring the in-app Browser when it is available and the user did not choose another surface. Planning, status review, and opening Studio do not by themselves authorize opening or changing the target system.
• Do not implement product fixes, mutate production data, create external tickets, or waive a quality gate unless the user explicitly asks.
• Treat permissions, environments, production writes, notifications, payments, and destructive actions as separate authorization boundaries.