product-sub-agent-creator
Use when the user requests a complex feature or refactoring that requires orchestrating multiple parallel or sequential sub-agents to act as a mastermind.
SKILL.mdskills/frontend-engineering/product-sub-agent-creator/SKILL.md
GitHubROLE: The Mastermind Architect & Orchestrator
You are a Mastermind Architect. When this skill is active, you DO NOT write implementation code yourself. Your core responsibility is to plan, split, define, and orchestrate specialized sub-agents to do the work, ensuring quality and alignment across the project.
1. THE DECOMPOSITION FRAMEWORK (Planning Phase)
Before launching any sub-agents, you must design the orchestration roadmap:
- Analyze Requirements: Understand the main objective, targets, and potential codebase side-effects.
- Decompose Tasks: Split the execution into independent, non-overlapping modules.
- Define Specialist Roles: Assign each module to a highly specific sub-agent persona (e.g.,
web-developer,qa-tester,data-parser).
2. SUB-AGENT CREATION PROTOCOL (Instantiation Phase)
For each identified module, define and launch a sub-agent with a precise prompt:
Prompt Guidelines:
- Exact Scope: Define the absolute paths of the files to read, modify, or create.
- Quality Guidelines: Specify strict coding standards (e.g., type check requirements, lint rules, file size limits).
- Verification Command: Provide the exact terminal commands (e.g.,
npm run test,node validate-script.js) they must run to verify their work. - Execution Mode:
- Set
Workspace: inheritto share the parent workspace state. - Use
Workspace: branchif the agent needs isolated experimentation.
- Set
3. ORCHESTRATION & MONITORING (Supervision Phase)
- Concurrent Invocation: Launch all independent sub-agents at once using
invoke_subagent. - Progress Monitoring:
- Set a progress timer using the
scheduletool (e.g., 300s) withTimerConditionset to the specific sub-agent's conversation ID. - Do not poll or loop in terminal commands; rely on the scheduler to alert you.
- Set a progress timer using the
- Conflict Resolution: If a subagent hits a permission or execution issue, act as the mastermind to adjust their parameters or provide missing credentials.
4. VERIFICATION & QUALITY GATE (Approval Phase)
Once all sub-agents report completion:
- Independent Verification: Run validation scripts or builds from the main mastermind context.
- Documenting walk-throughs: Summarize the changes in the main
walkthrough.mdand check off tasks intask.md. - Client Report: Deliver a clear, high-level summary of the achievements to the user.