workspace-architect 1.4.1 → 1.5.1

package/assets/prompts/breakdown-test.prompt.md

@@ -1,365 +0,0 @@
----
-mode: 'agent'
-description: 'Test Planning and Quality Assurance prompt that generates comprehensive test strategies, task breakdowns, and quality validation plans for GitHub projects.'
----
-
-# Test Planning & Quality Assurance Prompt
-
-## Goal
-
-Act as a senior Quality Assurance Engineer and Test Architect with expertise in ISTQB frameworks, ISO 25010 quality standards, and modern testing practices. Your task is to take feature artifacts (PRD, technical breakdown, implementation plan) and generate comprehensive test planning, task breakdown, and quality assurance documentation for GitHub project management.
-
-## Quality Standards Framework
-
-### ISTQB Framework Application
-
-- **Test Process Activities**: Planning, monitoring, analysis, design, implementation, execution, completion
-- **Test Design Techniques**: Black-box, white-box, and experience-based testing approaches
-- **Test Types**: Functional, non-functional, structural, and change-related testing
-- **Risk-Based Testing**: Risk assessment and mitigation strategies
-
-### ISO 25010 Quality Model
-
-- **Quality Characteristics**: Functional suitability, performance efficiency, compatibility, usability, reliability, security, maintainability, portability
-- **Quality Validation**: Measurement and assessment approaches for each characteristic
-- **Quality Gates**: Entry and exit criteria for quality checkpoints
-
-## Input Requirements
-
-Before using this prompt, ensure you have:
-
-### Core Feature Documents
-
-1. **Feature PRD**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}.md`
-2. **Technical Breakdown**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/technical-breakdown.md`
-3. **Implementation Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/implementation-plan.md`
-4. **GitHub Project Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/project-plan.md`
-
-## Output Format
-
-Create comprehensive test planning documentation:
-
-1. **Test Strategy**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-strategy.md`
-2. **Test Issues Checklist**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/test-issues-checklist.md`
-3. **Quality Assurance Plan**: `/docs/ways-of-work/plan/{epic-name}/{feature-name}/qa-plan.md`
-
-### Test Strategy Structure
-
-#### 1. Test Strategy Overview
-
-- **Testing Scope**: Features and components to be tested
-- **Quality Objectives**: Measurable quality goals and success criteria
-- **Risk Assessment**: Identified risks and mitigation strategies
-- **Test Approach**: Overall testing methodology and framework application
-
-#### 2. ISTQB Framework Implementation
-
-##### Test Design Techniques Selection
-
-Create a comprehensive analysis of which ISTQB test design techniques to apply:
-
-- **Equivalence Partitioning**: Input domain partitioning strategy
-- **Boundary Value Analysis**: Edge case identification and testing
-- **Decision Table Testing**: Complex business rule validation
-- **State Transition Testing**: System state behavior validation
-- **Experience-Based Testing**: Exploratory and error guessing approaches
-
-##### Test Types Coverage Matrix
-
-Define comprehensive test type coverage:
-
-- **Functional Testing**: Feature behavior validation
-- **Non-Functional Testing**: Performance, usability, security validation
-- **Structural Testing**: Code coverage and architecture validation
-- **Change-Related Testing**: Regression and confirmation testing
-
-#### 3. ISO 25010 Quality Characteristics Assessment
-
-Create a quality characteristics prioritization matrix:
-
-- **Functional Suitability**: Completeness, correctness, appropriateness assessment
-- **Performance Efficiency**: Time behavior, resource utilization, capacity validation
-- **Compatibility**: Co-existence and interoperability testing
-- **Usability**: User interface, accessibility, and user experience validation
-- **Reliability**: Fault tolerance, recoverability, and availability testing
-- **Security**: Confidentiality, integrity, authentication, and authorization validation
-- **Maintainability**: Modularity, reusability, and testability assessment
-- **Portability**: Adaptability, installability, and replaceability validation
-
-#### 4. Test Environment and Data Strategy
-
-- **Test Environment Requirements**: Hardware, software, and network configurations
-- **Test Data Management**: Data preparation, privacy, and maintenance strategies
-- **Tool Selection**: Testing tools, frameworks, and automation platforms
-- **CI/CD Integration**: Continuous testing pipeline integration
-
-### Test Issues Checklist
-
-#### Test Level Issues Creation
-
-- [ ] **Test Strategy Issue**: Overall testing approach and quality validation plan
-- [ ] **Unit Test Issues**: Component-level testing for each implementation task
-- [ ] **Integration Test Issues**: Interface and interaction testing between components
-- [ ] **End-to-End Test Issues**: Complete user workflow validation using Playwright
-- [ ] **Performance Test Issues**: Non-functional requirement validation
-- [ ] **Security Test Issues**: Security requirement and vulnerability testing
-- [ ] **Accessibility Test Issues**: WCAG compliance and inclusive design validation
-- [ ] **Regression Test Issues**: Change impact and existing functionality preservation
-
-#### Test Types Identification and Prioritization
-
-- [ ] **Functional Testing Priority**: Critical user paths and core business logic
-- [ ] **Non-Functional Testing Priority**: Performance, security, and usability requirements
-- [ ] **Structural Testing Priority**: Code coverage targets and architecture validation
-- [ ] **Change-Related Testing Priority**: Risk-based regression testing scope
-
-#### Test Dependencies Documentation
-
-- [ ] **Implementation Dependencies**: Tests blocked by specific development tasks
-- [ ] **Environment Dependencies**: Test environment and data requirements
-- [ ] **Tool Dependencies**: Testing framework and automation tool setup
-- [ ] **Cross-Team Dependencies**: Dependencies on external systems or teams
-
-#### Test Coverage Targets and Metrics
-
-- [ ] **Code Coverage Targets**: >80% line coverage, >90% branch coverage for critical paths
-- [ ] **Functional Coverage Targets**: 100% acceptance criteria validation
-- [ ] **Risk Coverage Targets**: 100% high-risk scenario validation
-- [ ] **Quality Characteristics Coverage**: Validation approach for each ISO 25010 characteristic
-
-### Task Level Breakdown
-
-#### Implementation Task Creation and Estimation
-
-- [ ] **Test Implementation Tasks**: Detailed test case development and automation tasks
-- [ ] **Test Environment Setup Tasks**: Infrastructure and configuration tasks
-- [ ] **Test Data Preparation Tasks**: Data generation and management tasks
-- [ ] **Test Automation Framework Tasks**: Tool setup and framework development
-
-#### Task Estimation Guidelines
-
-- [ ] **Unit Test Tasks**: 0.5-1 story point per component
-- [ ] **Integration Test Tasks**: 1-2 story points per interface
-- [ ] **E2E Test Tasks**: 2-3 story points per user workflow
-- [ ] **Performance Test Tasks**: 3-5 story points per performance requirement
-- [ ] **Security Test Tasks**: 2-4 story points per security requirement
-
-#### Task Dependencies and Sequencing
-
-- [ ] **Sequential Dependencies**: Tests that must be implemented in specific order
-- [ ] **Parallel Development**: Tests that can be developed simultaneously
-- [ ] **Critical Path Identification**: Testing tasks on the critical path to delivery
-- [ ] **Resource Allocation**: Task assignment based on team skills and capacity
-
-#### Task Assignment Strategy
-
-- [ ] **Skill-Based Assignment**: Matching tasks to team member expertise
-- [ ] **Capacity Planning**: Balancing workload across team members
-- [ ] **Knowledge Transfer**: Pairing junior and senior team members
-- [ ] **Cross-Training Opportunities**: Skill development through task assignment
-
-### Quality Assurance Plan
-
-#### Quality Gates and Checkpoints
-
-Create comprehensive quality validation checkpoints:
-
-- **Entry Criteria**: Requirements for beginning each testing phase
-- **Exit Criteria**: Quality standards required for phase completion
-- **Quality Metrics**: Measurable indicators of quality achievement
-- **Escalation Procedures**: Process for addressing quality failures
-
-#### GitHub Issue Quality Standards
-
-- [ ] **Template Compliance**: All test issues follow standardized templates
-- [ ] **Required Field Completion**: Mandatory fields populated with accurate information
-- [ ] **Label Consistency**: Standardized labeling across all test work items
-- [ ] **Priority Assignment**: Risk-based priority assignment using defined criteria
-- [ ] **Value Assessment**: Business value and quality impact assessment
-
-#### Labeling and Prioritization Standards
-
-- [ ] **Test Type Labels**: `unit-test`, `integration-test`, `e2e-test`, `performance-test`, `security-test`
-- [ ] **Quality Labels**: `quality-gate`, `iso25010`, `istqb-technique`, `risk-based`
-- [ ] **Priority Labels**: `test-critical`, `test-high`, `test-medium`, `test-low`
-- [ ] **Component Labels**: `frontend-test`, `backend-test`, `api-test`, `database-test`
-
-#### Dependency Validation and Management
-
-- [ ] **Circular Dependency Detection**: Validation to prevent blocking relationships
-- [ ] **Critical Path Analysis**: Identification of testing dependencies on delivery timeline
-- [ ] **Risk Assessment**: Impact analysis of dependency delays on quality validation
-- [ ] **Mitigation Strategies**: Alternative approaches for blocked testing activities
-
-#### Estimation Accuracy and Review
-
-- [ ] **Historical Data Analysis**: Using past project data for estimation accuracy
-- [ ] **Technical Lead Review**: Expert validation of test complexity estimates
-- [ ] **Risk Buffer Allocation**: Additional time allocation for high-uncertainty tasks
-- [ ] **Estimate Refinement**: Iterative improvement of estimation accuracy
-
-## GitHub Issue Templates for Testing
-
-### Test Strategy Issue Template
-
-```markdown
-# Test Strategy: {Feature Name}
-
-## Test Strategy Overview
-
-{Summary of testing approach based on ISTQB and ISO 25010}
-
-## ISTQB Framework Application
-
-**Test Design Techniques Used:**
-- [ ] Equivalence Partitioning
-- [ ] Boundary Value Analysis
-- [ ] Decision Table Testing
-- [ ] State Transition Testing
-- [ ] Experience-Based Testing
-
-**Test Types Coverage:**
-- [ ] Functional Testing
-- [ ] Non-Functional Testing
-- [ ] Structural Testing
-- [ ] Change-Related Testing (Regression)
-
-## ISO 25010 Quality Characteristics
-
-**Priority Assessment:**
-- [ ] Functional Suitability: {Critical/High/Medium/Low}
-- [ ] Performance Efficiency: {Critical/High/Medium/Low}
-- [ ] Compatibility: {Critical/High/Medium/Low}
-- [ ] Usability: {Critical/High/Medium/Low}
-- [ ] Reliability: {Critical/High/Medium/Low}
-- [ ] Security: {Critical/High/Medium/Low}
-- [ ] Maintainability: {Critical/High/Medium/Low}
-- [ ] Portability: {Critical/High/Medium/Low}
-
-## Quality Gates
-- [ ] Entry criteria defined
-- [ ] Exit criteria established
-- [ ] Quality thresholds documented
-
-## Labels
-`test-strategy`, `istqb`, `iso25010`, `quality-gates`
-
-## Estimate
-{Strategic planning effort: 2-3 story points}
-```
-
-### Playwright Test Implementation Issue Template
-
-```markdown
-# Playwright Tests: {Story/Component Name}
-
-## Test Implementation Scope
-{Specific user story or component being tested}
-
-## ISTQB Test Case Design
-**Test Design Technique**: {Selected ISTQB technique}
-**Test Type**: {Functional/Non-Functional/Structural/Change-Related}
-
-## Test Cases to Implement
-**Functional Tests:**
-- [ ] Happy path scenarios
-- [ ] Error handling validation
-- [ ] Boundary value testing
-- [ ] Input validation testing
-
-**Non-Functional Tests:**
-- [ ] Performance testing (response time < {threshold})
-- [ ] Accessibility testing (WCAG compliance)
-- [ ] Cross-browser compatibility
-- [ ] Mobile responsiveness
-
-## Playwright Implementation Tasks
-- [ ] Page Object Model development
-- [ ] Test fixture setup
-- [ ] Test data management
-- [ ] Test case implementation
-- [ ] Visual regression tests
-- [ ] CI/CD integration
-
-## Acceptance Criteria
-- [ ] All test cases pass
-- [ ] Code coverage targets met (>80%)
-- [ ] Performance thresholds validated
-- [ ] Accessibility standards verified
-
-## Labels
-`playwright`, `e2e-test`, `quality-validation`
-
-## Estimate
-{Test implementation effort: 2-5 story points}
-```
-
-### Quality Assurance Issue Template
-
-```markdown
-# Quality Assurance: {Feature Name}
-
-## Quality Validation Scope
-{Overall quality validation for feature/epic}
-
-## ISO 25010 Quality Assessment
-**Quality Characteristics Validation:**
-- [ ] Functional Suitability: Completeness, correctness, appropriateness
-- [ ] Performance Efficiency: Time behavior, resource utilization, capacity
-- [ ] Usability: Interface aesthetics, accessibility, learnability, operability
-- [ ] Security: Confidentiality, integrity, authentication, authorization
-- [ ] Reliability: Fault tolerance, recovery, availability
-- [ ] Compatibility: Browser, device, integration compatibility
-- [ ] Maintainability: Code quality, modularity, testability
-- [ ] Portability: Environment adaptability, installation procedures
-
-## Quality Gates Validation
-**Entry Criteria:**
-- [ ] All implementation tasks completed
-- [ ] Unit tests passing
-- [ ] Code review approved
-
-**Exit Criteria:**
-- [ ] All test types completed with >95% pass rate
-- [ ] No critical/high severity defects
-- [ ] Performance benchmarks met
-- [ ] Security validation passed
-
-## Quality Metrics
-- [ ] Test coverage: {target}%
-- [ ] Defect density: <{threshold} defects/KLOC
-- [ ] Performance: Response time <{threshold}ms
-- [ ] Accessibility: WCAG {level} compliance
-- [ ] Security: Zero critical vulnerabilities
-
-## Labels
-`quality-assurance`, `iso25010`, `quality-gates`
-
-## Estimate
-{Quality validation effort: 3-5 story points}
-```
-
-## Success Metrics
-
-### Test Coverage Metrics
-
-- **Code Coverage**: >80% line coverage, >90% branch coverage for critical paths
-- **Functional Coverage**: 100% acceptance criteria validation
-- **Risk Coverage**: 100% high-risk scenario testing
-- **Quality Characteristics Coverage**: Validation for all applicable ISO 25010 characteristics
-
-### Quality Validation Metrics
-
-- **Defect Detection Rate**: >95% of defects found before production
-- **Test Execution Efficiency**: >90% test automation coverage
-- **Quality Gate Compliance**: 100% quality gates passed before release
-- **Risk Mitigation**: 100% identified risks addressed with mitigation strategies
-
-### Process Efficiency Metrics
-
-- **Test Planning Time**: <2 hours to create comprehensive test strategy
-- **Test Implementation Speed**: <1 day per story point of test development
-- **Quality Feedback Time**: <2 hours from test completion to quality assessment
-- **Documentation Completeness**: 100% test issues have complete template information
-
-This comprehensive test planning approach ensures thorough quality validation aligned with industry standards while maintaining efficient project management and clear accountability for all testing activities.

package/assets/prompts/code-exemplars-blueprint-generator.prompt.md

@@ -1,126 +0,0 @@
----
-description: 'Technology-agnostic prompt generator that creates customizable AI prompts for scanning codebases and identifying high-quality code exemplars. Supports multiple programming languages (.NET, Java, JavaScript, TypeScript, React, Angular, Python) with configurable analysis depth, categorization methods, and documentation formats to establish coding standards and maintain consistency across development teams.'
-mode: 'agent'
----
-
-# Code Exemplars Blueprint Generator
-
-## Configuration Variables
-${PROJECT_TYPE="Auto-detect|.NET|Java|JavaScript|TypeScript|React|Angular|Python|Other"} <!-- Primary technology -->
-${SCAN_DEPTH="Basic|Standard|Comprehensive"} <!-- How deeply to analyze the codebase -->
-${INCLUDE_CODE_SNIPPETS=true|false} <!-- Include actual code snippets in addition to file references -->
-${CATEGORIZATION="Pattern Type|Architecture Layer|File Type"} <!-- How to organize exemplars -->
-${MAX_EXAMPLES_PER_CATEGORY=3} <!-- Maximum number of examples per category -->
-${INCLUDE_COMMENTS=true|false} <!-- Include explanatory comments for each exemplar -->
-
-## Generated Prompt
-
-"Scan this codebase and generate an exemplars.md file that identifies high-quality, representative code examples. The exemplars should demonstrate our coding standards and patterns to help maintain consistency. Use the following approach:
-
-### 1. Codebase Analysis Phase
-- ${PROJECT_TYPE == "Auto-detect" ? "Automatically detect primary programming languages and frameworks by scanning file extensions and configuration files" : `Focus on ${PROJECT_TYPE} code files`}
-- Identify files with high-quality implementation, good documentation, and clear structure
-- Look for commonly used patterns, architecture components, and well-structured implementations
-- Prioritize files that demonstrate best practices for our technology stack
-- Only reference actual files that exist in the codebase - no hypothetical examples
-
-### 2. Exemplar Identification Criteria
-- Well-structured, readable code with clear naming conventions
-- Comprehensive comments and documentation
-- Proper error handling and validation
-- Adherence to design patterns and architectural principles
-- Separation of concerns and single responsibility principle
-- Efficient implementation without code smells
-- Representative of our standard approaches
-
-### 3. Core Pattern Categories
-
-${PROJECT_TYPE == ".NET" || PROJECT_TYPE == "Auto-detect" ? `#### .NET Exemplars (if detected)
-- **Domain Models**: Find entities that properly implement encapsulation and domain logic
-- **Repository Implementations**: Examples of our data access approach
-- **Service Layer Components**: Well-structured business logic implementations
-- **Controller Patterns**: Clean API controllers with proper validation and responses
-- **Dependency Injection Usage**: Good examples of DI configuration and usage
-- **Middleware Components**: Custom middleware implementations
-- **Unit Test Patterns**: Well-structured tests with proper arrangement and assertions` : ""}
-
-${(PROJECT_TYPE == "JavaScript" || PROJECT_TYPE == "TypeScript" || PROJECT_TYPE == "React" || PROJECT_TYPE == "Angular" || PROJECT_TYPE == "Auto-detect") ? `#### Frontend Exemplars (if detected)
-- **Component Structure**: Clean, well-structured components
-- **State Management**: Good examples of state handling
-- **API Integration**: Well-implemented service calls and data handling
-- **Form Handling**: Validation and submission patterns
-- **Routing Implementation**: Navigation and route configuration
-- **UI Components**: Reusable, well-structured UI elements
-- **Unit Test Examples**: Component and service tests` : ""}
-
-${PROJECT_TYPE == "Java" || PROJECT_TYPE == "Auto-detect" ? `#### Java Exemplars (if detected)
-- **Entity Classes**: Well-designed JPA entities or domain models
-- **Service Implementations**: Clean service layer components
-- **Repository Patterns**: Data access implementations
-- **Controller/Resource Classes**: API endpoint implementations
-- **Configuration Classes**: Application configuration
-- **Unit Tests**: Well-structured JUnit tests` : ""}
-
-${PROJECT_TYPE == "Python" || PROJECT_TYPE == "Auto-detect" ? `#### Python Exemplars (if detected)
-- **Class Definitions**: Well-structured classes with proper documentation
-- **API Routes/Views**: Clean API implementations
-- **Data Models**: ORM model definitions
-- **Service Functions**: Business logic implementations
-- **Utility Modules**: Helper and utility functions
-- **Test Cases**: Well-structured unit tests` : ""}
-
-### 4. Architecture Layer Exemplars
-
-- **Presentation Layer**:
-  - User interface components
-  - Controllers/API endpoints
-  - View models/DTOs
-  
-- **Business Logic Layer**:
-  - Service implementations
-  - Business logic components
-  - Workflow orchestration
-  
-- **Data Access Layer**:
-  - Repository implementations
-  - Data models
-  - Query patterns
-  
-- **Cross-Cutting Concerns**:
-  - Logging implementations
-  - Error handling
-  - Authentication/authorization
-  - Validation
-
-### 5. Exemplar Documentation Format
-
-For each identified exemplar, document:
-- File path (relative to repository root)
-- Brief description of what makes it exemplary
-- Pattern or component type it represents
-${INCLUDE_COMMENTS ? "- Key implementation details and coding principles demonstrated" : ""}
-${INCLUDE_CODE_SNIPPETS ? "- Small, representative code snippet (if applicable)" : ""}
-
-${SCAN_DEPTH == "Comprehensive" ? `### 6. Additional Documentation
-
-- **Consistency Patterns**: Note consistent patterns observed across the codebase
-- **Architecture Observations**: Document architectural patterns evident in the code
-- **Implementation Conventions**: Identify naming and structural conventions
-- **Anti-patterns to Avoid**: Note any areas where the codebase deviates from best practices` : ""}
-
-### ${SCAN_DEPTH == "Comprehensive" ? "7" : "6"}. Output Format
-
-Create exemplars.md with:
-1. Introduction explaining the purpose of the document
-2. Table of contents with links to categories
-3. Organized sections based on ${CATEGORIZATION}
-4. Up to ${MAX_EXAMPLES_PER_CATEGORY} exemplars per category
-5. Conclusion with recommendations for maintaining code quality
-
-The document should be actionable for developers needing guidance on implementing new features consistent with existing patterns.
-
-Important: Only include actual files from the codebase. Verify all file paths exist. Do not include placeholder or hypothetical examples.
-"
-
-## Expected Output
-Upon running this prompt, GitHub Copilot will scan your codebase and generate an exemplars.md file containing real references to high-quality code examples in your repository, organized according to your selected parameters.

package/assets/prompts/comment-code-generate-a-tutorial.prompt.md

@@ -1,26 +0,0 @@
----
-description: 'Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial.'
-mode: 'agent'
----
-
-Transform this Python script into a polished, beginner-friendly project by refactoring the code, adding clear instructional comments, and generating a complete markdown tutorial.
-
-1. **Refactor the code**  
-   - Apply standard Python best practices  
-   - Ensure code follows the PEP 8 style guide  
-   - Rename unclear variables and functions if needed for clarity
-
-1. **Add comments throughout the code**  
-   - Use a beginner-friendly, instructional tone  
-   - Explain what each part of the code is doing and why it's important  
-   - Focus on the logic and reasoning, not just syntax  
-   - Avoid redundant or superficial comments
-
-1. **Generate a tutorial as a `README.md` file**  
-   Include the following sections:
-   - **Project Overview:** What the script does and why it's useful  
-   - **Setup Instructions:** Prerequisites, dependencies, and how to run the script  
-   - **How It Works:** A breakdown of the code logic based on the comments  
-   - **Example Usage:** A code snippet showing how to use it  
-   - **Sample Output:** (Optional) Include if the script returns visible results  
-   - Use clear, readable Markdown formatting