qa-author-by-task

Stars8

Forks0

UpdatedJuly 7, 2026 at 13:21

QA-Author by-task mode procedure. Use when QA-Author is dispatched for a master-plan task after TL, and after design-confirmed for UI tasks, to author task-scoped structural/api/e2e/functional test cases under docs/test-cases/by-task/<task-id>/ and coordinate visual-spec generation for UI tasks.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

evolplus

evolplus/talos

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

2 files

SKILL.md

readonly

name	qa-author-by-task
description	QA-Author by-task mode procedure. Use when QA-Author is dispatched for a master-plan task after TL, and after design-confirmed for UI tasks, to author task-scoped structural/api/e2e/functional test cases under docs/test-cases/by-task/<task-id>/ and coordinate visual-spec generation for UI tasks.
agents	["qa-author"]
sdlc_phase	qa
owner	Platform Eng
status	active

QA Author By-Task

Use

Use this skill for QA-Author by-task mode. Load test-case-author for TC format, ui-test-execution for executable specs, and visual-spec-author before writing structural tests for UI tasks.

Inputs

Task file under docs/plan/phase-*/tasks/<task-id>.md
Linked US/FR files
docs/architecture.md
Frozen API contracts for BE/BE+FE tasks
docs/uiux/handoffs/<task-id>.md and docs/instrumentation-contract.md for UI tasks
Existing by-us test cases for linked US IDs

Preconditions

TL has linked US IDs and FR IDs.
UI tasks have design-confirmed and a handoff on main.
FE tasks dependent on BE contracts have frozen API contracts.
Missing preconditions cause NEEDS_CONTEXT/blocked return; do not author partial task TCs silently.

Procedure

Verify by-us coverage exists for each linked US. If missing, file an open issue and continue only for task-specific layers that can be authored safely.
Determine required task layers:
- api.md for BE or BE+FE contract/API work;
- structural.md for UI tasks;
- e2e.md for multi-system or cross-surface flows;
- functional.md only for task-specific behavior not covered by by-us.
For UI tasks, run visual-spec-author first. Structural TCs derive from docs/uiux/visual-specs/<task-id>.md, not from ad-hoc Figma interpretation.
For API tests, read both the FR file and frozen API contract. If they disagree, file an open issue; do not silently let one override the other.
Author markdown TCs under docs/test-cases/by-task/<task-id>/.
Author executable specs at every TC's Executable: path using the project runner conventions.
Ensure runner test names start with the TC ID.
Emit plan-update.json with track: "qa" and by-task notes.

Hard Rules

Never author by-task cases into by-us paths or the reverse.
Never invent missing API contract behavior.
Never write structural UI tests before visual spec exists.
Every executable TC needs a real spec file.
Commit before signaling ready-to-finalize.

More from this repository

same repository

be-framework-coding-standard

evolplus/talos

Standardized backend implementation guidance for BE Dev using the SRS-declared Backend-Track and Backend-Framework. Use when coding, refactoring, or reviewing backend web APIs, BFFs, microservices, workers, jobs, or service integrations in TypeScript with Express, TypeScript with NestJS, Python with FastAPI, Java with Spring Boot, .NET Core C#, Pure Golang, Java Core, Golang with Gin, Golang with Fiber, Golang with Echo, or Golang with Kratos; BE Dev reads docs/SRS.md Backend-Track and Backend-Framework plus §3.4.5 Source Layout, then selects the matching reference so routing, layering, contracts, validation, observability, errors, transactions, and tests match the chosen stack.

2026-07-308

local-deployment

evolplus/talos

How DevOps composes the local Docker environment for QA and operator trials, including port probing, secret-safe env discovery, test-only runtime-reset endpoint verification for direct-DB fixtures, QA deploy-report fields, and human trial URLs without editing project Compose files.

2026-07-308

playwright-author

evolplus/talos

Concrete how-to for QA-Author writing Playwright specs from markdown TCs — project layout, full-state resets for direct-DB fixtures and caches, parallel-worker isolation, contract-aware URL assertions, network mocking, retries, traces, and visual diffs. Consult after `ui-test-execution` when the target surface is web AND the project uses Playwright.

2026-07-308

qa-execution-runner

evolplus/talos

QA-Exec run contract for executing authored test cases against the deployed build. Use when QA-Exec is dispatched for a task in-test to gather by-us/by-task test cases, check executable specs and instrumentation coverage, invoke the proper runner, execute UI tiers, validate visual specs, route failures, and write docs/qa-reports/<task-id>.md plus artifacts.

2026-07-308

sdlc-loop

evolplus/talos

Codex-native orchestration entrypoint for Evo Talos. Use when the user asks for /sdlc-loop, sdlc-loop, start project, continue the SDLC loop, run the governed workflow, or auto-dispatch eligible SDLC work until the next gate. Acts as the Codex equivalent of the Claude slash command.

2026-07-308

ui-test-execution

evolplus/talos

Framework-agnostic principles for executing UI tests against the running build — TC-to-spec mapping, selectors, full-state fixture reset across DB/cache/worker state, shared-resource parallelism, determinism, and visual diffs. Consult when QA-Author writes executable specs or QA-Exec invokes a runner against a deployed build.

2026-07-308

name	qa-author-by-task
description	QA-Author by-task mode procedure. Use when QA-Author is dispatched for a master-plan task after TL, and after design-confirmed for UI tasks, to author task-scoped structural/api/e2e/functional test cases under docs/test-cases/by-task/<task-id>/ and coordinate visual-spec generation for UI tasks.
agents	["qa-author"]
sdlc_phase	qa
owner	Platform Eng
status	active

QA Author By-Task

Use

Use this skill for QA-Author by-task mode. Load test-case-author for TC format, ui-test-execution for executable specs, and visual-spec-author before writing structural tests for UI tasks.

Inputs

Task file under docs/plan/phase-*/tasks/<task-id>.md
Linked US/FR files
docs/architecture.md
Frozen API contracts for BE/BE+FE tasks
docs/uiux/handoffs/<task-id>.md and docs/instrumentation-contract.md for UI tasks
Existing by-us test cases for linked US IDs

Preconditions

TL has linked US IDs and FR IDs.
UI tasks have design-confirmed and a handoff on main.
FE tasks dependent on BE contracts have frozen API contracts.
Missing preconditions cause NEEDS_CONTEXT/blocked return; do not author partial task TCs silently.

Procedure

Verify by-us coverage exists for each linked US. If missing, file an open issue and continue only for task-specific layers that can be authored safely.
Determine required task layers:
- api.md for BE or BE+FE contract/API work;
- structural.md for UI tasks;
- e2e.md for multi-system or cross-surface flows;
- functional.md only for task-specific behavior not covered by by-us.
For UI tasks, run visual-spec-author first. Structural TCs derive from docs/uiux/visual-specs/<task-id>.md, not from ad-hoc Figma interpretation.
For API tests, read both the FR file and frozen API contract. If they disagree, file an open issue; do not silently let one override the other.
Author markdown TCs under docs/test-cases/by-task/<task-id>/.
Author executable specs at every TC's Executable: path using the project runner conventions.
Ensure runner test names start with the TC ID.
Emit plan-update.json with track: "qa" and by-task notes.

Hard Rules

Never author by-task cases into by-us paths or the reverse.
Never invent missing API contract behavior.
Never write structural UI tests before visual spec exists.
Every executable TC needs a real spec file.
Commit before signaling ready-to-finalize.