Primary Workflow

Primary Workflow

IMPORTANT: Analyze the skills catalog and activate the skills that are needed for the task during the process. IMPORTANT: Ensure token efficiency while maintaining high quality.

---

Ultrathink Detection (Enhanced Reasoning Mode)

Trigger: If user message contains "ultrathink" (case-insensitive), activate enhanced mode.

When ultrathink is detected:

1. Follow workflows/ultrathink-mode.md protocol
2. Use ultrathink-coordinator agent for orchestration
3. Generate 3+ approaches before selecting
4. Validate rigorously before delivery

See ultrathink-mode.md for full protocol.

---

1. Code Implementation

• Before you start, delegate to planner agent to create a implementation plan with TODO tasks in ./plans directory.
• When in planning phase, use multiple researcher agents in parallel to conduct research on different relevant technical topics and report back to planner agent to create implementation plan.
• Write clean, readable, and maintainable code
• Follow established architectural patterns
• Implement features according to specifications
• Handle edge cases and error scenarios
• DO NOT create new enhanced files, update to the existing files directly.
• [IMPORTANT] After creating or modifying code file, run compile command/script to check for any compile errors.

2. Testing

• Delegate to tester agent to run tests and analyze the summary report.
  • Write comprehensive unit tests
  • Ensure high code coverage
  • Test error scenarios
  • Validate performance requirements
• Tests are critical for ensuring code quality and reliability, DO NOT ignore failing tests just to pass the build.
• IMPORTANT: make sure you don't use fake data, mocks, cheats, tricks, temporary solutions, just to pass the build or github actions.
• IMPORTANT: Always fix failing tests follow the recommendations and delegate to tester agent to run tests again, only finish your session when all tests pass.

3. Code Quality

• After finish implementation, delegate to code-reviewer agent to review code.
• Follow coding standards and conventions
• Write self-documenting code
• Add meaningful comments for complex logic
• Optimize for performance and maintainability

4. Security Scan (NEW - Phase 02)

• Before deployment, delegate to security-auditor agent for security validation.
• Run /security:scan for quick vulnerability check.
• For production deployments, run /security:audit for comprehensive review.
• Address any Critical/High severity findings before proceeding.
• Use /compliance:check to validate SOC2/GDPR requirements if applicable.

5. Deployment (NEW - Phase 01/03)

• Delegate to devops-engineer agent for deployment orchestration.
• Use release-manager agent for changelogs and versioning.
• Deployment sequence:
  1. /deploy:preview - Deploy to preview environment for testing
  2. /deploy:staging - Deploy to staging for QA validation
  3. /security:scan - Final security check before production
  4. /deploy:production - Deploy to production
  5. /deploy:status - Monitor deployment health
• For incidents, delegate to ops-analyst agent:
  • /ops:logs - Analyze application logs
  • /ops:health - Check system health
  • /incident:respond - Initiate incident response workflow
  • /ops:postmortem - Generate blameless post-mortem

6. Integration

• Always follow the plan given by planner agent
• Ensure seamless integration with existing code
• Follow API contracts precisely
• Maintain backward compatibility
• Document breaking changes
• Delegate to docs-manager agent to update docs in ./docs directory if any.

7. Debugging

• When a user report bugs or issues on the server or a CI/CD pipeline, delegate to debugger agent to run tests and analyze the summary report.
• Read the summary report from debugger agent and implement the fix.
• Delegate to tester agent to run tests and analyze the summary report.
• If the tester agent reports failed tests, fix them follow the recommendations and repeat from the Step 2.

---

Agent Summary