write-test-cases

Write Test Cases

You are tasked with generating manual test case specifications for a single feature by analyzing code in parallel and producing flow-based test case documents for QA teams.

Initial Setup

When this command is invoked, respond with:

I'll generate test cases for this feature. Let me discover the relevant code and analyze it.

Then proceed to Step 1.

Steps

Step 1: Determine Feature Scope

Parse the user's input to determine the feature under test. Handle these input forms:

1. _meta.md path (e.g., .rpiv/test-cases/users/_meta.md):

   • Read the file. Extract feature from frontmatter. Mark as has _meta.md.

2. Feature folder or slug (e.g., .rpiv/test-cases/order-management/ or order-management):

   • Check if .rpiv/test-cases/{input}/_meta.md exists
   • If yes: read it, extract feature, mark as has _meta.md
   • If no: treat as feature name

3. Source code path (e.g., src/orders/ or src/api/controllers/OrdersController.ts):

   • Use the path directly as the starting point for analysis

4. Feature name with optional instructions (e.g., Order Management focus on refund edge cases):

   • Parse as {feature identifier} [additional instructions]
   • Check if .rpiv/test-cases/{slugified-name}/_meta.md exists — if yes, read it and mark as has _meta.md
   • Store additional instructions as supplemental context for agent prompts and checkpoint

5. No arguments provided:

   I'll help you generate test cases. Please provide either:
   1. A feature name: `/skill:write-test-cases Order Management`
   2. A component path: `/skill:write-test-cases src/orders/`
   3. A feature slug: `/skill:write-test-cases order-management`
   4. A _meta.md path: `/skill:write-test-cases .rpiv/test-cases/orders/_meta.md`
   
   Add instructions after the feature: `/skill:write-test-cases Order Management focus on refund edge cases`
   

   Then wait for input.

Warm-Start from _meta.md

When _meta.md is available, read it FULLY and extract:

• Identity: feature, module, portal, slug from frontmatter
• Routes: from ## Routes section — route paths and component names
• Endpoints: from ## Endpoints section — HTTP methods and paths
• Scope decisions: from ## Scope Decisions section — in/out of scope items
• Domain context: from ## Domain Context section — business rules and intentional behaviors
• Checkpoint history: from ## Checkpoint History section — prior Q&A pairs