qa-skills 3.0.0 → 3.1.0

package/skills/qa-shortcut-integration/references/api-patterns.md

@@ -1,126 +0,0 @@
-# Shortcut API Patterns
-
-## Base URL and Headers
-
-```
-Base URL: https://api.app.shortcut.com/api/v3
-Headers:
-  Shortcut-Token: <SHORTCUT_API_TOKEN>
-  Content-Type: application/json
-```
-
-## Stories
-
-### Create Story
-
-```
-POST /api/v3/stories
-```
-
-**Request body:**
-```json
-{
-  "name": "Login fails when password contains special chars",
-  "description": "**Expected:** User can log in with special chars in password.\n**Actual:** 500 error.\n**Steps:** 1. Enter password with @#$ 2. Click Login",
-  "story_type": "bug",
-  "project_id": 123,
-  "labels": [{"name": "auth"}, {"name": "severity-critical"}],
-  "workflow_state_id": 50000001,
-  "external_links": [
-    {"url": "https://example.com/test-case/TC-001", "title": "Test Case TC-001"}
-  ]
-}
-```
-
-**Story types:** `bug`, `feature`, `chore`
-
-### Get Story
-
-```
-GET /api/v3/stories/{story_id}
-```
-
-### Update Story
-
-```
-PUT /api/v3/stories/{story_id}
-```
-
-**Partial update example:**
-```json
-{
-  "workflow_state_id": 50000002,
-  "labels": [{"name": "verified"}],
-  "description": "Original description + verification notes"
-}
-```
-
-### Search Stories
-
-```
-GET /api/v3/search/stories?query=login&project_id=123
-```
-
-Query supports text search, filters by project, epic, iteration, label.
-
-## Epics
-
-### List Epics
-
-```
-GET /api/v3/epics
-```
-
-Returns epics with `id`, `name`, `state`. Use to resolve epic by name for story creation.
-
-### Link Story to Epic
-
-Include `epic_id` in create/update story request.
-
-## Iterations
-
-### List Iterations
-
-```
-GET /api/v3/iterations
-```
-
-Returns iterations (sprints) with `id`, `name`, `status`. Use to assign stories to current sprint.
-
-### Assign Story to Iteration
-
-Include `iteration_id` in create/update story request.
-
-## Workflows
-
-### List Workflow States
-
-```
-GET /api/v3/workflows
-```
-
-Returns workflow states per project. Map QA status (e.g., "Open", "In Progress", "Done") to `workflow_state_id`.
-
-## Labels
-
-Labels are created in Shortcut UI or via API. Use exact names when adding to stories:
-
-```json
-"labels": [{"name": "auth"}, {"name": "severity-critical"}, {"name": "test-type-e2e"}]
-```
-
-## External Links
-
-Add links to test cases, requirements, evidence:
-
-```json
-"external_links": [
-  {"url": "https://example.com/test/TC-001", "title": "Test Case TC-001"},
-  {"url": "https://example.com/req/REQ-42", "title": "Requirement REQ-42"}
-]
-```
-
-## Rate Limits
-
-- 200 requests per minute
-- Throttle bulk operations; use batch endpoints when available

package/skills/qa-shortcut-integration/references/field-mapping.md

@@ -1,66 +0,0 @@
-# QA Field → Shortcut Field Mapping
-
-## Bug Report (from qa-bug-ticket-creator)
-
-| QA Field | Shortcut Field | Notes |
-| -------- | -------------- | ----- |
-| Title | `name` | Direct mapping |
-| Description (expected/actual/steps) | `description` | Markdown; use headers for structure |
-| Severity | `labels` | e.g., `severity-critical`, `severity-major` |
-| Priority | `labels` | e.g., `priority-p1`, `priority-p2` |
-| Component/Module | `labels` | e.g., `auth`, `frontend`, `api` |
-| Environment | `description` | Append to description or comment |
-| Evidence (screenshots, logs) | `external_links` | Link to artifact URLs |
-| — | `story_type` | Always `bug` for bug reports |
-
-## QA Task (from qa-task-creator)
-
-| QA Field | Shortcut Field | Notes |
-| -------- | -------------- | ----- |
-| Title | `name` | Direct mapping |
-| Description + acceptance criteria | `description` | Markdown |
-| Task type (Dev/QA/Docs/Enhancement) | `story_type` | Dev→feature, QA→chore, Docs→chore, Enhancement→feature |
-| Component | `labels` | Component label |
-| Links to bug/requirement | `external_links` | Add URL + title |
-| — | `story_type` | `feature` or `chore` per task type |
-
-## Coverage Gap (from qa-coverage-analyzer)
-
-| QA Field | Shortcut Field | Notes |
-| -------- | -------------- | ----- |
-| Gap description (e.g., "Add tests for AuthService") | `name` | Concise |
-| Module/file, coverage % | `description` | Context |
-| Component | `labels` | e.g., `test-coverage-gap`, `auth` |
-| — | `story_type` | `chore` |
-
-## Flaky Test (from qa-flaky-detector)
-
-| QA Field | Shortcut Field | Notes |
-| -------- | -------------- | ----- |
-| Test name + "flaky" | `name` | e.g., "Login E2E test flaky" |
-| Pattern, frequency | `description` | Flaky pattern details |
-| Component | `labels` | e.g., `flaky-test`, `auth` |
-| — | `story_type` | `bug` |
-
-## Workflow State Mapping
-
-| QA Status | Shortcut workflow_state | Typical name |
-| --------- | ----------------------- | ------------ |
-| New/Open | Initial state | "To Do", "Backlog" |
-| In Progress | Mid-state | "In Progress", "Development" |
-| Ready for Test | Pre-done | "Ready for QA", "Review" |
-| Verified/Done | Done state | "Done", "Verified" |
-
-Resolve `workflow_state_id` from `GET /api/v3/workflows`; names vary by workspace.
-
-## Label Conventions
-
-| Category | Examples |
-| -------- | -------- |
-| Severity | `severity-critical`, `severity-major`, `severity-minor` |
-| Priority | `priority-p1`, `priority-p2`, `priority-p3` |
-| Component | `auth`, `frontend`, `api`, `checkout` |
-| Test type | `test-type-unit`, `test-type-e2e`, `test-type-api` |
-| QA-specific | `test-coverage-gap`, `flaky-test`, `docs-update` |
-
-Create these labels in Shortcut if they don't exist.

package/skills/qa-spec-auditor/SKILL.md

@@ -1,162 +0,0 @@
----
-name: qa-spec-auditor
-description: Living documentation auditor that compares requirements vs UI/behavior vs API contract vs test results to detect spec drift, outdated docs, and undocumented features.
-output_dir: reports/audit
-dependencies:
-  recommended:
-    - qa-requirements-generator
-    - qa-spec-writer
----
-
-# QA Spec Auditor
-
-## Purpose
-
-Compare "how it should be" vs "how it is" after each release or sprint. Detect spec drift, outdated documentation, undocumented features, and regression set optimization opportunities. Produce actionable drift reports with task suggestions for qa-task-creator.
-
-## Trigger Phrases
-
-- "Spec audit" / "Documentation audit for [release/sprint]"
-- "Spec drift" / "Detect drift between docs and implementation"
-- "Outdated documentation" / "Docs vs implementation comparison"
-- "Undocumented features" / "Find features not in specs"
-- "Requirements vs UI" / "Requirements vs API contract"
-- "Living documentation audit" / "Spec compliance check"
-- "Regression set optimization" / "Worn out tests" / "Test rotation"
-
-## Comparison Dimensions
-
-| Dimension | Source A | Source B | Detects |
-|-----------|----------|----------|---------|
-| **Requirements ↔ UI/behavior** | Requirements, specs | Live UI (Playwright MCP) | UI doesn't match spec; missing flows |
-| **Requirements ↔ API contract** | Requirements, specs | OpenAPI, actual endpoints | API drift; undocumented endpoints |
-| **Requirements ↔ Test results** | Requirements | Test cases, RTM, execution | Untested requirements; orphan tests |
-| **Documentation ↔ Implementation** | Docs, README, wikis | Code, UI, API | Outdated docs; undocumented behavior |
-
-See `references/audit-checklist.md` for checklists per dimension.
-
-## Detection Categories
-
-| Category | Description | Output Action |
-|----------|-------------|---------------|
-| **Outdated documentation** | Docs describe old behavior | Update docs |
-| **Undocumented features** | Implementation has features not in specs | Add to specs or create tests |
-| **Spec drift** | Behavior changed but docs not updated | Update docs or fix implementation |
-| **Regression set optimization** | "Worn out" tests (always pass, low value); suggest rotation | Suggest test rotation; prioritize high-value tests |
-
-See `references/drift-patterns.md` for common patterns and remediation.
-
-## Output Deliverables
-
-1. **Drift Report** — Per dimension: findings, severity, affected artifacts
-2. **Action Items** — Update docs / fix implementation / create tests
-3. **Task Suggestions** — Structured for qa-task-creator (doc updates, test creation, spec fixes)
-4. **Regression Set Recommendations** — Tests to rotate, prioritize, or deprioritize
-
-### Drift Report Template
-
-```markdown
-# Spec Audit — [Release/Sprint]
-
-## Summary
-| Dimension | Findings | Critical | Action Items |
-|-----------|----------|----------|--------------|
-| Req ↔ UI | N | X | [Count] |
-| Req ↔ API | N | X | [Count] |
-| Req ↔ Tests | N | X | [Count] |
-| Docs ↔ Impl | N | X | [Count] |
-
-## Findings by Dimension
-### Requirements ↔ UI
-- [Finding] — [Severity] — [Action]
-### Requirements ↔ API
-- [Finding] — [Severity] — [Action]
-### Requirements ↔ Tests
-- [Finding] — [Severity] — [Action]
-### Documentation ↔ Implementation
-- [Finding] — [Severity] — [Action]
-
-## Task Suggestions (for qa-task-creator)
-1. [Task type] — [Description] — [Owner]
-2. ...
-
-## Regression Set Recommendations
-- Rotate: [Tests that are "worn out"]
-- Prioritize: [High-value tests]
-- Deprioritize: [Low-value, stable tests]
-```
-
-## Workflow
-
-1. **Input:** Requirements, specs, OpenAPI/API docs, test cases/RTM, optional UI URL
-2. **Requirements ↔ UI:** Use Playwright MCP to explore UI; compare flows, elements, validation to spec
-3. **Requirements ↔ API:** Compare OpenAPI/spec to requirements; detect undocumented endpoints, schema drift
-4. **Requirements ↔ Tests:** Validate RTM; find untested requirements, orphan tests
-5. **Documentation ↔ Implementation:** Compare docs to code/UI/API; flag outdated sections
-6. **Regression optimization:** Analyze test history; identify always-pass, low-value tests; suggest rotation
-7. **Output:** Drift report, action items, task suggestions for qa-task-creator
-
-## MCP Tools Used
-
-- **Playwright MCP (cursor-ide-browser):** UI exploration, compare live behavior to spec
-- **GitHub MCP:** Change tracking, PR/commit history for docs and code
-
-## Integration with Other Skills
-
-| Need | Skill | Usage |
-|------|-------|-------|
-| Task creation | qa-task-creator | Convert action items to structured tasks |
-| Requirements source | qa-requirements-generator | Normalized requirements for comparison |
-| API contract | qa-api-contract-curator | OpenAPI for API dimension |
-| Test cases/RTM | qa-testcase-from-docs, qa-coverage-analyzer | Test mapping, coverage |
-| Spec writing | qa-spec-writer | Update specs when drift found |
-
-## Scope
-
-**Can do (autonomous):**
-- Compare requirements vs UI (via Playwright MCP)
-- Compare requirements vs API contract (OpenAPI)
-- Compare requirements vs test results (RTM, coverage)
-- Compare documentation vs implementation
-- Detect outdated docs, undocumented features, spec drift
-- Produce drift report with action items
-- Suggest tasks for qa-task-creator
-- Recommend regression set optimization (test rotation)
-- Use GitHub MCP for change tracking
-
-**Cannot do (requires confirmation):**
-- Modify documentation or code directly
-- Change requirements without stakeholder approval
-- Override organizational doc/spec policies
-
-**Will not do (out of scope):**
-- Execute tests (consume results only)
-- Write or modify test automation
-- Deploy or change production systems
-
-## Quality Checklist
-
-- [ ] All four comparison dimensions addressed
-- [ ] Drift report includes severity per finding
-- [ ] Action items are specific (update X, fix Y, create test Z)
-- [ ] Task suggestions formatted for qa-task-creator
-- [ ] Regression recommendations include rationale
-- [ ] No hardcoded secrets; URLs/config referenced
-
-## Troubleshooting
-
-| Symptom | Likely Cause | Fix |
-|---------|--------------|-----|
-| UI comparison fails | Playwright MCP not available; auth required | Use API/docs comparison only; note "UI audit skipped" |
-| API contract missing | No OpenAPI; endpoints undocumented | Use qa-api-contract-curator first; manual endpoint list |
-| RTM incomplete | Requirements lack IDs; tests not traced | Use qa-requirements-generator; qa-testcase-from-docs for traceability |
-| Too many findings | Broad scope; noisy comparison | Focus on critical modules; prioritize by business impact |
-| Regression data missing | No test history | Use execution logs; flag "insufficient data" |
-| GitHub MCP errors | Token, permissions | Verify GitHub token; check repo access |
-
-## Reference Files
-
-| Topic | Reference |
-|-------|-----------|
-| Audit checklist per dimension | `references/audit-checklist.md` |
-| Drift patterns and remediation | `references/drift-patterns.md` |

package/skills/qa-spec-auditor/references/audit-checklist.md

@@ -1,144 +0,0 @@
-# Spec Audit Checklist by Dimension
-
-## Overview
-
-Use these checklists when auditing each comparison dimension. Tick items as verified; flag any mismatches as findings.
-
----
-
-## 1. Requirements ↔ UI/Behavior
-
-### Prerequisites
-
-- Requirements document with IDs and acceptance criteria
-- Live UI URL (or Playwright MCP target)
-- Optional: Screenshots, Figma links
-
-### Checklist
-
-| # | Check | How to Verify | Finding Type |
-|---|-------|---------------|--------------|
-| 1 | All required flows exist in UI | Navigate each flow; verify steps | Missing flow |
-| 2 | UI elements match spec (labels, placeholders) | Compare text, ARIA, structure | Spec drift |
-| 3 | Validation rules match spec | Trigger invalid input; compare messages | Spec drift |
-| 4 | Required fields enforced | Omit required fields; verify blocking | Spec drift |
-| 5 | Error states documented and implemented | Trigger errors; compare to spec | Undocumented / Drift |
-| 6 | Navigation/structure matches spec | Compare menu, breadcrumbs, routes | Spec drift |
-| 7 | No extra flows not in spec | Explore UI; flag unknown flows | Undocumented feature |
-| 8 | Accessibility (if in spec) | axe-core, keyboard nav per WCAG | Spec drift |
-
-### Output
-
-- List of requirements with UI mismatches
-- Severity: Critical (blocking), High (wrong behavior), Medium (cosmetic), Low (minor)
-
----
-
-## 2. Requirements ↔ API Contract
-
-### Prerequisites
-
-- Requirements with API expectations
-- OpenAPI spec or equivalent
-- Optional: Actual endpoint responses (from network traffic)
-
-### Checklist
-
-| # | Check | How to Verify | Finding Type |
-|---|-------|---------------|--------------|
-| 1 | All required endpoints exist | Compare req IDs to OpenAPI paths | Missing endpoint |
-| 2 | Request/response schema matches spec | Compare JSON schema to requirements | Spec drift |
-| 3 | Status codes match spec | Document expected 200/400/404/etc. | Spec drift |
-| 4 | Authentication/authorization per spec | Verify auth headers, scopes | Spec drift |
-| 5 | No undocumented endpoints | List all OpenAPI paths; flag untraced | Undocumented feature |
-| 6 | Versioning matches (if applicable) | Check /v1/, /v2/ vs spec | Spec drift |
-| 7 | Error response format per spec | Trigger errors; compare structure | Spec drift |
-| 8 | Deprecated endpoints flagged | Check OpenAPI deprecation vs spec | Outdated doc |
-
-### Output
-
-- Endpoints with mismatches
-- Undocumented endpoints
-- Schema drift details
-
----
-
-## 3. Requirements ↔ Test Results
-
-### Prerequisites
-
-- Requirements with IDs
-- RTM (Requirement → Test Case)
-- Test execution results (pass/fail, coverage)
-
-### Checklist
-
-| # | Check | How to Verify | Finding Type |
-|---|-------|---------------|--------------|
-| 1 | Every requirement has ≥1 test | RTM lookup | Untested requirement |
-| 2 | Every test traces to ≥1 requirement | RTM reverse lookup | Orphan test |
-| 3 | Failed tests map to requirements | Cross-ref results to RTM | Coverage gap |
-| 4 | Test coverage matches risk | High-risk reqs have adequate coverage | Gap |
-| 5 | Execution status current | Last run date; stale tests | Outdated |
-| 6 | Automation status accurate | Manual vs automated flag | Outdated doc |
-| 7 | Test design technique diversity | Per qa-coverage-analyzer | Technique gap |
-
-### Output
-
-- Untested requirements
-- Orphan tests
-- Stale or low-value tests
-
----
-
-## 4. Documentation ↔ Implementation
-
-### Prerequisites
-
-- README, wikis, internal docs
-- Codebase, UI, API (as implementation source)
-
-### Checklist
-
-| # | Check | How to Verify | Finding Type |
-|---|-------|---------------|--------------|
-| 1 | Setup/install steps work | Follow README; verify success | Outdated doc |
-| 2 | API examples run | Execute doc examples; compare output | Outdated doc |
-| 3 | Config options match code | Compare doc to actual config/env | Outdated doc |
-| 4 | Architecture diagram matches code | Compare to structure, imports | Outdated doc |
-| 5 | Changelog/release notes current | Compare to git history | Outdated doc |
-| 6 | Deprecation notices accurate | Check code for deprecated flags | Outdated doc |
-| 7 | No significant features missing from docs | Code review vs doc scope | Undocumented feature |
-| 8 | Screenshots/UI examples current | Compare to live UI | Outdated doc |
-
-### Output
-
-- Doc sections to update
-- Undocumented implementation details
-- Broken examples or steps
-
----
-
-## 5. Regression Set Optimization (Bonus)
-
-### Prerequisites
-
-- Test execution history (pass/fail over time)
-- Test-to-requirement mapping
-- Risk data (from qa-risk-analyzer)
-
-### Checklist
-
-| # | Check | How to Verify | Recommendation |
-|---|-------|---------------|----------------|
-| 1 | "Worn out" tests | Always pass, never fail, many runs | Rotate out or reduce frequency |
-| 2 | High-value tests | Cover critical reqs, catch regressions | Prioritize; run first |
-| 3 | Low-value, stable tests | Low risk, always pass | Deprioritize |
-| 4 | Flaky tests | Intermittent failures | Fix or quarantine |
-| 5 | Missing coverage for changed code | Per qa-risk-analyzer impact | Add tests |
-
-### Output
-
-- Tests to rotate
-- Tests to prioritize
-- Tests to deprioritize or remove

package/skills/qa-spec-auditor/references/drift-patterns.md

@@ -1,207 +0,0 @@
-# Common Spec Drift Patterns and Remediation
-
-## Overview
-
-Spec drift occurs when documentation, requirements, or specs diverge from actual implementation. This reference catalogs common patterns and recommended remediation.
-
----
-
-## Pattern 1: Behavior Changed, Docs Not Updated
-
-### Description
-
-Implementation was modified (bug fix, enhancement, refactor) but requirements, specs, or user docs were not updated.
-
-### Detection
-
-- Git history: code changed, doc files unchanged
-- Compare current behavior to doc description
-- User reports: "The docs say X but it does Y"
-
-### Remediation
-
-| Owner | Action |
-|-------|--------|
-| **Tech writer / QA** | Update requirements, spec, or user docs to match implementation |
-| **Product** | Confirm if behavior change was intentional; if not, file bug |
-| **Dev** | Add "update docs" to DoD for behavior-changing PRs |
-
-### Prevention
-
-- Include doc updates in PR checklist
-- Link requirements to implementation in traceability
-- Periodic spec audits (this skill)
-
----
-
-## Pattern 2: Undocumented Feature
-
-### Description
-
-A feature exists in the product (UI, API, behavior) but has no corresponding requirement, spec, or documentation.
-
-### Detection
-
-- UI exploration: flows or elements not in requirements
-- API: endpoints not in OpenAPI or requirements
-- Code: features without doc references
-
-### Remediation
-
-| Owner | Action |
-|-------|--------|
-| **Product / BA** | Add requirement; assess if intentional or technical debt |
-| **QA** | Create test cases; add to RTM |
-| **Tech writer** | Document in user docs, API docs |
-| **qa-task-creator** | Create tasks: "Add requirement for [feature]", "Document [endpoint]" |
-
-### Prevention
-
-- Feature flags with doc requirement
-- API-first design: OpenAPI before implementation
-- Exploratory testing to catch gaps
-
----
-
-## Pattern 3: Outdated Documentation
-
-### Description
-
-Documentation describes old behavior, deprecated options, or incorrect steps. Implementation has moved on.
-
-### Detection
-
-- Setup steps fail
-- API examples return different structure
-- Screenshots don't match UI
-- Changelog missing recent releases
-
-### Remediation
-
-| Owner | Action |
-|-------|--------|
-| **Tech writer** | Update affected sections; verify against current implementation |
-| **Dev** | Update code comments, README, inline docs |
-| **QA** | Re-verify doc examples; report inaccuracies |
-
-### Prevention
-
-- Doc review in release process
-- Automated checks: run doc examples in CI
-- Single source of truth (e.g., OpenAPI for API docs)
-
----
-
-## Pattern 4: Requirements ↔ Test Gap
-
-### Description
-
-- **Untested requirement:** Requirement has no test
-- **Orphan test:** Test has no requirement traceability
-- **Stale test:** Test passes but doesn't validate current behavior
-
-### Detection
-
-- RTM gaps (qa-coverage-analyzer)
-- Test name/description doesn't match any requirement
-- Test steps outdated after behavior change
-
-### Remediation
-
-| Gap Type | Action |
-|----------|--------|
-| **Untested requirement** | Create test (qa-testcase-from-docs); add to RTM |
-| **Orphan test** | Map to requirement or deprecate if redundant |
-| **Stale test** | Update test steps; re-validate against current behavior |
-
-### Prevention
-
-- RTM maintained in same workflow as requirements
-- Test review when requirements change
-- Traceability in test case format
-
----
-
-## Pattern 5: API Contract Drift
-
-### Description
-
-- OpenAPI/spec doesn't match actual API responses
-- New parameters, fields, or endpoints not in spec
-- Deprecated fields still in spec but removed from API
-
-### Detection
-
-- Contract testing (Pact, OpenAPI validator)
-- Manual comparison: actual response vs schema
-- Consumer integration failures
-
-### Remediation
-
-| Owner | Action |
-|-------|--------|
-| **API owner** | Update OpenAPI to match implementation |
-| **qa-api-contract-curator** | Formalize contract from traffic or code |
-| **Consumer teams** | Update clients if breaking change |
-
-### Prevention
-
-- OpenAPI generated from code (or vice versa)
-- Contract tests in CI
-- Versioning and deprecation policy
-
----
-
-## Pattern 6: "Worn Out" Regression Tests
-
-### Description
-
-Tests that always pass, run frequently, but rarely catch bugs. They consume time without adding value. Often cover stable, low-risk areas.
-
-### Detection
-
-- Execution history: 100% pass over many runs
-- Low risk score (qa-risk-analyzer)
-- Redundant with other tests
-
-### Remediation
-
-| Action | When |
-|--------|------|
-| **Rotate out** | Run less frequently (e.g., weekly vs every PR) |
-| **Consolidate** | Merge with similar tests |
-| **Deprioritize** | Run after high-risk tests |
-| **Remove** | If truly redundant and low value |
-
-### Prevention
-
-- Risk-based test prioritization
-- Periodic test value assessment
-- Replace static tests with parameterized or generated tests for coverage
-
----
-
-## Severity Guidelines
-
-| Severity | Criteria | Example |
-|----------|----------|---------|
-| **Critical** | Blocking; wrong behavior; security | Auth flow doesn't match spec; API returns wrong data |
-| **High** | Major discrepancy; user impact | Required validation missing; doc steps fail |
-| **Medium** | Noticeable drift; moderate impact | Extra field in API; outdated screenshot |
-| **Low** | Minor; cosmetic | Typo in doc; deprecated option still listed |
-
----
-
-## Task Suggestion Format for qa-task-creator
-
-When producing task suggestions, use this structure:
-
-```markdown
-## Task: [Title]
-- **Type:** doc_update | spec_fix | test_creation | implementation_fix
-- **Dimension:** req_ui | req_api | req_tests | docs_impl
-- **Finding:** [Brief description]
-- **Action:** [Specific action]
-- **Artifacts:** [Files, IDs, URLs]
-- **Priority:** critical | high | medium | low
-```