test-spec_skill

Overview

This skill generates a comprehensive test specification and QA plan for Swift-based iOS/macOS apps. It transforms product requirements, implementation details, and UX specs into a structured TEST_SPEC.md covering unit tests, integration tests, UI automation, accessibility checks, and a beta testing plan. Use it to create a repeatable QA strategy that developers and testers can follow.

How this skill works

The skill reads PRD, implementation guide, UX spec, and architecture docs to extract features, acceptance criteria, view models, data models, API endpoints, user flows, and edge cases. It produces a TEST_SPEC.md that defines test strategy, environments, tooling, test suites for models and view models, priorities, example test code, and a TestFlight beta plan. The output is organized for direct use in the test target and CI pipelines.

When to use it

• When you have a PRD and implementation guide ready and need a QA strategy.
• Before starting test implementation to define coverage and priorities.
• When onboarding new QA engineers or developers to the project.
• Before release to ensure all critical flows and accessibility checks are covered.
• When creating CI rules and test runners for automated checks.

Best practices

• Start with acceptance criteria from the PRD and derive P0/P1 test cases first.
• Aim for a fast feedback loop: heavy unit test coverage, limited critical UI tests.
• Use mocks and stubs for integration tests; reserve real backend testing for staging.
• Include accessibility checks and device/state matrix in each release cycle.
• Automate tests in CI and run full suites on staging before TestFlight betas.

Example use cases

• Generate TEST_SPEC.md from a completed PRD and implementation guide for a new iOS feature set.
• Produce detailed unit and ViewModel test cases for a refactor to ensure behavior is preserved.
• Create UI test plan and XCUITest targets for P0 user journeys before a release.
• Define accessibility audit steps and checklist to meet WCAG-like requirements.
• Outline a TestFlight beta plan with rollout percentages, feedback collection, and crash monitoring.