Use when starting a conversation in a project that has Argus installed — introduces available QA skills and guides setup
The 100-eyed watchman for your test automation.
Argus is a skill pack that gives you QA superpowers. Each skill handles a specific part of the testing lifecycle. You control the workflow — invoke skills when you need them.
If the project doesn't have a .argus/ folder yet, help the user set one up:
.argus/ directory in the project root.argus/config.yaml from answersReference the example config at config/config.example.yaml for valid values.
| Skill | Invoke when... |
|---|---|
test-planner | You need to define test scope (browsers, devices, environments) |
spec-analyzer | You have a spec or ticket to analyze into a feature file |
| Skill | Invoke when... |
|---|---|
test-case-creator | You need test cases generated from a feature file |
test-data-generator | You need realistic test data for your test cases |
page-object-generator | You need automation code (page objects + test specs) |
| Skill | Invoke when... |
|---|---|
flow-composer | You need to chain features into E2E flows |
suite-composer | You need to build a test suite (smoke, sanity, regression, full) |
| Skill | Invoke when... |
|---|---|
ui-verifier | You need to compare a design image against the live app |
accessibility-checker | You need WCAG compliance checks |
| Skill | Invoke when... |
|---|---|
test-runner | You need to execute automation tests |
test-maintainer | You need to check if existing tests are still valid |
| Skill | Invoke when... |
|---|---|
bug-reporter | A test failed and you need to draft a bug ticket |
report-generator | You need a sprint, feature, daily, or release report |
report-exporter | You need to export test cases, discovery reports, or bug reports to Excel or HTML for sharing with stakeholders |
| Skill | Invoke when... |
|---|---|
jira-connector | You need to pull a ticket from Jira |
exploratory-tester | You need to explore an existing app to understand its flows |
New project: test-planner → spec-analyzer → test-case-creator → page-object-generator → flow-composer
Existing project: exploratory-tester → test-planner → spec-analyzer → test-case-creator → page-object-generator
Quick test cases: spec-analyzer → test-case-creator
Before release: suite-composer (regression) → test-runner → report-generator (release readiness)
.argus/config.yaml).All generated artifacts live in .argus/:
.argus/
├── config.yaml ← Project configuration
├── specs/ ← Input spec documents (organized per feature)
│ └── <feature-name>/ ← SRS, wireframes, API contracts, designs
├── features/ ← Analyzed feature files (output of spec-analyzer)
├── test-cases/ ← Generated test cases
├── test-data/ ← Generated test data
├── flows/ ← E2E flow definitions
├── suites/ ← Test suite definitions
├── automation/ ← Generated page objects and test specs
│ ├── web/
│ ├── mobile/
│ └── api/
├── artifacts/ # Presentation-ready HTML and Excel exports
└── reports/ ← All reports
├── analysis/ ← Spec analysis reports
├── discovery/
├── ui-verification/
├── accessibility/
├── maintenance/
└── bugs/