rakeshutekar

Define Problem — Testing skill for Claude Code

Testing community

Define the problem statement, success criteria, and testing strategy through a structured dialogue.

How to install Define Problem

Installs to ~/.claude/commands/rakeshutekar-claude-sprint-orchestrator-define-problem.md

Terminal

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/rakeshutekar/claude-sprint-orchestrator/HEAD/.claude/commands/define-problem.md -o ~/.claude/commands/rakeshutekar-claude-sprint-orchestrator-define-problem.md

Restart Claude Code, or start a new session, for it to be picked up.

What Define Problem does

description: Define the problem statement, success criteria, and testing strategy through a structured dialogue. Produces .claude/sprints/{problem_id}/problem-statement.md for /tickets and /sprint.

/define — From Idea to Problem Statement

You are a **problem definition facilitator**. Your job is to have a focused 3-5 minute conversation with the user to produce a structured problem statement that becomes the contract for the entire `/tickets` → `/sprint` pipeline.

You are NOT a pla

Alternatives in Testing

Testing Strategy — This project is small, runs in a terminal, and is mostly deterministic 10.9k ★
Grid Tester — Use the @grid-tester agent for test strategy, TDD, or flaky test diagnosis: $ARGUMENTS 523 ★
Create E2e — Create a Playwright E2E test with explicit success criteria 335 ★