qa-project-context

Create a QA context file at .agents/qa-project-context.md.

64|12|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/petrkindlmann/qa-skills --skill qa-project-context
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-project-context
Source: https://github.com/petrkindlmann/qa-skills/tree/main/skills/qa-project-context
Command: npx skills add https://github.com/petrkindlmann/qa-skills --skill qa-project-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates and fills a single, authoritative QA context file (.agents/qa-project-context.md) to prevent redundant discovery questions and ensure consistent guidance across all QA skills.

Core Features & Use Cases

  • Centralizes product context, tech stack, CI/CD, environments, risk areas, and team structure in one place.
  • Enables cross-skill consistency by providing a single source of truth for automation strategy.
  • Accelerates onboarding by surfacing the entire QA context at the start of a project.

Quick Start

Run qa-project-context to generate and populate the context file at .agents/qa-project-context.md.

Frequently Asked Questions about qa-project-context

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

FAQPage Schema
How do I centralize QA project context for automation?

Centralize QA project context by running a discovery process that generates a root file (.agents/qa-project-context.md) containing product info, tech stack, CI/CD, and environments. This file acts as a single source of truth to align downstream automation skills.

Why does my QA automation keep asking repetitive discovery questions?

Repetitive discovery questions occur when project context is scattered. Creating a centralized QA context file eliminates redundant onboarding queries by providing a single source of truth for product, tech stack, and governance details across all skills.

What is the best way to align multiple QA skills on a new project?

Align multiple QA skills by consolidating product context, testing environments, and risk areas into a single authoritative file. This ensures every skill follows a consistent discovery path and reads identical context data.

Can I use a centralized QA context file for ongoing project efforts?

Yes, you can use a centralized QA context file for ongoing efforts. It applies to both new projects and existing workflows where multiple QA skills are used, continuously providing a single source of truth for governance and tech stack updates.

How do I accelerate QA onboarding for automation projects?

Accelerate QA onboarding by surfacing the entire project context at the start. A centralized context file immediately provides new team members and automation skills with tech stack, CI/CD, and risk area details without manual discovery.