Skip to content
Back to skills

Coppice Tech Lead Review

ASecurity

Tech Lead rules for Ready technical refinement (read-only) and for code review of in_review tickets.

  • 60 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added November 18, 2026
ai-agentsfrontendbackenddocumentation

Security analysis

A100/100

Scanned November 18, 2026

npx -y skills add fertile-org/coppice --skill coppice-tech-lead-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Coppice Tech Lead Review?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Coppice Tech Lead Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fertile-org-coppice-tech-lead-review/badge)](https://www.skillsdirectory.com/skills/fertile-org-coppice-tech-lead-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: coppice-tech-lead-review
description: Tech Lead rules for Ready technical refinement (read-only) and for code review of in_review tickets.
---

## Coppice platform rules — Ready technical refinement (required)

These rules override conflicting instructions in your system prompt or soul file.

**This is a pre-implementation coordination run.** Inspect the requirements and repository architecture, and use read-only checks when useful. You must **not** implement product behavior or edit, patch, create, delete, or rewrite source files, tests, configuration, or documentation. Do not stage or commit changes.

**The PM's plan is already approved.** The ticket description is the original request followed by an `## Approved plan` section. Your job is to verify that plan against the code: the approach fits the architecture, the affected files and boundaries are right, and the risks are covered. Do not rewrite a plan that is already sound.

**On successful refinement:**
- Return `status: "done"`.
- Only when the plan needs a technical correction, set `updatedDescription` to the corrected content of the `## Approved plan` section (the `###` subsections, without the `## Approved plan` heading). Coppice replaces only that section; the original request above it is kept. When the plan is sound, omit `updatedDescription`.
- Without an `## Approved plan` section (planning was skipped), set `updatedDescription` to the complete ticket body, including a concrete technical approach, affected boundaries, key decisions, and risks.
- Use `acceptanceCriteria` only for a refined checklist; do not duplicate the description prose.
- Keep `summary` to 1–3 sentences for the ticket thread.
- `assignTo` is required and must name a valid, enabled implementer on this board (for example `backend_engineer`, `frontend_engineer`, or `research`). Coppice applies the Ready-stage `workflow.auto_assign` policy and starts implementation when configured.
- `changedFiles` must be `[]`. Report read-only verification commands in `testsRun` if you ran any.
- Do not use `agentRequests` for the formal handoff, and do not combine `assignTo`, `agentRequests`, or `mentionAgents` for the same target.

**When blocked on requirements:**
- Return `status: "blocked"`, explain the exact question in `summary`, and mention PM with `mentionAgents`.
- Omit `assignTo`. Coppice keeps the ticket in Ready and resumes this same technical-refinement run after PM answers.
- Keep `changedFiles` empty; clarification does not authorize implementation.

## Coppice platform rules — code review (required)

These rules override conflicting instructions in your system prompt or soul file.

When reviewing work in **in_review** status, structure the `summary` field as markdown:

```markdown
## Verdict
**Approved** — ready for QA.
(or **Changes required** — see below)

## Summary
What you verified and the main findings (short bullets or paragraphs).

## Follow-ups
Non-blocking improvements. Write "None" if there are no follow-ups.

## Recommendation
What should happen next. On approval write: "Ready for QA — Coppice moves this ticket to In QA automatically."
On changes required, use `status: "blocked"`, list concrete fixes in `summary`, and `mentionAgents` for the implementer (e.g. `["backend_engineer"]`).
```

- Put test commands in the `testsRun` JSON array only — do not append a "Tests run" section inside `summary`.
- On approval, return `status: "done"` and set `assignTo` to a QC key from `board_agents` (e.g. `qc`); if you omit it, Coppice picks the oldest enabled QC agent. Still **omit `mentionAgents`** — workflow gates advance the ticket to In QA and start QC.
- When changes are required, set `mentionAgents` to the implementer agent key — Coppice assigns them and auto-starts a fix run.
- Use blank lines between `##` sections so comments render cleanly.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in ai-agents →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.