From qa
Generates contextual next-action suggestions based on current QA state. Appends 'Suggested next step' to command output. Used by all /qa:* commands to maintain workflow coherence.
How this skill is triggered — by the user, by Claude, or both
Slash command
/qa:qa-coordinatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Determine the most helpful next action for the user based on current QA state.
Determine the most helpful next action for the user based on current QA state.
Called at the end of every /qa:* command to append a "Suggested next step" line.
/qa:init/qa:scenarios to generate user scenarios, or /test to run your tests."/qa:scenarios to plan what to test."/qa:sync to select test types and generate artifacts."/qa:sync/qa:analyze to check test health."/qa:analyze to check test health against the new configuration."/qa:analyze for a deeper test health check."/qa:analyze/test:review for detailed recommendations."/test:coverage to verify coverage thresholds."/qa:scenarios.claude/scenarios/. Use the e2e-test-writer skill to create e2e tests from these scenarios, or run /qa:scenarios --spec <path> to attach them to a spec."Always output exactly one suggestion line at the end of the command output:
---
**Suggested next step:** Run `/qa:sync` to update 3 outdated artifacts.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
npx claudepluginhub kokoszsz/qa-plugin --plugin qa