feat(web): implement schedule editor in MaintenancePoliciesTab
CI / changes (push) Successful in 8s
CI / commitlint (push) Has been skipped
CI / openapi (push) Has been skipped
CI / web (push) Successful in 31s
CI / go (push) Successful in 51s
CI / bird2 (push) Successful in 15s
CI / release (push) Successful in 3m48s
CI / changes (push) Successful in 8s
CI / commitlint (push) Has been skipped
CI / openapi (push) Has been skipped
CI / web (push) Successful in 31s
CI / go (push) Successful in 51s
CI / bird2 (push) Successful in 15s
CI / release (push) Successful in 3m48s
Enhanced the MaintenancePoliciesTab by integrating a schedule editor for maintenance policies. Users can now select schedule modes, input custom cron expressions, and dynamically update the schedule preview. This update improves the user interface and experience for managing maintenance schedules.
This commit is contained in:
Denozordec
@@ -0,0 +1,124 @@
|
||||
# ARCHIVE Command - Task Archiving
|
||||
|
||||
This command creates comprehensive archive documentation and updates the Memory Bank for future reference.
|
||||
|
||||
## Memory Bank Integration
|
||||
|
||||
Reads from:
|
||||
- `memory-bank/tasks.md` - Complete task details and checklists
|
||||
- `memory-bank/reflection/reflection-[task_id].md` - Reflection document
|
||||
- `memory-bank/progress.md` - Implementation status
|
||||
- `memory-bank/creative/creative-*.md` - Creative phase documents (Level 3-4)
|
||||
|
||||
Creates:
|
||||
- `memory-bank/archive/archive-[task_id].md` - Archive document
|
||||
|
||||
Updates:
|
||||
- `memory-bank/tasks.md` - Mark task as COMPLETE
|
||||
- `memory-bank/progress.md` - Add archive reference
|
||||
- `memory-bank/activeContext.md` - Reset for next task
|
||||
|
||||
## Progressive Rule Loading
|
||||
|
||||
### Step 1: Load Core Rules
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/main.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
|
||||
```
|
||||
|
||||
### Step 2: Load ARCHIVE Mode Map
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/visual-maps/archive-mode-map.mdc
|
||||
```
|
||||
|
||||
### Step 3: Load Complexity-Specific Archive Rules
|
||||
Based on complexity level from `memory-bank/tasks.md`:
|
||||
|
||||
**Level 1:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level1/quick-documentation.mdc
|
||||
```
|
||||
|
||||
**Level 2:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level2/archive-basic.mdc
|
||||
```
|
||||
|
||||
**Level 3:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level3/archive-intermediate.mdc
|
||||
```
|
||||
|
||||
**Level 4:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level4/archive-comprehensive.mdc
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Verify Reflection Complete**
|
||||
- Check that `memory-bank/reflection/reflection-[task_id].md` exists
|
||||
- Verify reflection is complete
|
||||
- If not complete, return to `/reflect` command
|
||||
|
||||
2. **Create Archive Document**
|
||||
|
||||
**Level 1:**
|
||||
- Create quick summary
|
||||
- Update `memory-bank/tasks.md` marking task complete
|
||||
|
||||
**Level 2:**
|
||||
- Create basic archive document
|
||||
- Document changes made
|
||||
- Update `memory-bank/tasks.md` and `memory-bank/progress.md`
|
||||
|
||||
**Level 3-4:**
|
||||
- Create comprehensive archive document
|
||||
- Include: Metadata, Summary, Requirements, Implementation details, Testing, Lessons Learned, References
|
||||
- Archive creative phase documents
|
||||
- Document code changes
|
||||
- Document testing approach
|
||||
- Summarize lessons learned
|
||||
- Update all Memory Bank files
|
||||
|
||||
3. **Archive Document Structure**
|
||||
```
|
||||
# TASK ARCHIVE: [Task Name]
|
||||
|
||||
## METADATA
|
||||
- Task ID, dates, complexity level
|
||||
|
||||
## SUMMARY
|
||||
Brief overview of the task
|
||||
|
||||
## REQUIREMENTS
|
||||
What the task needed to accomplish
|
||||
|
||||
## IMPLEMENTATION
|
||||
How the task was implemented
|
||||
|
||||
## TESTING
|
||||
How the solution was verified
|
||||
|
||||
## LESSONS LEARNED
|
||||
Key takeaways from the task
|
||||
|
||||
## REFERENCES
|
||||
Links to related documents (reflection, creative phases, etc.)
|
||||
```
|
||||
|
||||
4. **Update Memory Bank**
|
||||
- Create `memory-bank/archive/archive-[task_id].md`
|
||||
- Mark task as COMPLETE in `memory-bank/tasks.md`
|
||||
- Update `memory-bank/progress.md` with archive reference
|
||||
- Reset `memory-bank/activeContext.md` for next task
|
||||
- Clear completed task details from `memory-bank/tasks.md` (keep structure)
|
||||
|
||||
## Usage
|
||||
|
||||
Type `/archive` to archive the completed task after reflection is done.
|
||||
|
||||
## Next Steps
|
||||
|
||||
After archiving complete, use `/van` command to start the next task.
|
||||
|
||||
@@ -0,0 +1,117 @@
|
||||
# BUILD Command - Code Implementation
|
||||
|
||||
This command implements the planned changes following the implementation plan and creative phase decisions. It enforces a test-driven approach where tests are written for all success criteria and must pass before completing each phase.
|
||||
|
||||
## Memory Bank Integration
|
||||
|
||||
Reads from:
|
||||
- `memory-bank/tasks.md` - Implementation plan and checklists
|
||||
- `memory-bank/creative/creative-*.md` - Design decisions (Level 3-4)
|
||||
- `memory-bank/activeContext.md` - Current project context
|
||||
|
||||
Updates:
|
||||
- `memory-bank/tasks.md` - Implementation progress, test results, and status
|
||||
- `memory-bank/progress.md` - Build status, test outcomes, and observations
|
||||
|
||||
## Progressive Rule Loading
|
||||
|
||||
### Step 1: Load Core Rules
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/main.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/command-execution.mdc
|
||||
```
|
||||
|
||||
### Step 2: Load BUILD Mode Map
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/visual-maps/build-mode-map.mdc
|
||||
```
|
||||
|
||||
### Step 3: Load Complexity-Specific Implementation Rules
|
||||
Based on complexity level from `memory-bank/tasks.md`:
|
||||
|
||||
**Level 1:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level1/workflow-level1.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level1/optimized-workflow-level1.mdc
|
||||
```
|
||||
|
||||
**Level 2:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level2/workflow-level2.mdc
|
||||
```
|
||||
|
||||
**Level 3-4:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level3/implementation-intermediate.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level4/phased-implementation.mdc
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Verify Prerequisites**
|
||||
- Check `memory-bank/tasks.md` for planning completion
|
||||
- For Level 3-4: Verify creative phase documents exist
|
||||
- Review implementation plan
|
||||
|
||||
2. **Determine Complexity Level**
|
||||
- Read complexity level from `memory-bank/tasks.md`
|
||||
- Load appropriate workflow rules
|
||||
|
||||
3. **Execute Implementation**
|
||||
|
||||
**Level 1 (Quick Bug Fix):**
|
||||
- Review bug report
|
||||
- Examine relevant code
|
||||
- Implement targeted fix
|
||||
- Write test(s) validating the fix
|
||||
- Run tests and ensure they pass
|
||||
- Update `memory-bank/tasks.md`
|
||||
|
||||
**Level 2 (Simple Enhancement):**
|
||||
- Review build plan
|
||||
- Examine relevant code areas
|
||||
- Implement changes sequentially
|
||||
- Write tests for each success criterion
|
||||
- Run all tests and ensure they pass
|
||||
- Update `memory-bank/tasks.md`
|
||||
|
||||
**Level 3-4 (Feature/System):**
|
||||
- Review plan and creative decisions
|
||||
- Create directory structure
|
||||
- Build in planned phases
|
||||
- **For each phase:**
|
||||
- Write tests for all phase success criteria
|
||||
- Run tests and ensure they pass
|
||||
- Do NOT proceed to next phase until all tests pass
|
||||
- Integration testing
|
||||
- Document implementation
|
||||
- Update `memory-bank/tasks.md` and `memory-bank/progress.md`
|
||||
|
||||
4. **Test-Driven Phase Completion**
|
||||
- Extract success criteria from current phase in `memory-bank/tasks.md`
|
||||
- Write test cases covering each success criterion
|
||||
- Execute all tests
|
||||
- **Gate:** All tests MUST pass before phase completion
|
||||
- Document test results in `memory-bank/tasks.md`
|
||||
- If tests fail: fix implementation, re-run tests, repeat until all pass
|
||||
|
||||
5. **Command Execution**
|
||||
- Document all commands executed
|
||||
- Document results and observations
|
||||
- Follow platform-specific command guidelines
|
||||
|
||||
6. **Verification**
|
||||
- Verify all build steps completed
|
||||
- Verify all success criteria tests pass
|
||||
- Verify changes meet requirements
|
||||
- Update `memory-bank/tasks.md` with completion status
|
||||
|
||||
## Usage
|
||||
|
||||
Type `/build` to start implementation based on the plan in `memory-bank/tasks.md`.
|
||||
|
||||
## Next Steps
|
||||
|
||||
After implementation complete, proceed to `/reflect` command for task review.
|
||||
|
||||
@@ -0,0 +1,91 @@
|
||||
# CREATIVE Command - Design Decisions
|
||||
|
||||
This command performs structured design exploration for components flagged during planning.
|
||||
|
||||
## Memory Bank Integration
|
||||
|
||||
Reads from:
|
||||
- `memory-bank/tasks.md` - Components requiring creative phases
|
||||
- `memory-bank/activeContext.md` - Current project context
|
||||
|
||||
Creates:
|
||||
- `memory-bank/creative/creative-[feature_name].md` - Design decision documents
|
||||
|
||||
Updates:
|
||||
- `memory-bank/tasks.md` - Records design decisions
|
||||
|
||||
## Progressive Rule Loading
|
||||
|
||||
### Step 1: Load Core Rules
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/main.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
|
||||
```
|
||||
|
||||
### Step 2: Load CREATIVE Mode Map
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/visual-maps/creative-mode-map.mdc
|
||||
```
|
||||
|
||||
### Step 3: Load Creative Phase Enforcement
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Core/creative-phase-enforcement.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/creative-phase-metrics.mdc
|
||||
```
|
||||
|
||||
### Step 4: Load Specialized Creative Rules (Lazy Loaded)
|
||||
Load only when specific creative phase type is needed:
|
||||
|
||||
**For Architecture Design:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-architecture.mdc
|
||||
```
|
||||
|
||||
**For UI/UX Design:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-uiux.mdc
|
||||
```
|
||||
|
||||
**For Algorithm Design:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Phases/CreativePhase/creative-phase-algorithm.mdc
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Verify Planning Complete**
|
||||
- Check `memory-bank/tasks.md` for planning completion
|
||||
- Verify creative phases are identified
|
||||
- If not complete, return to `/plan` command
|
||||
|
||||
2. **Identify Creative Phases**
|
||||
- Read components flagged for creative work from `memory-bank/tasks.md`
|
||||
- Prioritize components for design exploration
|
||||
|
||||
3. **Execute Creative Phase**
|
||||
For each component:
|
||||
- **🎨🎨🎨 ENTERING CREATIVE PHASE: [TYPE]**
|
||||
- Define requirements and constraints
|
||||
- Generate 2-4 design options
|
||||
- Analyze pros/cons of each option
|
||||
- Select and justify recommended approach
|
||||
- Document implementation guidelines
|
||||
- Verify solution meets requirements
|
||||
- **🎨🎨🎨 EXITING CREATIVE PHASE**
|
||||
|
||||
4. **Document Decisions**
|
||||
- Create `memory-bank/creative/creative-[feature_name].md`
|
||||
- Update `memory-bank/tasks.md` with design decisions
|
||||
|
||||
5. **Verify Completion**
|
||||
- Ensure all flagged components have completed creative phases
|
||||
- Mark creative phase as complete in `memory-bank/tasks.md`
|
||||
|
||||
## Usage
|
||||
|
||||
Type `/creative` to start creative design work for components flagged in the plan.
|
||||
|
||||
## Next Steps
|
||||
|
||||
After all creative phases complete, proceed to `/build` command for implementation.
|
||||
|
||||
@@ -0,0 +1,84 @@
|
||||
# PLAN Command - Task Planning
|
||||
|
||||
This command creates detailed implementation plans based on complexity level determined in VAN mode.
|
||||
|
||||
## Memory Bank Integration
|
||||
|
||||
Reads from:
|
||||
- `memory-bank/tasks.md` - Task requirements and complexity level
|
||||
- `memory-bank/activeContext.md` - Current project context
|
||||
- `memory-bank/projectbrief.md` - Project foundation (if exists)
|
||||
|
||||
Updates:
|
||||
- `memory-bank/tasks.md` - Adds detailed implementation plan
|
||||
|
||||
## Progressive Rule Loading
|
||||
|
||||
### Step 1: Load Core Rules
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/main.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
|
||||
```
|
||||
|
||||
### Step 2: Load PLAN Mode Map
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/visual-maps/plan-mode-map.mdc
|
||||
```
|
||||
|
||||
### Step 3: Load Complexity-Specific Planning Rules
|
||||
Based on complexity level from `memory-bank/tasks.md`:
|
||||
|
||||
**Level 2:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level2/task-tracking-basic.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level2/workflow-level2.mdc
|
||||
```
|
||||
|
||||
**Level 3:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level3/task-tracking-intermediate.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level3/planning-comprehensive.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level3/workflow-level3.mdc
|
||||
```
|
||||
|
||||
**Level 4:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level4/task-tracking-advanced.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level4/architectural-planning.mdc
|
||||
Load: .cursor/rules/isolation_rules/Level4/workflow-level4.mdc
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Read Task Context**
|
||||
- Read `memory-bank/tasks.md` to get complexity level
|
||||
- Read `memory-bank/activeContext.md` for current context
|
||||
- Review codebase structure
|
||||
|
||||
2. **Create Implementation Plan**
|
||||
- **Level 2:** Document planned changes, files to modify, implementation steps
|
||||
- **Level 3:** Create comprehensive plan with components, dependencies, challenges
|
||||
- **Level 4:** Create phased implementation plan with architectural considerations
|
||||
|
||||
3. **Technology Validation** (Level 2-4)
|
||||
- Document technology stack selection
|
||||
- Create proof of concept if needed
|
||||
- Verify dependencies and build configuration
|
||||
|
||||
4. **Identify Creative Phases**
|
||||
- Flag components requiring design decisions
|
||||
- Document which components need creative exploration
|
||||
|
||||
5. **Update Memory Bank**
|
||||
- Update `memory-bank/tasks.md` with complete plan
|
||||
- Mark planning phase as complete
|
||||
|
||||
## Usage
|
||||
|
||||
Type `/plan` to start planning based on the task in `memory-bank/tasks.md`.
|
||||
|
||||
## Next Steps
|
||||
|
||||
- **If creative phases identified:** Use `/creative` command
|
||||
- **If no creative phases:** Proceed to `/build` command
|
||||
|
||||
@@ -0,0 +1,101 @@
|
||||
# REFLECT Command - Task Reflection
|
||||
|
||||
This command facilitates structured reflection on completed implementation, documenting lessons learned and process improvements.
|
||||
|
||||
## Memory Bank Integration
|
||||
|
||||
Reads from:
|
||||
- `memory-bank/tasks.md` - Completed implementation details
|
||||
- `memory-bank/progress.md` - Implementation status and observations
|
||||
- `memory-bank/creative/creative-*.md` - Design decisions (Level 3-4)
|
||||
|
||||
Creates:
|
||||
- `memory-bank/reflection/reflection-[task_id].md` - Reflection document
|
||||
|
||||
Updates:
|
||||
- `memory-bank/tasks.md` - Reflection status
|
||||
|
||||
## Progressive Rule Loading
|
||||
|
||||
### Step 1: Load Core Rules
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/main.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
|
||||
```
|
||||
|
||||
### Step 2: Load REFLECT Mode Map
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/visual-maps/reflect-mode-map.mdc
|
||||
```
|
||||
|
||||
### Step 3: Load Complexity-Specific Reflection Rules
|
||||
Based on complexity level from `memory-bank/tasks.md`:
|
||||
|
||||
**Level 1:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level1/quick-documentation.mdc
|
||||
```
|
||||
|
||||
**Level 2:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level2/reflection-basic.mdc
|
||||
```
|
||||
|
||||
**Level 3:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level3/reflection-intermediate.mdc
|
||||
```
|
||||
|
||||
**Level 4:**
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/Level4/reflection-comprehensive.mdc
|
||||
```
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Verify Implementation Complete**
|
||||
- Check `memory-bank/tasks.md` for implementation completion
|
||||
- If not complete, return to `/build` command
|
||||
|
||||
2. **Review Implementation**
|
||||
- Compare implementation against original plan
|
||||
- Review creative phase decisions (Level 3-4)
|
||||
- Review code changes and testing
|
||||
|
||||
3. **Document Reflection**
|
||||
|
||||
**Level 1:**
|
||||
- Quick review of bug fix
|
||||
- Document solution
|
||||
|
||||
**Level 2:**
|
||||
- Review enhancement
|
||||
- Document what went well
|
||||
- Document challenges
|
||||
- Document lessons learned
|
||||
|
||||
**Level 3-4:**
|
||||
- Comprehensive review of implementation
|
||||
- Compare against original plan
|
||||
- Document what went well
|
||||
- Document challenges encountered
|
||||
- Document lessons learned
|
||||
- Document process improvements
|
||||
- Document technical improvements
|
||||
|
||||
4. **Create Reflection Document**
|
||||
- Create `memory-bank/reflection/reflection-[task_id].md`
|
||||
- Structure: Summary, What Went Well, Challenges, Lessons Learned, Process Improvements, Technical Improvements, Next Steps
|
||||
|
||||
5. **Update Memory Bank**
|
||||
- Update `memory-bank/tasks.md` with reflection status
|
||||
- Mark reflection phase as complete
|
||||
|
||||
## Usage
|
||||
|
||||
Type `/reflect` to start reflection on the completed task.
|
||||
|
||||
## Next Steps
|
||||
|
||||
After reflection complete, proceed to `/archive` command to finalize task documentation.
|
||||
|
||||
@@ -0,0 +1,73 @@
|
||||
# VAN Command - Initialization & Entry Point
|
||||
|
||||
This command initializes the Memory Bank system, performs platform detection, determines task complexity, and routes to appropriate workflows.
|
||||
|
||||
## Memory Bank Integration
|
||||
|
||||
**CRITICAL:** All Memory Bank files are located in `memory-bank/` directory:
|
||||
- `memory-bank/tasks.md` - Source of truth for task tracking
|
||||
- `memory-bank/activeContext.md` - Current focus
|
||||
- `memory-bank/progress.md` - Implementation status
|
||||
- `memory-bank/projectbrief.md` - Project foundation
|
||||
|
||||
## Progressive Rule Loading
|
||||
|
||||
This command loads rules progressively to optimize context usage:
|
||||
|
||||
### Step 1: Load Core Rules (Always Required)
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/main.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/memory-bank-paths.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/platform-awareness.mdc
|
||||
Load: .cursor/rules/isolation_rules/Core/file-verification.mdc
|
||||
```
|
||||
|
||||
### Step 2: Load VAN Mode Map
|
||||
```
|
||||
Load: .cursor/rules/isolation_rules/visual-maps/van_mode_split/van-mode-map.mdc
|
||||
```
|
||||
|
||||
### Step 3: Load Complexity-Specific Rules (Based on Task Analysis)
|
||||
After determining complexity level, load:
|
||||
- **Level 1:** `.cursor/rules/isolation_rules/Level1/workflow-level1.mdc`
|
||||
- **Level 2-4:** Load plan mode rules (transition to PLAN command)
|
||||
|
||||
## Workflow
|
||||
|
||||
1. **Platform Detection**
|
||||
- Detect operating system
|
||||
- Adapt commands for platform
|
||||
- Set path separators
|
||||
|
||||
2. **Memory Bank Verification**
|
||||
- Check if `memory-bank/` directory exists
|
||||
- If not, create Memory Bank structure
|
||||
- Verify essential files exist
|
||||
|
||||
3. **Task Analysis**
|
||||
- Read `memory-bank/tasks.md` if exists
|
||||
- Analyze task requirements
|
||||
- Determine complexity level (1-4)
|
||||
|
||||
4. **Route Based on Complexity**
|
||||
- **Level 1:** Continue in VAN mode, proceed to implementation
|
||||
- **Level 2-4:** Transition to `/plan` command
|
||||
|
||||
5. **Update Memory Bank**
|
||||
- Update `memory-bank/tasks.md` with complexity determination
|
||||
- Update `memory-bank/activeContext.md` with current focus
|
||||
|
||||
## Usage
|
||||
|
||||
Type `/van` followed by your task description or initialization request.
|
||||
|
||||
Example:
|
||||
```
|
||||
/van Initialize project for adding user authentication feature
|
||||
```
|
||||
|
||||
## Next Steps
|
||||
|
||||
- **Level 1 tasks:** Proceed directly to `/build` command
|
||||
- **Level 2-4 tasks:** Use `/plan` command for detailed planning
|
||||
|
||||
Reference in New Issue
Block a user