feat: add task issue template

[Astro-Han]

Summary

Adds a third GitHub issue form for maintainer or agent execution tasks that are not user-facing bug reports or feature requests.

Why

PawWork currently has bug and feature intake forms. That is clear for users, but maintainer-created agent work sometimes needs a more execution-oriented brief: goal, scope, relevant context, verification, and whether the agent can implement directly or should investigate first.

Related Issue

No related issue. This PR adds the issue form discussed directly in the maintainer workflow.

Human Review Status

Pending. A human should make the final merge decision after reviewing the final diff and verification evidence.

Review Focus

Check whether the Task form is small enough for maintainers to use while still giving coding agents enough context to execute safely.

Risk Notes

Low risk. This only adds a new issue template. The template references a task label; GitHub only auto-applies labels that already exist, so the repository should create the task label before relying on automatic labeling.

How To Verify

YAML parse: ok for .github/ISSUE_TEMPLATE/03-task.yml
Diff check: only .github/ISSUE_TEMPLATE/03-task.yml was staged and committed

Screenshots or Recordings

Not applicable. This is a GitHub metadata change, not a visible app UI change.

Checklist

• Human review status is stated above as pending, approved, or not required
• I linked the related issue, or stated why there is no issue
• This PR has type, scope, and priority labels, or I requested maintainer labeling
• I described the review focus and any meaningful risks
• I listed the relevant verification steps and the key result for each
• I did not introduce unrelated refactors, dependencies, generated files, or file changes beyond the stated scope
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for desktop, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, generated content, or local file changes when relevant
• I reviewed the final diff for unrelated changes and suspicious dependency changes
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English

Summary by CodeRabbit

• Chores
  • Added a new structured "Task" issue template to standardize task reporting, including a title prefix, default metadata, and a labeled workflow.
  • The template provides required fields for goal, scope, and verification, an optional pointers field, and an execution mode dropdown with three safe-start options to guide task submissions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 265a5987-5eb0-4a7b-b54e-85e5a4f84cd8

📥 Commits

Reviewing files that changed from the base of the PR and between 33c5ad7 and ee4bda1.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/03-task.yml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/ISSUE_TEMPLATE/03-task.yml

---

📝 Walkthrough

Walkthrough

A new GitHub issue template "Task" was added at .github/ISSUE_TEMPLATE/03-task.yml. It provides metadata (title prefix [Task] , task label) and a structured issue form with required fields for goal, scope, verification, an optional pointers field, and an execution_mode dropdown with three options.

Changes

Task Issue Template

Layer / File(s)	Summary
Template Metadata .github/ISSUE_TEMPLATE/03-task.yml	Adds template name: Task, description, title prefix [Task] , and default label task.
Guidance / Intro .github/ISSUE_TEMPLATE/03-task.yml	Adds initial markdown guidance explaining intended use for maintainer/agent execution work and emphasizing verifiable tasks.
Form — Goal & Scope .github/ISSUE_TEMPLATE/03-task.yml	Adds required goal and scope textarea inputs with labels, descriptions, examples; scope includes in-scope/out-of-scope sections.
Form — Pointers .github/ISSUE_TEMPLATE/03-task.yml	Adds optional pointers textarea for relevant files/issues/PRs/logs context.
Form — Verification .github/ISSUE_TEMPLATE/03-task.yml	Adds required verification textarea with label, description, and example checklist for validating results.
Form — Execution Mode .github/ISSUE_TEMPLATE/03-task.yml	Adds required execution_mode dropdown with three predefined safe-start options describing escalating starting modes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• docs: make templates agent-ready #345 — also modifies .github/ISSUE_TEMPLATE/* handling and CI/workflow logic related to issue-template files.

Suggested labels

documentation

Poem

🐰 A little form hatched for tasks to do,
Goals and scope, and what to review,
Pointers tucked softly, checks in a row,
Execution modes guide how to go.
Hop on, maintainers — let progress grow!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding a new task issue template to GitHub.
Description check	✅ Passed	The PR description is comprehensive, addressing all required template sections including summary, rationale, related issues, review focus, risks, verification steps, and checklist.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/task-issue-template

---

_{Review rate limit: 8/10 reviews remaining, refill in 8 minutes and 40 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request introduces a new GitHub Issue Template for 'Task' to track maintainer or agent execution work. The template includes structured fields for defining goals, scope, context, and verification steps. A review comment suggests reordering the execution mode options to ensure the safest option is selected by default, aligning with the principle of least privilege.