完全なソフトウェアテストのライフサイクルのためのAIエージェントのスキルとツール:要件分析、テスト計画、テスト設計、実行、欠陥管理、閉鎖、テスト自動化。

このリポジトリには、AIコーディングエージェント(Claude Code、GitHub Copilot、Clineなど)をガイドする、再利用可能なエージェントスキル、自己完結の命令セットが含まれており、専門QAおよびテストタスクを実行します。 単一のテストプランジェネレータとして開始したのは、フルSTLCスキルパック

タスクのリポジトリ構造

│ ├── stlc manual testing/ # STLC スキルパック — 7 フェーズ 14 スキル │ ├── 01 jira-requirement-analyzer/# Phase 1 — 要件分析 │ ├── 02 testplan-creater-via-jira LIVE/ # Phase 2 — 実験計画 (flagship) │ ├── SKILL.md │ ├── 文脈/How to Create TestPlan VWO.md │ ├──コピロット/テストプラン.prompt.md │ │ ├── 参照/問い合わせ-checklist.md │ ├── スクリプト/fetch jira.sh │ └── テンプレート/test-plan-template.md │ ├── 03-test-design/ │ ├── 実験シナリオ設計者/ │ │ └── api-test-designer/ │ ├── 04-test-case-development/ │ ├──テストケースライター/ │ │ └── 実験データジェネレーター/ │ ├──05-test-execution/ │ ├── 自動化スクリプト・ジェネレーター/ │ │ ├── 回帰-スイートセレクター/

AgentSkills

AI agent skills and tools for the full software testing lifecycle: requirement analysis, test planning, test design, execution, defect management, closure, and test automation.

This repository contains reusable agent skills, self-contained instruction sets that guide AI coding agents (Claude Code, GitHub Copilot, Cline, etc.) to perform specialized QA and testing tasks. What started as a single Test Plan Generator is now a full STLC skill pack

📦 Repository Structure

│ ├── stlc_manual_testing/ # STLC skill pack — 7 phases, 14 skills │ ├── 01_jira-requirement-analyzer/ # Phase 1 — Requirement Analysis │ ├── 02_testplan-creater-via-jira_LIVE/ # Phase 2 — Test Planning (flagship) │ │ ├── SKILL.md │ │ ├── context/How_to_Create_TestPlan_VWO.md │ │ ├── copilot/test-plan.prompt.md │ │ ├── references/requirement-checklist.md │ │ ├── scripts/fetch_jira.sh │ │ └── template/test-plan-template.md │ ├── 03-test-design/ │ │ ├── test-scenario-designer/ │ │ └── api-test-designer/ │ ├── 04-test-case-development/ │ │ ├── test-case-writer/ │ │ └── test-data-generator/ │ ├── 05-test-execution/ │ │ ├── automation-script-generator/ │ │ ├── regression-suite-selector/ │ │ └── test-execution-tracker/ │ ├── 06-defect-management/ │ │ ├── bug-reporter/ │ │ ├── bug-triage-assistant/ │ │ └── rca-analyzer/ │ └── 07-test-closure/ │ ├── test-coverage-analyzer/ │ └── test-closure-reporter/

---

## 🗺️ STLC Roadmap — which skill fires when

```mermaid
flowchart LR
    A["01 RequirementAnalysis"] --> B["02 TestPlanning"]
    B --> C["03 TestDesign"]
    C --> D["04 Test CaseDevelopment"]
    D --> E["05 TestExecution"]
    E --> F["06 DefectManagement"]
    F --> G["07 TestClosure"]

    A -.- A1[jira-requirement-analyzer]
    B -.- B1[test-plan-generator]
    C -.- C1[test-scenario-designerapi-test-designer]
    D -.- D1[test-case-writertest-data-generator]
    E -.- E1[automation-script-generatorregression-suite-selectortest-execution-tracker]
    F -.- F1[bug-reporterbug-triage-assistantrca-analyzer]
    G -.- G1[test-coverage-analyzertest-closure-reporter]

---

🧰 STLC Manual Testing Pack

Concept: One skill per STLC activity. Each skill is a SKILL.md with a routing description, a step-by-step workflow, an output contract, and guardrails, so any agent produces the same shape of artifact every time.

Why: QA work done ad-hoc by an agent drifts: fabricated acceptance criteria, unprioritized scenarios, bug reports missing repro steps. Encoding each activity as a skill makes the output repeatable and reviewable.

Q&A — why a skill pack instead of one mega-prompt?