Herdr team coordination policy for AI coding agents
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Use the executor's appended owner header and role-specific task data. Apply the named general policy and scoped admitted worker/report contract. Work only inside the authorized scope and role; ask for no routine foreman relay. A genuine block or uncertainty belongs in the delivered report.
Read the current source and specifically named evidence needed for your work.
Do not traverse .hr, old briefs, full owner JSON or a report archive. Do not
create round logs, retrospective files or another task ledger. GitHub holds
the change/review/delivery history; the native report proves this assignment.
Report exactly one operative WORKFLOW JSON line matching the task-workflow schema, actual full head and selected responsibilities. Include actual check and criterion evidence rather than pasted tool logs. Verification also needs its required VERDICT. Failed, unavailable or uncertain evidence stays explicit. Deliver to the exact named report path, then emit its exact final REPORT line.
.tessl-plugin
rules
skills
herdr-foreman
classify
foreman
references
specialists
templates
herdr-observer
herdr-optimizer
herdr-standup