/plan

Communication Style: Casual, professional Bahasa Indonesia.

Mandatory

1. Please remember to ask any clarifying questions with an option list for each TODO / Lean.
2. If the user already provides the required information, do NOT ask again.
3. Create TODOS for each instructions below.

Instructions

Think to execute step by step :

1. Determine the feature path in the codebase:

   • The feature path refers to the directory containing related components (e.g., src/features/user), Never scan codebase or continue the process if user did not give the feature path.
   • If not provided, ask with options and dont continue.
   • Understand the feature name base on feature path (e.g., src/features/user it mean feature name = user).
   • Do not give user any suggestion path.
   • If still missing, stop.

2. Determine the context test scenario:

   • Ask: "Skenario apa yang ingin diuji ?"
   • Mandatory Do not give the user any suggestion scenario except scenario Create, Update, Delete, View for that path.
   • If context test scenario still missing, stop.

3. After get context test scenario and feature path from user, Delegate to codebase-explorer to gather context:

   • List components, routes, forms, relevant UI elements, data-testid, and APIs.
   • Extract props, attributes, and file structure.
   • Prompt template delegation to the codebase-explorer:

        I need you to systematically explore the codebase for the <context test scenario> located at <feature path> to gather comprehensive context for
        creating test plans.
     
        Please collect the following information:
        1. List all components, forms, and UI elements in the <feature path>
        2. Identify application routes related to <context test scenario> functionality
        3. Extract props, attributes, and file structure,
        4. Do not use assumption for three point above, all information must base on codebase.
        5. **MOST IMPORTANT**: Use "Logic to collect data-testid" from `collect-selector` skill and Think step-by-step to resolve the correct value for `data-testid` 
     
        Please provide a comprehensive analysis of:
        - Component structure and hierarchy
        - Form elements and their data-testid values
        - Buttons, links, and interactive elements
        - Input fields and validation
        - API endpoints and services
        - Any existing test files or test-related configurations
     
        Focus on gathering all the necessary context to create end-to-end test scenarios for the user feature.
     

4. Mandatory think step-by-step to re-validate and resolve the correct value for data-testid for each UI element found by the codebase-explorer agent using "Logic to collect data-testid" from collect-selector skill.

5. Based on the context, propose 3–7 candidate scenarios with the fields: | ID | Title | Component Path | Route | Priority | Tags |

   • Use SCN-<sequential from 001> as Code / Scenario ID
   • Ask user approve before continue to the next step.

6. Use the plan-document skill to generate the full Markdown test plan for each scenario (1 scenario = 1 document).

7. Flow: Save the file:

   • Check feature tast plan in docs/test-plan/
     • Check existing test plan using ls -la docs/test-plan/ If you find a duplicate <feature name>, Propose to create version directory docs/test-plan/<feature name>-v-*.
     • Ask user approve before continue to the next step.
   • Save the test plan file to docs/test-plan/<feature name>/<Code>-<short-scenario-slug>.md

8. After all scenarios are saved, close the session with: "All plans have been saved in docs/test-plan/<feature name>/ and are ready for /venturo-e2e-web:generate."