Menu
Build a pragmatic unit/integration/e2e test strategy aligned with a spec.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Safely sync a branch with origin/main using fetch + rebase, with an optional "accept current" conflict policy.
Improve acceptance criteria so they are testable, unambiguous, and complete.
Add an MCP integration section (tools, auth, error handling, observability, tests) to an existing spec.
Extract MUST/SHOULD/MAY requirements, constraints, flows, and open questions from long epic/PRD text (PDF/TXT export).
Identify edge cases, security/privacy issues, operational risks, and delivery risks in a spec.
Propose a safe rollout/migration plan with monitoring and rollback steps.
| name | test-plan |
| description | Build a pragmatic unit/integration/e2e test strategy aligned with a spec. |
Create a pragmatic test strategy aligned with the spec.
Write a test plan for this spec.
Include:
- Unit tests: key pure logic, boundary conditions
- Integration tests: DB/API boundaries, mocks vs real dependencies
- E2E tests: critical user journeys (if applicable)
- Non-functional tests: performance, rate limits, resiliency (if relevant)
For each test group:
- what to test,
- what to mock/stub,
- minimal set that must pass for โdoneโ.
If the spec is brownfield, include regression coverage suggestions.