testing-cycle

testing-cycle

Processing feedback: $ARGUMENTS

Phase 1: Classify Feedback

Analyze the feedback and assign a classification:

Present the classification to the user for confirmation before proceeding.

Show:

• Feedback: (original, quoted)
• Classification: [type]
• Rationale: (why this classification)
• Proposed action: (what will be done)

Wait for user confirmation. They may reclassify.

Phase 2: Act by Type

Bug (Critical)

1. Investigate: Find relevant code, understand the root cause
   • Search for related files using the feedback keywords
   • Read the relevant source files
   • Check if there's an existing test covering this behavior
2. Test first:
   • If a test exists but tests the wrong thing → fix the test first (it should now fail)
   • If no test exists → write a failing test that captures the bug
   • Run the test to confirm it fails
3. Fix the code: Make the minimal change to fix the bug
4. Verify tests pass: Run the project's test command (from CLAUDE.md)
5. Ask user to verify: "Can you verify this fix in the running app?"
6. Commit: fix(scope): description

Bug (Minor)

1. Identify the issue in code
2. Fix the code (minimal change)
3. Add test only if the behavior is non-trivial or regression-prone
4. Run the project's test command
5. Commit: fix(scope): description

Gap

1. Document the gap clearly
2. Write a user story with:
   • Type, estimated effort
   • Description explaining what's missing and why it matters
   • INVEST-style acceptance criteria
   • Technical notes if relevant
3. Add to the appropriate backlog file in docs/reference/backlog/:
   • Add the story section (use next available story number)
   • Update the summary table
4. Update docs/reference/BACKLOG_INDEX.md if a new story was added
5. Do NOT implement — this is scope control
6. Report what was logged

Test Correction

1. Find the problematic test
2. Understand the correct behavior from user feedback
3. Fix the test to match correct behavior
4. Run the corrected test — if it now fails, also fix the code
5. Run the project's test command
6. Commit: test(scope): correct [description] (add fix prefix if code also changed)

Enhancement

1. Evaluate scope:
   • Trivial (< 10 lines, obvious improvement) → ask user if should fix now
   • Larger → create backlog story (same process as Gap)
2. Act accordingly:
   • If fixing now: implement, test, commit as feat(scope): or fix(scope):
   • If deferring: log to backlog and report

Phase 3: Verify

After any code change:

1. Run the project's test command (from CLAUDE.md) to verify all tests pass
2. If the app is running, ask the user: "Can you verify this in the running app?"
3. If tests fail, fix the issue before proceeding

Phase 4: Report

Present a summary:

### Feedback Processed

**Feedback:** [original feedback]
**Classification:** [type]
**Action taken:** [what was done]
**Files modified:** [list of files]
**Tests:** [added/modified/none] — tests [pass/fail]
**Commit:** [hash and message] (or "logged to backlog as [story-ID]" for gaps)

Ready for next feedback item (`/testing-cycle <feedback>`) or finish testing.