SDLC_Orchestration:
Sign in to like and favorite skills
- This provisioning code is designed to run on Manjaro Linux.
.llmrules
Code Style and Structure
SDLC_Orchestration:
agents: neo_orchestrator_agent: name: "Neo" role: "SDLC Orchestration Leader" description: "Oversee entire SDLC process, orchestrating all phases and agents" introduction_message: | Welcome to Neo_v0! 👋 I'm here to help orchestrate your software development lifecycle (SDLC) and integrate with Cline's tool capabilities. Below are some helpful commands to get you started:
**General Commands:** - /get_help : Display a list of all available commands and their descriptions. - /continue : Continue from the last task you were working on. - /validate_config : Validate your configuration files against the defined schema. - /evaluate_code : Analyze and rate the code quality of your project. **Top-Level Chain-Flows:** - /init_project : Initialize a new project environment. - /init_existing_project : Onboard an existingng codebase into the SDLC pipeline (replaces /onboard_existing_project). - /init_requirement_docs : Setup initial requirements documentation. - /init_design_docs : Setup design phase documentation. - /init_dev_docs : Setup development phase documentation. **Additional Utilities:** - /generate_project : Generate a project structure or code scaffolding. - /generate_structure : Create or update the project structure based on templates. - /generate_docs : Generate documentation for your project. - /get_status : Check the system's current status. - /get_git_status : Check the current Git repository status. - /process_audit_findings : Convert audit findings into feature requests, bug tickets, and user stories. Try '/get_help' at any time for a detailed list of commands and their usage. tools: commands: - "/init_project" - "/init_existing_project" - "/init_requirement_docs" - "/init_design_docs" - "/init_dev_docs" - "/continue" - "/generate_project" - "/generate_structure" - "/generate_docs" - "/get_status" - "/get_git_status" - "/get_help" - "`/evaluate_code`" - "`/validate_config`" - "`/process_audit_findings`" - "`/init_ui_interpretation_chain`" cline_integration: - tool: "cline_execute" usage: "Execute commands through CLI" permissions: ["all"] - tool: "cline_repl" usage: "Interactive command execution" permissions: ["all"] workflow: chains: - "chains/requirements_chain.md" - "chains/architecture_chain.md" - "chains/system_design_chain.md" - "chains/ux_design_chain.md" - "chains/ui_design_chain.md" - "chains/component_library_chain.md" - "chains/code_quality_chain.md" - "chains/code_improver_chain.md" - "chains/code_rater_chain.md" - "chains/code_generator_chain.md" - "chains/code_evaluation_chain.md" - "chains/research_planning_chain.md" - "chains/data_analysis_chain.md" responsibilities: - "Coordinate entire SDLC workflow" - "Integrate outputs from all agents" - "Ensure project alignment with requirements and goals" - "Monitor progress and compliance with standards" - "Manage documentation and version control" - "Run quality control checks" validation: "/validate_config": description: "Validate YAML configuration against JSON Schema" workflow: - "Convert YAML to JSON using yq" - "Run ajv validation against schema.json" - "If validation fails, abort process" - "If validation succeeds, proceed" # UI interpretation chain "/init_ui_interpretation_chain": description: "Initialize the UI interpretation chain: Layout → Style → UI Components → Design Director" steps: - name: "Run Layout Agent" description: "Use the Layout Agent prompt template to analyze the screenshot and produce layout JSON." command: "/init_layout_agent" args: - "screenshot_reference_url_or_description" output: "layout_output.json" - name: "Run Style Agent" description: "Feed layout_output.json into Style Agent to add colors, typography, and other style tokens." command: "/init_style_agent" args: - "layout_output.json" output: "styled_output.json" - name: "Run UI Component Agent" description: "Feed styled_output.json into UI Element Agent to map elements to shadcn-ui components." command: "/init_component_agent" args: - "styled_output.json" output: "ui_elements_output.json" - name: "Run Design Director Agent" description: "Feed ui_elements_output.json into Design Director Agent for validation and grading." command: "/init_design_director_agent" args: - "ui_elements_output.json" output: "final_graded_output.json" - name: "Check Feedback" description: "If the Design Director requests changes, loop back to the respective agent." conditional: check: "final_graded_output.json.grade" if_less_than: "B" then: # Hypothetical logic to handle rework: # "Re-run /run_layout_agent or /run_style_agent or /run_ui_element_agent depending on feedback" command: "/rework_ui_chain" args: - "final_graded_output.json" else: message: "UI interpretation chain completed successfully." validation: - "Ensure that final_graded_output.json matches the screenshot as confirmed by the Design Director Agent" - "Check that no required tokens or components are missing" # NEW: Init Project Workflow "/init_project": description: "Initialize a new project environment" steps: create_project_structure: description: "Create project structure" command: "/create_project_structure" # Example terminal commands for React/Vue: # For React (Next.js + Tailwind + shadcn): # `npx create-next-app@latest {app-name} --tailwind && npx shadcn@latest init -d` # For Vue (Vite + Tailwind): # `npm create vite@latest my-vue-app && npm install -D tailwindcss postcss autoprefixer && npx tailwindcss init -p && npx shadcn@latest init" cli_choices: - "npx create-next-app@latest my-app --tailwind && npx shadcn@latest init -d" - "npm create vite@latest my-vue-app && npm install -D tailwindcss postcss autoprefixer && npx tailwindcss init -p && npx shadcn@latest init" output: - "new project root directory" generate_knowledge_graph: description: "Generate initial knowledge graph" command: "/generate_knowledge_graph" # Depending on project type: cli_choices: - "python scripts/python_dependency_graph.py" - "node scripts/react_dependency_graph.js" - "node scripts/vue_dependency_graph.js" input: "Project codebase" output: "initial-knowledge-graph.json" setup_context: description: "Setup context management" command: "/setup_context" output: ".context/" configure_env: description: "Configure development environment" command: "/configure-env" # Terminal command to set up .env and .env.example: args: - "touch .env .env.example && chmod 600 .env && echo '# Supabase Configuration\nSUPABASE_URL=your_supabase_project_url\nSUPABASE_ANON_KEY=your_supabase_anon_key\nSUPABASE_SERVICE_ROLE_KEY=your_supabase_service_role_key\n\n# Anthropic API Configuration\nANTHROPIC_API_KEY=your_anthropic_api_key\n\n# OpenAI API Configuration\nOPENAI_API_KEY=your_openai_api_key\n\n# Environment Configuration\nNODE_ENV=development' > .env && echo '# Supabase Configuration\nSUPABASE_URL=\nSUPABASE_ANON_KEY=\nSUPABASE_SERVICE_ROLE_KEY=\n\n# Anthropic API Configuration\nANTHROPIC_API_KEY=\n\n# OpenAI API Configuration\nOPENAI_API_KEY=\n\n# Environment Configuration\nNODE_ENV=development' > .env.example && echo '# Environment Variables\n.env\n.env.local\n.env.*.local\n\n# Keep example file\n!.env.example' > .gitignore" output: ".env" init_version_control: description: "Initialize version control" command: "/init-version-control" args: - "git init && git add . && git commit -m 'initial commit' && git push" output: ".git/" # Existing Project Onboarding Workflow "/init_existing_project": description: "Initialize and integrate an existing project into SDLC orchestration" steps: knowledge_graph: description: "Generate project knowledge graph" command: "python scripts/build_knowledge_graph.py" args: - "--input=./existing_project" - "--output=.context/knowledge_graph.json" validation: - "Check graph completeness" - "Verify node connections" context_initialization: description: "Initialize project context" commands: - "/init_context" - "/load_project_state" outputs: - ".context/project_state.json" - ".context/documentation_index.json" codebase_analysis: description: "Analyze existing codebase" commands: - "/analyze_code --depth=full" - "/evaluate_code --mode=audit" scans: - type: "Static Analysis" tool: "ESLint" - type: "Dependencies" tool: "npm audit" - type: "Test Coverage" tool: "Jest --coverage" ui_assessment: description: "Assess UI/UX state" commands: - "/capture_screenshots" - "/compare_design_system" artifacts: - "ui_audit/" - "component_inventory.json" documentation_audit: description: "Audit existing documentation" scan_directories: - "docs/" - "README.md" - "API.md" mapping: - source: "existing_docs/" target: "deliverables/" template: "templates/doc_migration.md" gap_analysis: description: "Generate gap analysis report" command: "/generate_audit_report" args: - "--include=all" - "--output=deliverables/reports/audit_report.md" sections: - "Project Overview" - "Codebase Assessment" - "Documentation Status" - "Test Coverage" - "UI/UX Alignment" - "Security Review" - "Performance Metrics" - "Recommendations" integration_planning: description: "Plan project integration" outputs: - type: "Integration Plan" template: "templates/onboarding/integration_plan.md" sections: - "Timeline" - "Resource Requirements" - "Risk Assessment" - "Migration Steps" - type: "Checklist" template: "templates/onboarding/migration_checklist.md" items: - "Documentation Migration" - "Code Standards Alignment" - "Test Coverage Improvement" - "UI/UX Standardization" - "Security Compliance" post_actions: - command: "/process_audit_findings" args: - "--input=deliverables/reports/audit_report.md" - "--output=deliverables/reports/updated_backlog_report.md" "/process_audit_findings": description: "Process audit report to generate feature requests and bug tickets" parameters: - name: "audit_report" type: "file" description: "The generated audit report file" required: true - name: "output_report" type: "file" description: "Path for the updated backlog report" required: true workflow: parse_findings: description: "Parse audit report for gaps and issues" command: "python scripts/parse_audit_report.py" args: - "--input=${audit_report}" - "--output=.context/parsed_findings.json" validation: - "Check JSON structure" - "Verify findings categorization" feature_creation: description: "Create feature requests from identified gaps" command: "/create_user_story" args: - "--from=.context/parsed_findings.json" - "--type=feature" template: "templates/user_story.md" format: story: "As a [type of user], I want [some goal] so that [some reason]" criteria: - "Given [context]" - "When [action]" - "Then [expected result]" outputs: - "docs/feature-requests/*.md" - "deliverables/product/FRD.md" sprint_planning: description: "Add new stories to sprint backlog" command: "/feature_map" args: - "--add-to-sprint=next_sprint" - "--stories=.context/parsed_findings.json" updates: - "deliverables/product/PRD.md" - ".context/sprint_backlog.json" bug_handling: description: "Process discovered bugs" for_each_bug: - create_branch: command: "git checkout -b bugfix/${bug_id}" - record_bug: command: "echo" args: - "Bug: ${bug_id} - ${description}" - ">>" - "cline_docs/context/bugs.md" - update_context: command: "/update_context" args: - "--type=bug" - "--id=${bug_id}" - "--details=${bug_details}" report_generation: description: "Generate summary of changes" command: "/generate_docs" args: - "--template=templates/backlog_report.md" - "--output=${output_report}" sections: - "New Feature Requests" - "New Bug Tickets" - "Updated Sprint Backlog" - "Context Updates" validation_gates: - after: "parse_findings" check: "Findings properly categorized" - after: "feature_creation" check: "All stories have acceptance criteria" - after: "bug_handling" check: "All bugs documented and tracked" - before: "report_generation" check: "All updates completed" traceability: links: - from: "audit_report.md" to: "docs/feature-requests/*.md" - from: "docs/feature-requests/*.md" to: "deliverables/product/FRD.md" - from: "cline_docs/context/bugs.md" to: "deliverables/reports/updated_backlog_report.md" validation_gates: - after: "knowledge_graph" check: "Graph completeness" - after: "codebase_analysis" check: "Critical issues" - after: "documentation_audit" check: "Required docs present" - before: "integration_planning" check: "All assessments complete" # UI interpretation chain "/init_requirement_docs": description: "Setup initial requirements documentation" workflow: steps: create_requirement_structure: description: "Create directories for requirement docs and write initial templates" actions: - "Create directories: deliverables/documentation/product/" - "Write BRD.md, PRD.md, FRD.md, DBRD.md, SRS.md from templates" # Example tool usage (pseudocode): # Use write_to_file tool to write PRD.md with the provided PRD template content # and similarly for BRD, FRD, DBRD, SRS as needed. # For PRD.md: # <write_to_file> # <path>deliverables/documentation/product/PRD.md</path> # <content> # # (Complete PRD template content from provided snippet) # </content> # </write_to_file> # Repeat similarly for BRD.md, FRD.md, DBRD.md, SRS.md if defined. outputs: - "deliverables/documentation/product/BRD.md" - "deliverables/documentation/product/PRD.md" - "deliverables/documentation/product/FRD.md" - "deliverables/documentation/product/DBRD.md" - "deliverables/documentation/product/SRS.md" link_requirements: description: "Link created documents into .context and cline_docs for reference" actions: - "Update cline_docs/codebase_summary.md with references to new requirement docs" - "Update .context/documentation_index.json to include requirement docs" # Design interpretation chain "/init_design_docs": description: "Setup design phase documentation" workflow: steps: create_design_structure: description: "Create directories for design docs and write initial templates" actions: - "Create directories: deliverables/design/" - "Write UXDD.md, user_persona_report.md, user_journey_map.md, wireframe_spec.md, design_spec.md, design_system.md from templates" # Example: # <write_to_file> # <path>deliverables/design/UXDD.md</path> # <content> # # (UXDD content from snippet) # </content> # </write_to_file> # Similarly for user_persona_report.md, user_journey_map.md, wireframe_spec.md, design_spec.md, design_system.md outputs: - "deliverables/design/UXDD.md" - "deliverables/design/user_persona_report.md" - "deliverables/design/user_journey_map.md" - "deliverables/design/wireframe_spec.md" - "deliverables/design/design_spec.md" - "deliverables/design/design_system.md" integrate_with_ux_research: description: "Integrate design docs with ux_research and ui_design chains" actions: - "Update cline_docs/codebase_summary.md with references to UXDD and related docs" - "Add entries in .context/documentation_index.json linking to design docs" update_dependencies: description: "Parse .context/dependencies.json (if exists) to ensure design docs reference correct components" actions: - "If dependencies file exists, cross-reference UI components mentioned in UXDD or wireframe_spec with codebase_summary" - "Update design_system.md with any component references from dependencies" # Development interpretation chain "/init_dev_docs": description: "Setup design phase documentation" workflow: steps: create_design_structure: description: "Create directories for design docs and write initial templates" actions: - "Create directories: deliverables/design/" - "Write UXDD.md, user_persona_report.md, user_journey_map.md, wireframe_spec.md, design_spec.md, design_system.md from templates" # Example: # <write_to_file> # <path>deliverables/design/UXDD.md</path> # <content> # # (UXDD content from snippet) # </content> # </write_to_file> # Similarly for user_persona_report.md, user_journey_map.md, wireframe_spec.md, design_spec.md, design_system.md outputs: - "deliverables/design/UXDD.md" - "deliverables/design/user_persona_report.md" - "deliverables/design/user_journey_map.md" - "deliverables/design/wireframe_spec.md" - "deliverables/design/design_spec.md" - "deliverables/design/design_system.md" integrate_with_ux_research: description: "Integrate design docs with ux_research and ui_design chains" actions: - "Update cline_docs/codebase_summary.md with references to UXDD and related docs" - "Add entries in .context/documentation_index.json linking to design docs" update_dependencies: description: "Parse .context/dependencies.json (if exists) to ensure design docs reference correct components" actions: - "If dependencies file exists, cross-reference UI components mentioned in UXDD or wireframe_spec with codebase_summary" - "Update design_system.md with any component references from dependencies" # Morpheus Validation phase morpheus_validator_agent: name: "Morpheus" role: "High-Level Validator & Decision Maker" description: "Provides final validation of requirements, architecture, and design decisions" tools: - "prompts/core/reasoning.md" - "prompts/chains/components/code_quality/code_evaluation_agent.xml" - "prompts/chains/components/code_quality/code_generator_agent.xml" - "prompts/chains/components/code_quality/code_improver_agent.xml" - "prompts/chains/components/code_quality/code_rater.xml" - "prompts/chains/components/code_quality/code_quality_chain.xml" responsibilities: - "Validate final requirements" - "Enforce SOLID, YAGNI, KISS principles" - "Prevent premature optimization" - "Ensure adequate test coverage" workflow: requirements_validation: - "Challenge assumptions" - "Simplify solutions" - "Verify business value" - "Ensure acceptance criteria clarity" solution_review: - "Evaluate against SOLID" - "Check YAGNI compliance" - "Check KISS simplicity" - "Assess test coverage"
specialized_agents: # Product Owner: Requirements & Prioritization product_owner: role: "Product Owner" responsibilities: primary: - "Business analysis" - "Requirements gathering" secondary: - "Feature prioritization" - "Stakeholder management" communication: channels: - "direct_message" - "event_queue" message_format: required: - "sender" - "receiver" - "intent" - "payload" deliverables: documentation: templates: - type: "Technical Spec" path: "templates/tech_spec.md" - type: "User Guide" path: "templates/user_guide.md" validation: - "Completeness check" - "Technical accuracy" code: requirements: - "Unit tests" - "Integration tests" - "Documentation" quality_metrics: - "Code coverage" - "Complexity score" tools: - "/init_requirements" - "/feature_map" - "/init_roadmap" chains: - "chains/requirements_chain.md" - "chains/feature_analysis_chain.md" # UX Researcher: Research, Interviews, Surveys ux_researcher: role: "UX Researcher" responsibilities: - "User research planning" - "Interview analysis" - "Survey data processing" - "Insights generation" deliverables: - type: "Research Plan" template: "chains/components/research/research_plan_generator.md" - type: "Research Analysis" template: "chains/components/research/research_analysis_prompt.md" tools: - "/research_init" - "/interview_analyze" - "/survey_process" chains: - "chains/research_planning_chain.md" - "chains/data_analysis_chain.md" # UX Designer: User Journeys, Wireframes, Interaction Design ux_designer: role: "UX Designer" responsibilities: - "User journey mapping" - "Interaction design" - "Information architecture" - "Wireframe creation" deliverables: - type: "Persona" template: "chains/components/ui_ux/persona_generator.md" - type: "User Journey" template: "chains/components/ui_ux/journey_map_generator.md" - type: "Wireframes" template: "chains/components/ui_ux/wireframe-generation-prompt.md" tools: - "/wireframe_init" - "/journey_map" - "/persona_gen" chains: - "chains/ux_design_chain.md" - "chains/wireframe_chain.md" # UI Designer: Visual Design System, Components, Layout ui_designer: role: "UI Designer" responsibilities: - "Visual design system" - "Component library" - "Layout patterns" - "Interactive prototypes" deliverables: - type: "Design System" template: "chains/components/ui_ux/design_system_generator.md" - type: "Component Library" template: "chains/components/ui_ux/component_generator.md" tools: - "/design_system_init" - "/component_gen" - "/style_guide" chains: - "chains/ui_design_chain.md" - "chains/component_library_chain.md" # System Architect: System & API Design, Architecture Diagrams system_architect: role: "System Architect" responsibilities: - "System design" - "Architecture patterns" - "Technical specifications" - "Integration design" deliverables: - type: "Architecture Diagram" template: "chains/components/architecture/architectural-diagram-generator.md" - type: "System Design" template: "chains/components/architecture/generate-high-level-system-architecture.md" - type: "API Design" template: "chains/components/architecture/software_architect_api_designer.md" tools: - "/init_architecture" - "/gen_uml_<uml_type>" - "/api_design" chains: - "chains/architecture_chain.md" - "chains/system_design_chain.md" # Frontend Developer: UI Implementation & Client-Side Logic frontend_developer: role: "Frontend Developer" responsibilities: - "UI implementation" - "Client-side logic" - "Accessibility compliance" - "Performance optimization" rules: - "Follow atomic design principles" - "Ensure responsive design" - "Maintain accessibility standards" tools: commands: - "/ui_implement": description: "Generate UI documentation" workflow: steps: generate_documentation: description: "Use external design system template" template: "templates/design_system/design_system_documentation.xml" actions: - "Parse template and produce design_system_documentation.html from the referenced file" - "/component_build" deliverables: - type: "UI Components" template: "chains/components/development/atomic_design_system.xml" - type: "Frontend Code" template: "chains/components/development/tailwind_class_generator.xml" - type: "Style Guide" template: "chains/components/development/ui-styling-prompt.xml" workflow: implementation: - "Analyze design specs" - "Create component structure" - "Implement UI logic" - "Add styling" - "Ensure responsiveness" quality: template: "chains/components/code_quality/code_evaluation_agent.md" steps: - "Run linting" - "Check accessibility" - "Test cross-browser compatibility" - "Optimize bundle size" # Backend Developer: Server-Side Logic & APIs backend_developer: role: "Backend Developer" responsibilities: - "Server-side logic" - "API development" - "Database interactions" - "Security & performance" rules: - "Follow SOLID principles" - "Implement secure coding practices" - "Optimize database queries" - "Maintain API documentation" tools: - "/api_implement" - "/service_build" - "/init_git" - "/commit" - "/gen_docs" chains: - "chains/api_design_chain.md" - "chains/implementation_analysis_chain.md" - "chains/system_design_chain.md" deliverables: - type: "API Implementation" template: "chains/components/development/implementation-analysis-prompt.meta.md" - type: "Server Code" template: "chains/components/development/generate-high-level-system-architecture.meta.md" - type: "API Documentation" template: "chains/components/development/user-documentation-prompt.meta.md" workflow: implementation: - "Design API endpoints" - "Implement business logic" - "Setup database interactions" - "Add authentication/authorization" quality: template: "chains/components/code_quality/code_improver_agent.md" steps: - "Run security checks" - "Optimize performance" - "Test API endpoints" - "Validate data handling" # Database Developer: Schema & Query Optimization database_developer: role: "Database Developer" responsibilities: - "Database design" - "Data modeling" - "Query optimization" - "Data integrity" rules: - "Ensure data normalization" - "Implement indexing strategy" - "Maintain data integrity" - "Optimize query performance" deliverables: - type: "Database Schema" template: "chains/components/development/generate-tech-stack-BOM.meta.md" - type: "Query Optimization" template: "chains/components/development/performance-testing-prompt.meta.md" - type: "Data Migration" template: "chains/components/development/implementation-analysis-prompt.meta.md" workflow: implementation: - "Design database schema" - "Create indexes" - "Implement stored procedures" - "Setup replication" quality: template: "chains/components/code_quality/code_rater.md" steps: - "Check query performance" - "Validate data integrity" - "Test scalability" - "Monitor resource usage" # System Admin: Infrastructure & Deployment system_admin: role: "System Administrator" responsibilities: - "Infrastructure setup" - "Deployment automation" - "Monitoring & backups" - "Security measures" tools: - "/init_architecture" - "/generate_project_structure" - "/gen_uml_<uml_type>" - "/api_design" deliverables: - type: "Infrastructure Setup" template: "chains/components/development/architectural-diagram-generator.meta.md" - type: "Deployment Config" template: "chains/components/development/monitoring-setup-prompt.meta.md" - type: "Monitoring Setup" template: "chains/components/development/security-documentation-prompt.meta.md" workflow: implementation: - "Setup infrastructure" - "Configure CI/CD" - "Implement monitoring" - "Setup backup system" quality: template: "chains/components/code_quality/code_generator_agent.md" steps: - "Test infrastructure" - "Validate security" - "Check performance"
common_attributes: communication: channels: - "direct_message" - "event_queue" message_format: required: - "sender" - "receiver" - "intent" - "payload" quality_control: review_process: - "Peer review" - "Quality metrics" - "Documentation check" quality_gates: code_review: checklist: - "Code style compliance" - "Test coverage" - "Documentation completeness" approvers: required: 2 roles: - "Senior Developer" - "Tech Lead" deployment: requirements: - "All tests passing" - "Security scan complete" - "Performance benchmarks met"
workflows: phases: - name: "requirements" description: "Gather and validate requirements" chains: - "chains/requirements_chain.md" - "chains/feature_analysis_chain.md"
- name: "architecture" description: "High-level system architecture and technical decisions" chains: - "chains/architecture_chain.md" - name: "system_design" description: "Detailed system design, including UML diagrams and integration points" chains: - "chains/system_design_chain.md" - name: "ux_research" description: "User research planning and analysis" chains: - "chains/research_planning_chain.md" - "chains/data_analysis_chain.md" - name: "ux_design" description: "User experience design, user journeys, and wireframes" chains: - "chains/ux_design_chain.md" - "chains/wireframe_chain.md" # Consolidate research analysis prompts into UX phase if needed - name: "ui_design" description: "UI component library, style guides, and visual design system" chains: - "chains/ui_design_chain.md" - "chains/component_library_chain.md" - name: "development" description: "Frontend and backend implementation, code quality, code generation" chains: - "chains/code_quality_chain.md" - "chains/code_improver_chain.md" - "chains/code_rater_chain.md" - "chains/code_generator_chain.md" - "chains/code_evaluation_chain.md" - "chains/implementation_analysis_chain.md" - "chains/api_design_chain.md" - name: "testing" description: "Testing at various levels: unit, integration, E2E" chains: - "chains/testing/unit_test_chain.md" - "chains/testing/integration_test_chain.md" - "chains/testing/e2e_test_chain.md" - "chains/testing/security_test_chain.md" - "chains/testing/performance_test_chain.md" - name: "deployment" description: "Infrastructure setup, CI/CD, and monitoring" # Add any relevant chains for deployment phase # chains: # - "chains/deployment_chain.md" (if exists) # Define the standard lifecycle flow: sequence: - "requirements" - "architecture" - "system_design" - "ux_research" - "ux_design" - "ui_design" - "development" - "testing" - "deployment"
requirement_gathering: agent: role: "Requirements Clarification Specialist" responsibilities: - "Identify unclear requirements proactively" - "Generate targeted clarifying questions" - "Document evolving requirements" workflow: phases: initialization: steps: - "Await initial user stories or feature requests" - "Analyze completeness of provided requirements" - "Generate clarifying questions" - "Document confirmed requirements" gathering: questions: - "What is the feature title?" - "Please describe the feature in detail." - "Who are the primary users?" - "What problem does this feature solve?" - "What are the expected outcomes?" - "Any technical constraints?" - "Priority level? (High/Medium/Low)" validation_rules: - "No implementation without clear, validated requirements" - "No documentation finalization without user request" - "No diagrams without explicit need" templates: feature_request: format: overview: fields: - "Title" - "Description" users: fields: - "Target Users" - "User Needs" details: fields: - "Problem Statement" - "Expected Outcomes" - "Technical Constraints" - "Priority Level" dependencies: fields: - "Auto-detected Dependencies"
principles: kiss: name: "Keep It Simple, Stupid" guidelines: - "Favor straightforward solutions" - "Prioritize maintainability" yagni: name: "You Aren't Gonna Need It" guidelines: - "Implement only currently required features" - "Avoid speculative additions" commands: "/init_requirements": description: "Initialize requirements gathering" workflow: - "Setup requirements structure" - "Initialize templates" - "Configure tracking" "/feature_map": description: "Generate feature mapping" workflow: - "Analyze gathered requirements" - "Create feature hierarchy" - "Set dependencies" "/validate_requirements": description: "Validate gathered requirements" workflow: - "Check completeness" - "Verify clarity" - "Apply KISS/YAGNI" - "Ensure testability" documentation: deliverables: - type: "BRD" template: "templates/business_requirements_document.md" - type: "PRD" template: "templates/product_requirements_document.md" - type: "FRD" template: "templates/feature_requirements_document.md" quality_checks: requirements_validation: checklist: - "Requirements are unambiguous" - "Success criteria are measurable" - "User needs defined" - "Technical constraints documented" - "Dependencies identified" - "Priority set" - "Stakeholders reviewed" best_practices: do: - "Start from user needs" - "Use clear, simple language" - "Document assumptions" - "Include acceptance criteria" - "Validate with stakeholders" - "Track changes" don't: - "Add implementation details prematurely" - "Make assumptions without validation" - "Skip stakeholder validation" - "Ignore non-functional requirements" - "Rush through clarification" integration: version_control: - "Store requirements in VCS" - "Track changes" - "Maintain history" documentation_links: - "Link requirements to user stories" - "Connect to specs" - "Reference architectural decisions" quality_assurance: - "Ensure testability" - "Link to test cases" - "Maintain traceability matrix" error_prevention: validation_steps: - "Double-check all gathered requirements" - "Verify stakeholder sign-off" - "Ensure clear acceptance criteria" - "Document assumptions" - "Track open questions" - "Maintain requirement traceability" notes: smart_criteria: - "Specific" - "Measurable" - "Achievable" - "Relevant" - "Time-bound" maintenance: - "Regular stakeholder reviews" - "Keep documentation updated" - "Track changes systematically" - "Maintain clear communication channels" requirements_traceability: structure: epic: template: "templates/requirements/epic_template.md" components: - "business_value" - "success_metrics" - "constraints" - "dependencies"
design_management: # This section manages the design phases of the SDLC: ux_research → ux_design → ui_design. # It defines triggers, documentation templates, and deliverables for each sub-phase. # Triggers: Once requirements are validated and documented (e.g., PRD completed and validated), # the design phase can start, beginning with user research, followed by UX design, then UI design.
triggers: # Trigger after requirements validation: after_requirements_validation: action: "/init_design_phase" description: "Initialize design phase once PRD and requirements are finalized" validation: - "Check PRD completeness" - "Verify clarity of requirements" - "Confirm stakeholder approval" documentation: uxdd_components: # Organized by sub-phase (ux_research, ux_design, ui_design) ux_research: user_research_report: template: "templates/design/research_report.md" sections: - "Research objectives" - "Methodology" - "Key findings" - "Recommendations" user_personas: template: "templates/design/persona_template.md" sections: - "Demographics" - "Goals and needs" - "Pain points" - "Behaviors" ux_design: user_journeys: template: "templates/design/journey_template.md" sections: - "User goals" - "Journey stages" - "Touch points" - "Pain points" - "Opportunities" wireframes: template: "templates/design/wireframe_template.md" organization: by_user_flow: - "User registration flow" - "Core feature flows" - "Settings flows" by_component: - "Navigation components" - "Form components" - "Content components" annotations: types: - "User interactions" - "Data elements" - "State changes" - "Component behavior" svg_generation: command: "/generate_svg" output: "deliverables/design/wireframes/*.svg" embedding: "auto-embed into UXDD.md" ui_design: object_oriented_ux: template: "templates/design/ooux_template.md" sections: - "Object mapping" - "Relationship diagrams" - "Core objects" - "Object attributes" design_system: template: "templates/design/design_system_generator.md" component_library: template: "templates/design/component_generator.md" prototype: simple_prototype: template: "templates/design/prototype_template.md" technologies: - "HTML" - "CSS" - "JavaScript" features: - "Basic interactions" - "Navigation flow" - "Form handling" output: - "deliverables/design/prototype/index.html" - "deliverables/design/prototype/styles.css" - "deliverables/design/prototype/script.js" # Consolidate UX documentation into a single UXDD at the end of the design phases commands: "/init_design_phase": description: "Initialize design phase after requirements validation" workflow: - "Load validated PRD content" - "Setup UXDD structure" - "Initialize ux_research tasks" - "Create tracking system" "/new_feature_design": description: "Handle new feature’s design process" workflow: - "Analyze final requirements" - "Update user journeys" - "Create wireframes" - "Update prototype" - "Update UXDD" deliverables: - "Updated user journeys" - "Feature wireframes" - "Prototype updates" - "UXDD updates" "/consolidate_uxdd": description: "Consolidate all UX documentation into a final UXDD" workflow: - "Gather all UX research & design components" - "Generate final UXDD" - "Embed SVG wireframes" - "Create comprehensive index" output: file: "deliverables/documentation/design/UXDD.md" sections: - name: "Research" sources: - "deliverables/design/user_research_report.md" - "deliverables/design/user_personas.md" - name: "Design" sources: - "deliverables/design/ooux_template.md" - "deliverables/design/journey_template.md" - "deliverables/design/wireframes/*.svg" - name: "Prototype" sources: - "deliverables/design/prototype_documentation.md" - "deliverables/design/prototype_screenshots"
development_management:
development: commands: "/dev_init": description: "Set up the development environment" workflow: - "Environment setup (install dependencies, configure tools)" - "Code scaffolding (generate initial structure)" - "Testing framework initialization" "/test_init": description: "Initialize testing environment" workflow: - "Set up test frameworks (unit, integration)" - "Configure test scripts" - "Prepare test data and mocks" "/test_unit": description: "Run unit tests" workflow: - "Execute unit tests" - "Generate test reports" - "Check code coverage" "/test_integration": description: "Run integration tests" workflow: - "Execute integration tests" - "Validate service interactions" - "Check integration coverage reports" "/analyze_code": description: "Run code analysis tools for quality checks" parameters: - files: "Files to analyze" - depth: "Analysis depth" workflow: - "Run ESLint or equivalent linters" - "Execute SonarQube or CodeClimate analysis" - "Generate quality reports" - "Identify technical debt" "/optimize_code": description: "Perform code optimization steps" workflow: - "Refactor complex areas" - "Improve performance hotspots" - "Reduce bundle size" - "Enhance maintainability" "/validate_config": description: "Validate configuration against schema" workflow: - "run: yq -o=json ./.github/config.yaml > ./config.json" - "run: npx ajv validate -s ./.github/schema.json -d ./config.json" - "Check results and proceed if successful" "/create_nextra_project": description: "Create and configure a Nextra project with Atomic Design System" workflow: - name: "Project Creation" steps: - "Create project directory" - "Initialize Nextra project" - "Configure dependencies" command: | mkdir project-site && cd project-site && \ npx create-next-app@latest . --typescript --tailwind --eslint && \ npm install nextra nextra-theme-docs && \ npm install @radix-ui/react-icons @radix-ui/react-slot clsx tailwind-merge && \ npm install @radix-ui/react-accordion @radix-ui/react-alert-dialog @radix-ui/react-aspect-ratio && \ npm install @radix-ui/react-avatar @radix-ui/react-checkbox @radix-ui/react-collapsible && \ npm install @radix-ui/react-context-menu @radix-ui/react-dialog @radix-ui/react-dropdown-menu && \ npm install @radix-ui/react-hover-card @radix-ui/react-label @radix-ui/react-menubar && \ npm install @radix-ui/react-navigation-menu @radix-ui/react-popover @radix-ui/react-progress && \ npm install @radix-ui/react-radio-group @radix-ui/react-scroll-area @radix-ui/react-select && \ npm install @radix-ui/react-separator @radix-ui/react-slider @radix-ui/react-switch && \ npm install @radix-ui/react-tabs @radix-ui/react-toast @radix-ui/react-toggle && \ npm install @radix-ui/react-tooltip && \ npm install class-variance-authority tailwindcss-animate framer-motion - name: "Configuration Setup" steps: - "Configure Nextra" - "Setup Tailwind" - "Configure TypeScript" files: - path: "next.config.js" content: | const withNextra = require('nextra')({ theme: 'nextra-theme-docs', themeConfig: './theme.config.jsx' }) module.exports = withNextra() - path: "theme.config.jsx" content: | export default { logo: <span>Atomic Design System</span>, project: { link: 'https://github.com/yourusername/project-name' }, docsRepositoryBase: 'https://github.com/yourusername/project-name', footer: { text: 'Atomic Design System Documentation' } } - name: "Directory Structure" steps: - "Create atomic design directories" - "Setup documentation structure" structure: - pages: - atoms: - button.mdx - input.mdx - typography.mdx - molecules: - form-field.mdx - card.mdx - organisms: - form.mdx - navigation.mdx - templates: - page-layout.mdx - design-system: - colors.mdx - spacing.mdx - typography.mdx - components: - ui - index.mdx - name: "Component Setup" steps: - "Initialize shadcn-ui components" - "Setup Framer Motion animations" command: | npx shadcn-ui@latest init && \ npx shadcn-ui@latest add button card form input label tabs - name: "Documentation Setup" steps: - "Create initial documentation" - "Setup component examples" files: - path: "pages/index.mdx" content: | # Atomic Design System Welcome to our Atomic Design System documentation. This system is built using: - Next.js - Tailwind CSS - shadcn/ui - Framer Motion ## Getting Started Browse through our component categories: - [Atoms](/atoms) - Basic building blocks - [Molecules](/molecules) - Simple component combinations - [Organisms](/organisms) - Complex component combinations - [Templates](/templates) - Page-level layouts ## Design Tokens Explore our design foundations: - [Colors](/design-system/colors) - [Typography](/design-system/typography) - [Spacing](/design-system/spacing) - name: "Final Setup" steps: - "Install remaining dependencies" - "Build initial version" command: | npm run build && \ echo "Nextra Atomic Design System project setup complete!" validation: - "Verify all dependencies installed" - "Check configuration files" - "Validate component structure" - "Test documentation build" # Tools and checks code_quality: analysis_tools: - "ESLint" - "SonarQube" - "CodeClimate" steps: - "Run linters" - "Assess code complexity" - "Check test coverage" - "Review documentation completeness" # Database initialization and environment setup database_initialization: "/init_database": description: "Initialize database environment and structure" workflow: - "Select database type (Postgres, MongoDB, etc.)" - "Configure connection" - "Set up schema using migrations" - "Initialize seed data if needed" database_types: postgres: setup: - name: "Initialize PostgreSQL" commands: - "docker run --name project-db -e POSTGRES_PASSWORD=password -d postgres" - "npx prisma init" configuration: - DATABASE_URL="postgresql://postgres:password@localhost:5432/mydb" - name: "Setup Prisma" steps: - "Create schema.prisma" - "Generate client" - "Run initial migration" mongodb: setup: - name: "Initialize MongoDB" commands: - "docker run --name mongo-db -d mongo" - "npm install mongoose" configuration: - MONGODB_URI="mongodb://localhost:27017/mydb" - name: "Setup Mongoose" steps: - "Create schema models" - "Configure connections" - "Initialize indexes" schema_management: "/create_schema": description: "Generate database schema from models" workflow: - "Analyze data models" - "Generate schema file" - "Setup relationships" - "Create indexes" "/run_migration": description: "Create and run database migrations" workflow: - "Generate migration files" - "Validate changes" - "Apply migrations" - "Verify database state" data_management: "/seed_database": description: "Seed database with initial data" workflow: - "Load seed data files" - "Validate data format" - "Insert seed data" - "Verify data integrity" "/backup_database": description: "Create database backup" workflow: - "Lock tables" - "Export data" - "Export schema" - "Store backup" security: setup: - "Create database users" - "Set permissions" - "Configure authentication" - "Setup encryption" policies: - "Password requirements" - "Access controls" - "Data encryption" - "Audit logging" monitoring: metrics: - "Connection pool status" - "Query performance" - "Storage usage" - "Backup status" alerts: - "Connection issues" - "Performance degradation" - "Storage warnings" - "Backup failures" maintenance: "/optimize_db": description: "Perform database optimization" workflow: - "Analyze performance" - "Optimize indexes" - "Vacuum tables" - "Update statistics" "/health_check": description: "Check database health" workflow: - "Check connections" - "Verify replication" - "Check disk space" - "Validate backups"
document_management: # Directories - cline_docs, directories: cline_docs: "cline_docs/" internal_docs: - name: "project_roadmap.md" purpose: "Track high-level goals, progress, and milestones" - name: "current_task.md" purpose: "Record current objectives and context" - name: "tech_stack.md" purpose: "Document chosen technologies and frameworks" - name: "codebase_summary.md" purpose: "Overview of project structure, data flow, dependencies" deliverables: structure: requirements: - "BRD.md" # Business Requirements Document - "PRD.md" # Product Requirements Document - "FRD.md" # Feature Requirements Document - "DBRD.md" # Database Requirements Document - "SRS.md" # Software Requirements Specification design: core: - "UXDD.md" # UX Design Document architecture: - "system_architecture.md" - "deployment_architecture.md" ui_design: - "design_system.md" - "style_guide.md" component_library: - "components.md" - "patterns.md" development: - "API_specs/" - "database_specs/" - "security_specs/"
# Add project onboarding functionality project_onboarding: commands: "/onboard_existing_project": description: "Onboard existing project into SDLC orchestration" workflow: discovery: - "Scan existing codebase structure" - "Identify existing documentation" - "Map current test coverage" - "Analyze deployment setup" normalization: - "Align with standard directory structure" - "Convert docs to template format" - "Standardize naming conventions" validation: - "Run config validation" - "Check documentation completeness" - "Verify test coverage" integration: - "Link to workflow phases" - "Setup CI/CD pipelines" - "Configure monitoring" outputs: - type: "Gap Analysis Report" template: "templates/onboarding/gap_analysis.md" - type: "Integration Plan" template: "templates/onboarding/integration_plan.md" - type: "Migration Checklist" template: "templates/onboarding/migration_checklist.md" matrix: template: "templates/traceability/matrix_template.md" links: - from: "deliverables/product/FRD.md" to: - "tests/results/" - "tests/performance/" - from: "deliverables/design/UXDD.md" to: - "deliverables/product/PRD.md" - "deliverables/product/FRD.md" security_compliance: standards: - name: "OWASP Top 10" validation_chain: "chains/security/owasp_validation_chain.md" - name: "GDPR" validation_chain: "chains/security/gdpr_validation_chain.md" checks: - "Security vulnerability scanning" - "Dependency vulnerability checks" - "Code security analysis" - "Access control validation" validation_workflow: triggers: - after: "/generate_structure" run: "/validate_config" - after: "/dev_init" run: "/validate_config" - before: "testing" run: "/validate_config" ci_cd_integration: requirements: - tool: "yq" purpose: "YAML processing" installation: "npm install -g yq" - tool: "ajv" purpose: "JSON Schema validation" installation: "npm install -g ajv-cli" workflow: - "Convert YAML to JSON using yq" - "Validate against schema using ajv" - "Generate validation report" - "Block pipeline if validation fails" schema_validation: mandatory_fields: agent: - "role" - "responsibilities" - "tools" workflow: - "name" - "description" - "chains" enums: workflow_phases: - "requirements" - "architecture" - "system_design" - "ux_research" - "ux_design" - "ui_design" - "development" - "testing" - "deployment" # Add new commands for the development management phase development_management: commands: "/update_context": description: "Update context management system with latest changes" workflow: - name: "Check for Changes" description: "Identify changes in the project context" command: "/detect_changes" output: "changes_detected.json" - name: "Update Vector Store" description: "Update the vector store with new context data" command: "/update_vector_store" args: - "changes_detected.json" output: "vector_store_updated.json" - name: "Sync with Agents" description: "Synchronize updated context with all relevant agents" command: "/sync_agents" args: - "vector_store_updated.json" output: "agents_synced.json" - name: "Update Documentation" description: "Reflect changes in the project documentation" command: "/update_docs" args: - "agents_synced.json" output: "documentation_updated.json" validation: - "Ensure vector store is updated correctly" - "Verify all agents are synchronized" - "Check documentation reflects latest changes" context_management: codebase_context: description: "Codebase Context Specification (CCS) implementation" version: "1.1-RFC" structure: root_directory: ".context/" core_files: - name: "index.md" description: "Primary entry point with YAML front matter" required: true - name: "docs.md" description: "Extended documentation and guides" required: true directories: - name: "diagrams/" description: "Architectural and workflow diagrams" - name: "images/" description: "Supporting visual assets" initialization: command: "/init_context" steps: - name: "Create Directory Structure" action: "create_directories" paths: - ".context/" - ".context/diagrams/" - ".context/images/" - name: "Initialize Core Files" action: "create_files" templates: index_md: path: ".context/index.md" content_template: | --- module-name: "${project_name}" description: "${project_description}" technologies: [] related-modules: [] permissions: "read-write" version: "1.0.0" --- # ${project_name} ## Module Overview ## Architecture ## Domain Logic ## Integration Points ## Configuration docs_md: path: ".context/docs.md" content_template: | # Extended Documentation ## Tutorials ## Domain-Specific Guidance - name: "Initialize .contextignore" action: "create_file" path: ".contextignore" content: | # Build outputs dist/ build/ # Dependencies node_modules/ # Test artifacts **/__snapshots__/ *.test.js.snap # Temporary files *.tmp *.log indexing: command: "/index_context" steps: - name: "Parse Context Files" action: "parse_markdown" targets: - ".context/**/*.md" exclude: - file: ".contextignore" parser_config: extract_front_matter: true parse_mermaid: true process_links: true - name: "Generate Embeddings" action: "create_embeddings" config: model: "text-embedding-ada-002" dimensions: 1536 batch_size: 100 - name: "Index Context" action: "index_context" metadata: - "module_name" - "technologies" - "permissions" - "version" module_management: command: "/manage_modules" operations: create_module: description: "Create new module context" steps: - "Create module .context directory" - "Initialize module index.md" - "Update root index.md references" link_module: description: "Link external module context" steps: - "Validate external reference" - "Add to related-modules in front matter" - "Update context index" visualization: command: "/visualize_context" generators: - name: "Architecture Diagram" type: "mermaid" source: "diagrams/architecture.md" output: "diagrams/architecture.svg" - name: "Module Hierarchy" type: "mermaid" source: "diagrams/modules.md" output: "diagrams/modules.svg" validation: command: "/validate_context" checks: - "Verify required files exist" - "Validate YAML front matter" - "Check link integrity" - "Validate module references" - "Verify diagram syntax" integration: vector_db: - name: "Index Context in Vector DB" description: "Add context content to vector database" steps: - "Extract content from .context directory" - "Generate embeddings" - "Store in vector DB with metadata" - name: "Context Queries" description: "Query patterns for context retrieval" examples: - "Find related modules" - "Search architecture patterns" - "Locate domain concepts" knowledge_graph: - name: "Build Context Graph" description: "Create graph representation of context" nodes: - "Modules" - "Technologies" - "Integration points" edges: - "Dependencies" - "Relationships" - "Data flow" prompt_processing: description: "Prompt improvement and compression pipeline" version: "1.0.0" pipeline: command: "/process_prompt" steps: - name: "Meta-Prompt Enhancement" description: "Enhance user input using meta-prompt template" action: "enhance_prompt" input: - type: "user_input" description: "Original user query or request" - type: "template" source: "prompts/meta-prompt.txt" description: "Meta-prompt template for enhancement" output: type: "enhanced_prompt" format: "text" validation: - "Check template variables are filled" - "Verify prompt structure" - "Ensure context preservation" - name: "Initial LLM Processing" description: "Process enhanced prompt through base LLM" action: "process_llm" input: type: "enhanced_prompt" source: "previous_step" config: model: "gpt-4" temperature: 0.7 max_tokens: 2000 output: type: "llm_response" format: "text" validation: - "Check response completeness" - "Verify response relevance" - name: "Context Enrichment" description: "Enrich prompt with relevant context and knowledge" action: "enrich_context" input: - type: "llm_response" source: "previous_step" - type: "context_sources" sources: vector_db: - collection: "codebase_context" query_type: "semantic" top_k: 5 - collection: "design_system" query_type: "semantic" top_k: 3 knowledge_graph: - node_types: ["modules", "components", "patterns"] edge_types: ["depends_on", "implements", "uses"] max_depth: 2 context_directory: - path: ".context/" file_patterns: ["*.md", "diagrams/*.md"] enrichment_rules: - name: "Code Context" priority: "high" sources: ["codebase_context"] max_tokens: 1000 - name: "Design Patterns" priority: "medium" sources: ["design_system"] max_tokens: 500 - name: "Architecture Context" priority: "high" sources: ["knowledge_graph", "context_directory"] max_tokens: 800 output: type: "enriched_prompt" format: "text" sections: - "Original Response" - "Relevant Code Context" - "Design System Context" - "Architectural Context" validation: - "Check context relevance" - "Verify context integration" - "Ensure context size limits" - name: "Prompt Compression" description: "Compress and optimize enriched prompt" action: "compress_prompt" input: - type: "enriched_prompt" source: "previous_step" - type: "compression_template" source: "prompts/core/docs/prompt-compression.md" description: "Compression guidelines and rules" compression_rules: - name: "Context Preservation" priority: "highest" description: "Preserve critical context while removing redundancy" - name: "Knowledge Integration" priority: "high" description: "Maintain essential knowledge elements" - name: "Clarity Enhancement" priority: "medium" description: "Improve clarity without losing meaning" output: type: "final_prompt" format: "text" sections: - "Compressed Query" - "Essential Context" - "Key Knowledge Points" validation: - "Check compression ratio" - "Verify information preservation" - "Ensure clarity and coherence" - "Validate context retention" optimization: metrics: - name: "Compression Ratio" description: "Ratio of final to original prompt length" target: "≤ 0.7" - name: "Context Retention" description: "Percentage of critical context preserved" target: "≥ 95%" - name: "Knowledge Integration" description: "Effectiveness of knowledge incorporation" target: "≥ 0.9" - name: "Response Quality" description: "Relevance and coherence of responses" target: "≥ 0.8" monitoring: metrics: - "Pipeline latency" - "Compression efficiency" - "Context preservation score" - "Knowledge integration score" - "Response quality rating" alerts: - condition: "compression_ratio > 0.8" message: "Low compression achievement" - condition: "context_retention < 0.9" message: "Critical context loss detected" - condition: "knowledge_integration < 0.8" message: "Poor knowledge integration detected"