test-strategy-writer
From the author
Write test strategy, 测试策略撰写。Use when: PRD、API Contract、HLD 基线明确后，需要定义独立测试范围、独立测试层次、阶段化执行规则、环境策略、入口/出口标准。 也用于既有相关文档的有限增量更新。
Install
npx skills add TestAny-io/testany-agent-skills --skill test-strategy-writer -a claude-code
Installs to .claude/skills/test-strategy-writer/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Download .zip
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
Security100
Provenance63
Maintenance100
Licence100
Adoption33
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- test-spec-writerTestAny-io/testany-agent-skillsWrite test spec, 测试规格/测试用例包撰写。Use when: LLD 完成且测试策略已确认后，需要产出独立测试范围内完整的 test case package、追溯矩阵与执行说明。 也用于既有相关文档的有限增量更新。Testing★ 82
- test-strategy-reviewerTestAny-io/testany-agent-skillsReview test strategy, 测试策略评审。Use when: 测试策略写完后，需要审查风险覆盖、独立测试分层、阶段化执行规则、环境策略与入口/出口标准是否成立。Testing★ 82
- prd-writervibeeval/vibecosystemProduct Requirements Document writing - PRD templates, MoSCoW prioritization, user personas, competitive analysis, feature specs, acceptance criteria, risk assessmentWriting★ 540
- testing-strategyanthropics/knowledge-work-pluginsDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.OfficialTesting★ 32.5K
- hld-writerTestAny-io/testany-agent-skillsWrite HLD, High-Level Design, 写技术设计文档。Use when: PRD 和 API Contract 完成后需要做系统架构设计、技术选型、制定技术方案。 也用于既有相关文档的有限增量更新。Writing★ 82
- test-strategypetrkindlmann/qa-skillsProduce a multi-quarter QA strategy document. Covers scope, risk-based prioritization, test levels (unit/integration/E2E), pyramid analysis, entry/exit criteria, quality KPIs, tool selection rationale, CI scaling levers, and timeline planning. Output is an actionable strategy document, not a shelf document. Use when: "test strategy," "QA strategy doc," "testing approach," "QA roadmap," "multi-quarter QA direction." Not for: a single-sprint or single-release plan — use test-planning. Not for: identifying which areas carry the most risk — use risk-based-testing first. Related: risk-based-testing, qa-metrics, release-readiness, test-planning, test-reliability.Testing★ 208
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in