Files

T

shancheas f2f0be111a chore: update .gitignore and improve coding standards documentation

- Added .cursor/sessions/* to .gitignore to prevent session files from being tracked.
- Enhanced coding standards in SKILL.md by adding semicolons to TypeScript examples for consistency.
- Improved formatting in continuous learning, detail layout, and other SKILL.md files for better readability.

These changes aim to streamline development processes and maintain code quality across the project.

2026-08-25 17:50:17 +07:00

3.3 KiB

Raw Blame History

Orchestrate Command

Sequential agent workflow for complex tasks.

Usage

/orchestrate [workflow-type] [task-description]

Workflow Types

feature

Full feature implementation workflow:

planner -> tdd-guide -> code-reviewer -> security-reviewer

bugfix

Bug investigation and fix workflow:

explorer -> tdd-guide -> code-reviewer

refactor

Safe refactoring workflow:

architect -> code-reviewer -> tdd-guide

security

Security-focused review:

security-reviewer -> code-reviewer -> architect

Execution Pattern

For each agent in the workflow:

Invoke agent with context from previous agent
Collect output as structured handoff document
Pass to next agent in chain
Aggregate results into final report

Handoff Document Format

Between agents, create handoff document:

## HANDOFF: [previous-agent] -> [next-agent]

### Context

[Summary of what was done]

### Findings

[Key discoveries or decisions]

### Files Modified

[List of files touched]

### Open Questions

[Unresolved items for next agent]

### Recommendations

[Suggested next steps]

Example: Feature Workflow

/orchestrate feature "Add user authentication"

Executes:

Planner Agent
- Analyzes requirements
- Creates implementation plan
- Identifies dependencies
- Output: HANDOFF: planner -> tdd-guide
TDD Guide Agent
- Reads planner handoff
- Writes tests first
- Implements to pass tests
- Output: HANDOFF: tdd-guide -> code-reviewer
Code Reviewer Agent
- Reviews implementation
- Checks for issues
- Suggests improvements
- Output: HANDOFF: code-reviewer -> security-reviewer
Security Reviewer Agent
- Security audit
- Vulnerability check
- Final approval
- Output: Final Report

Final Report Format

ORCHESTRATION REPORT
====================
Workflow: feature
Task: Add user authentication
Agents: planner -> tdd-guide -> code-reviewer -> security-reviewer

SUMMARY
-------
[One paragraph summary]

AGENT OUTPUTS
-------------
Planner: [summary]
TDD Guide: [summary]
Code Reviewer: [summary]
Security Reviewer: [summary]

FILES CHANGED
-------------
[List all files modified]

TEST RESULTS
------------
[Test pass/fail summary]

SECURITY STATUS
---------------
[Security findings]

RECOMMENDATION
--------------
[SHIP / NEEDS WORK / BLOCKED]

Parallel Execution

For independent checks, run agents in parallel:

### Parallel Phase

Run simultaneously:

- code-reviewer (quality)
- security-reviewer (security)
- architect (design)

### Merge Results

Combine outputs into single report

Arguments

$ARGUMENTS:

feature <description> - Full feature workflow
bugfix <description> - Bug fix workflow
refactor <description> - Refactoring workflow
security <description> - Security review workflow
custom <agents> <description> - Custom agent sequence

Custom Workflow Example

/orchestrate custom "architect,tdd-guide,code-reviewer" "Redesign caching layer"

Tips

Start with planner for complex features
Always include code-reviewer before merge
Use security-reviewer for auth/payment/PII
Keep handoffs concise - focus on what next agent needs
Run verification between agents if needed

3.3 KiB Raw Blame History