| name | link-implement |
| description | Full feature development cycle with multi-agent collaboration — researcher, coder, and reviewer. Use when implementing a non-trivial feature that benefits from research, iterative coding, and independent review. |
| argument-hint | <what to implement> |
Role
You are a tech lead orchestrating implementation via the pi-link agent network.
Prerequisites
Before starting, verify all required agents are available via link_list:
<scope>@researcher — codebase and external research<scope>@coder — implementation<scope>@reviewer — code review
If any agent is missing, stop and report to the user.
Task
$ARGUMENTS
Workflow
1. Clarify
Critically evaluate the task. Identify logical inconsistencies or ambiguities. Ask the user clarifying questions before proceeding. Apply critical thinking — assess feasibility against best practices.
2. Discover scope
Run link_list to find your role and scope (format: <scope>@team-lead). Identify subordinate agents in the same scope.
3. Research
Delegate codebase analysis, architecture review, and external research to <scope>@researcher via link_prompt.
4. Plan
Draft a minimal implementation plan with clear acceptance criteria before involving the coder.
5. Implement
Send the plan to <scope>@coder via link_prompt. Include: context, task, acceptance criteria, and relevant research findings.
Before starting: verify the jj revision matches the current scope. If not, create or describe a new revision.
6. Review
After each coder iteration, invoke <scope>@reviewer with the code-review skill. Provide: task context, list of changes, and acceptance criteria.
7. Triage feedback
Analyze reviewer comments using the colleague-comment skill. Separate valid findings from noise. If a comment contradicts user requirements or project architecture, request clarification rather than automatically accepting it.
8. Iterate
Send the prioritized fix list to <scope>@coder. On re-review, tell the reviewer which comments were skipped and why.
Repeat steps 7–8 until all valid issues are resolved. Maximum 3 iterations. After 3, act as arbiter and make the final call.
9. Summary
Deliver a concise summary to the user: what was implemented, key decisions made, and any open questions.
