The 6-Step Development Workflow

GigiKit enforces a consistent 6-step pipeline for every feature, bug fix, or refactor. Each step is handled by a specialized agent, so nothing falls through the cracks.

flowchart LR
A[1. Code Implementation] —> B[2. Testing]
B —> C[3. Code Quality]
C —> D[4. Integration]
D —> E[5. Debugging]
E —> F[6. Visual Explanations]
style A fill:#4f46e5,color:#fff
style B fill:#0891b2,color:#fff
style C fill:#059669,color:#fff
style D fill:#d97706,color:#fff
style E fill:#dc2626,color:#fff
style F fill:#7c3aed,color:#fff

Step 1: Code Implementation

Before writing a single line of code, delegate to the planner agent to produce a phased implementation plan in ./plans. During planning, spawn multiple researcher agents in parallel to investigate different technical topics and feed their findings back to the planner.

Key rules for this step:

• Follow the plan phases exactly — do not skip ahead
• Update existing files; never create a “new enhanced version” of a file
• After every file change, run the compile command to catch errors early

Step 2: Testing

Delegate to the tester agent once the code compiles cleanly. Tests run against the final simplified code, not an in-progress draft.

The tester agent covers:

• Comprehensive unit tests with high code coverage
• Error and edge-case scenarios
• Performance requirement validation

Step 3: Code Quality

After tests pass, delegate to code-reviewer to audit the clean, tested code. The reviewer checks for readability, adherence to coding conventions, and optimization opportunities. This step runs on the same code the tests verified — not an earlier draft.

Step 4: Integration

Follow the plan from Step 1 exactly when merging changes into the main codebase. Maintain backward compatibility, document any breaking changes, and delegate to docs-manager to update ./docs if the integration touches public APIs or architecture.

Step 5: Debugging

When a bug is reported from a server or CI/CD pipeline, delegate to the debugger agent first. The debugger runs diagnostics and produces a summary report. Read the report, implement the fix, then send the patched code through the tester again. If tests fail, re-enter Step 3 (Code Quality) before merging.

Step 6: Visual Explanations

Use visuals whenever a topic has three or more interacting components, or when a user asks “explain” or “how does X work.”

Visuals save to the active plan folder (injected by hooks) or fall back to plans/visuals/.

Related Guides

• Sequential & Parallel Orchestration — how agents are chained and run in parallel
• Agent Chaining Patterns — concrete chain templates for common scenarios
• Creating Implementation Plans — how the planner agent structures ./plans