lead

Orchestrate developer and reviewer agents for multi-phase implementation tasks.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/rk-terence/TokenPulse --skill lead-rk-terence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lead
Source: https://github.com/rk-terence/TokenPulse/tree/main/.agents/skills/lead
Command: npx skills add https://github.com/rk-terence/TokenPulse --skill lead-rk-terence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires developer, reviewer, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of managing multi-phase implementation tasks by orchestrating developer and reviewer agents, ensuring efficient task scoping, execution, and review.

Core Features & Use Cases

  • Task Orchestration: Facilitates collaboration between developers and reviewers, guiding the workflow from initial design to final implementation.
  • Dynamic Task Decomposition: Automatically decomposes tasks into manageable phases, allowing for flexible and efficient development cycles.
  • Review Loop Management: Manages the developer-reviewer loop, ensuring thorough code review and prompt resolution of issues.

Quick Start

To activate leader mode, run the command: /lead "path/to/design_doc" or provide a task description.

Frequently Asked Questions about lead

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate developer and reviewer agents for multi-phase implementation?

To orchestrate developer and reviewer agents, this skill scopes tasks, routes phases, and manages the review loop from design doc parsing to final audit. It automates task decomposition to guide the workflow through execution and issue resolution.

How does task decomposition work for complex software engineering projects?

Task decomposition for complex software engineering projects works by automatically breaking down large scopes into manageable phases. This allows flexible development cycles by routing decomposed tasks between developer and reviewer subagents for execution and review.

Do I need separate developer and reviewer subagents to manage code review loops?

Yes, you need separate developer and reviewer subagents to manage code review loops. The orchestration skill requires both dependency types to execute implementation phases and perform the final audit on the generated code.

Can I use a design doc to automate task routing and code review for my project?

You can use a design doc to automate task routing and code review by passing the file path to the skill. It parses the design document, decomposes the requirements into phases, and orchestrates the developer-reviewer loop automatically.

What is the best way to manage developer collaboration across multiple implementation phases?

The best way to manage developer collaboration across multiple implementation phases is using an orchestration skill that handles dynamic task decomposition and review loop management. This ensures thorough code review and prompt resolution of issues throughout the workflow.

What are the limitations of automating task scoping without a dedicated reviewer agent?

Automating task scoping without a dedicated reviewer agent prevents the execution of the final audit and blocks the code review loop. The skill requires both developer and reviewer subagents to resolve issues and validate multi-phase implementation.