test stack

.claude/commands/PECO.SprintPlanning.md

@@ -0,0 +1,51 @@
+---
+description: Sprint planning assistant that creates a story and sub-tasks for a 2-week sprint based on high-level and detailed design documents.
+---
+
+### User Input
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding. If empty, ask the user for a ticket number or task description to work on.
+
+## Goal
+Create a comprehensive sprint plan including a JIRA story and sub-tasks for a 2-week sprint cycle.
+
+## Required Information
+- High-level design document
+- Detailed design document(s)
+- Current project status and past tickets
+
+You can ask for the exact path to design documents, or search the current folder based on a task description provided by the user.
+
+## Steps
+
+### Step 1: Gather Required Information
+Ensure you have all necessary documents and context. Ask for additional details if needed:
+- Design document paths or descriptions
+- Related EPIC or parent ticket information
+- Any specific constraints or requirements
+
+### Step 2: Understand the Problem
+Analyze the current state of the project:
+- Read through the design documents thoroughly
+- Review past tickets and their status
+- Examine the current codebase to understand implementation status
+- Identify what has been completed and what remains to be done
+
+### Step 3: Define the Sprint Goal
+Based on your analysis, propose a realistic goal for the 2-week sprint. Discuss the proposed goal with the user to ensure alignment and feasibility before proceeding.
+
+### Step 4: Break Down Work into Sub-Tasks
+After goal confirmation, create a detailed breakdown of work items:
+- Each task should ideally be scoped to ~2 days of work
+- Focus strictly on items within the sprint goal scope
+- Ensure tasks are concrete and actionable
+
+### Step 5: Create JIRA Tickets
+After user confirmation of the task breakdown, create:
+- One parent story for the sprint goal
+- Individual sub-tasks for each work item identified in Step 4
+
+

.claude/commands/PECO.WorkOn.md

@@ -0,0 +1,61 @@
+---
+description: Work on a JIRA ticket by understanding the ticket description, overall feature design, and scope of work, then implementing the solution.
+---
+
+### User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding. If empty, ask the user for a ticket number to work on.
+
+## Goal
+Implement a JIRA ticket based on the overall design documentation and the specific scope defined in the ticket.
+
+## Steps
+
+### Step 1: Understand the Overall Design
+Locate and review the relevant design documentation:
+- Use search tools to find the corresponding design doc based on the JIRA ticket content
+- Read through the design doc thoroughly to understand the feature architecture
+- Describe your findings and understanding of the problem
+- Ask for confirmation before proceeding
+
+### Step 2: Create a New Branch
+Create a new stacked branch using `git stack create <branch-name>` for this work.
+- Make sure you add the JIRA ticket into the branch name
+
+### Step 3: Discuss Implementation Details
+Plan the implementation approach:
+
+**Important**: Focus on and limit the scope of work according to the JIRA ticket only.
+
+**Important**: Don't start from scratch - there should already be a design doc related to this ticket. Make sure you understand it first, then add implementation details if needed.
+
+Present your implementation plan and ask for confirmation. You may receive feedback on what to change - make sure you incorporate this feedback into your approach.
+
+### Step 4: Implement the Solution
+Write the implementation code:
+- Keep code clean and simple
+- Don't over-engineer or write unnecessary code
+- Follow existing code patterns and conventions in the codebase
+
+### Step 5: Write Tests
+Ensure adequate test coverage:
+- Write comprehensive tests for your implementation
+- Run build and tests to ensure they pass
+- Follow the testing guidelines in the CLAUDE.md file
+
+### Step 6: Update the Design Documentation
+After completing the code changes:
+- Review the related design doc and update it to reflect any discrepancies with the actual implementation
+- Document any important discussions or Q&As that occurred during implementation
+- Ensure documentation remains accurate and up-to-date
+
+### Step 7: Commit and Prepare PR
+Finalize your changes:
+- Commit the changes with a clear commit message
+- Prepare a comprehensive PR title and description following the PR template
+- Use `git stack push` to push changes and create the PR automatically
+- also please update the  pr desc by following the pr desc guidline of the repo