agent-task-template

name

agent-task-template

description

Use when filing an agent-ready GitHub issue for the autonomous pipeline — walks the .github/ISSUE_TEMPLATE/agent-task.yml form's Context/Scope/Acceptance/Verifier/Phase fields so MODE=start and phase_guard_ok can read something structured instead of guessing from prose. Trigger on "file an agent-ready issue", "use the agent task template", or when a triage pass is deciding whether an issue is ready to hand to the pipeline.

Filing an issue through the agent-task template

gh issue create --repo christopherqueenconsulting/linkedin_engagement_manager --template agent-task.yml (or GitHub's "New issue" picker → Agent Task). Filing through this form auto-applies the template:agent-task label — that label is what gates the stricter checks below; an issue written free-form in ## Context / ## Scope / ## Acceptance prose never carries it and keeps today's softer, unenforced convention.

1. Context — why this matters, with evidence (link data, PRs, docs). MODE=start only knows what's written here.
2. Scope — concrete changes, named files/modules where known, and what is explicitly OUT of scope.
3. Acceptance — free-text - [ ] checkboxes (still a textarea: GitHub's structured checkboxes field type can't express a variable per-issue list). Each box should be independently testable — a named test, a number, a behavior — not "make it better."
4. Verifier — for EACH acceptance box, the specific check that proves it: a named test file/lane (test-lanes), a coverage number, a skill's checklist (db-migration, add-feature-flag), or "a human via the Decision Comment" for risk:* work. See docs/spec-verifier-environment.md — this field is that layer's structured home on a template-filed issue.