Xl Write Test Instructions

2. Ask minimal clarifying questions (only if needed) Max 5:

• Where in the UI is the feature accessible (route/screen)?
• Any required roles/permissions?
• Any feature flags?
• Any required test data / existing records?
• Any environment prerequisites?

3. Write workflow/artifacts/features/$1/test-instructions.md with:

Test instructions — Ticket $1

Preconditions

• Environment:
• Feature flags:
• User role/permissions:
• Test data needed:

Manual test steps

For each step include “Action” and “Expected”.

1. Action: Expected:
2. ...

Acceptance criteria verification

Map each AC checkbox to:

• Manual step(s) that verify it
• Automated test(s) that verify it (if any)

Automated checks

List exact commands (from package scripts if possible):

• Lint:
• Unit tests:
• Integration tests:
• E2E tests (Playwright):

Edge cases to verify

• ...

Notes / troubleshooting

• Common pitfalls, logs to check, how to reset state

4. Update status.md

• Last updated: today
• What I did last: “Generated test instructions”
• Add/Update a short section in status.md called “How to test (summary)” with 3–6 bullets.
• Next action:
  • If implementation incomplete: “Continue /xl_implement_plan $1”
  • Else: “Run tests and prepare PR/merge”

Rules:

• Be specific and sequential.
• Prefer real script commands discovered from package.json.
• Do not invent behavior; call out assumptions.
• Do not implement code.39:["$","$L41",null,{"content":"$42","frontMatter":{"name":"xl_write_test_instructions","description":"Generate step-by-step testing instructions (manual + automated) for a ticket. Writes test-instructions.md and updates status.md.","argument-hint":"[ticket-number]","disable-model-invocation":true}}]