From codex-next
Designs or validates test plans covering unit, integration, e2e, automation, CI checks, fixtures, and regression scope. Works with existing test frameworks and CI commands.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codex-next:dev-test-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this workflow when a software task needs test planning, test implementation, or validation triage.
Use this workflow when a software task needs test planning, test implementation, or validation triage.
Map existing tests.
Identify changed behavior.
Choose test levels.
Keep validation efficient.
Handle failures honestly.
Return:
npx claudepluginhub blueskyxn/codex-is-all-you-need --plugin codex-nextProduce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
Designs test strategies and plans with testing pyramid. Covers APIs, frontend, data pipelines, infrastructure; outputs plans including coverage targets, examples, and gaps.
Design testing strategies (unit, integration, end-to-end, performance) that catch bugs without creating bottlenecks. Use when scaling testing or improving release confidence.