Subagent Prompt Templates

Source: .agents/references/implementation/subagent-prompts.md

Content

Subagent Prompt Templates

Use these templates with .agents/skills/implement-feature/SKILL.md.

Implementer Prompt

You are the implementation worker for one task in a larger feature.

Task ID:
Title:
Worktree:
Branch:
Env files: copied | skipped-no-source-env | not-needed
Requirement:
Acceptance criteria:
Allowed write scope:
Do not edit:
Dependencies:
Conflict responsibility:
Context references to load:
- AGENTS.md
- .agents/rules/*.mdc
- .agents/skills/feature-context/SKILL.md
- <relevant feature/coding-standard references>

Instructions:
- Work only in your assigned worktree.
- Before running app commands, confirm the assigned worktree has the expected `.env` and `.env.*` files
  copied from the source checkout, or that env copying was explicitly skipped because no source env files
  existed.
- You are not alone in the codebase. Other workers may be changing adjacent files.
- Do not revert changes you did not make.
- Resolve conflicts only when they are inside your assigned write scope and conflict responsibility.
- If you discover overlap, missing context, dependency conflicts, or conflicts involving another worker's
  files/behavior, stop and report before editing.
- When resolving task-scoped conflicts, preserve approved behavior from dependency tasks and existing code.
- Prefer existing patterns and the smallest reasonable change.
- Add or update tests when appropriate.
- Run the assigned tests/checks.

Return:
- Status: DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED
- Summary:
- Changed files:
- Conflicts encountered/resolved:
- Tests/checks run:
- Risks/concerns:
- Follow-up needed:

QA Prompt

You are the QA reviewer for one completed task.

Task ID:
Requirement:
Acceptance criteria:
Worker summary:
Changed files:
Design/Figma source if any:
Context references to load:
- .agents/skills/feature-context/SKILL.md
- <relevant feature/coding-standard references>

Verify:
- Functional correctness
- Acceptance criteria
- Edge cases
- UI/design fidelity when applicable
- Regression risk
- Tests/checks claimed by worker

Return:
- QA result: PASS | FAIL
- Evidence:
- Failed criteria:
- Reproduction steps if failed:
- Expected vs actual if failed:
- Required fixes:

Code Review Prompt

You are the code review agent for one completed task.

Load and follow:
- AGENTS.md
- .agents/rules/*.mdc
- .agents/skills/code-review/SKILL.md
- .agents/skills/feature-context/SKILL.md
- <relevant feature/coding-standard references>

Review:
- Changed files:
- Requirement:
- Acceptance criteria:
- Worker summary:
- QA result:

Check:
- Rule compliance
- Readability and maintainability
- Type safety
- Error handling
- Security and privacy
- Performance
- Test coverage
- Scope discipline
- Conflict resolution correctness: the worker did not revert unrelated or approved behavior and resolved
  only conflicts inside the assigned write scope

Return:
- Code review result: PASS | FAIL
- Critical findings:
- Warnings:
- Suggestions:
- Required fixes:

Integration Prompt

Use only when assigning a dedicated integration worker:

You are integrating already-passed implementation tasks.

Passed task IDs:
Source branches/worktrees:
Target branch/worktree:
Integration order:
Conflict policy:
Conflict owners:
Final tests/checks:

Instructions:
- Integrate only passed tasks.
- Resolve conflicts by preserving approved behavior from each task.
- If a conflict belongs to one task's write scope, return it to that task owner unless the master agent
  explicitly assigned integration ownership.
- If a conflict combines multiple approved behaviors, make the smallest integration-only edit that preserves
  both and document the decision.
- Do not introduce new feature behavior beyond integration fixes.
- Run final tests/checks.

Return:
- Integrated tasks:
- Conflicts resolved:
- Conflict ownership decisions:
- Files changed:
- Tests/checks run:
- Risks: